web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / AX 2012 Production Upg...
Microsoft Dynamics AX (Archived)

AX 2012 Production Upgrade

(0) ShareShare
ReportReport
Posted on by lcwik 480

Hi,

We have upgraded AX 2012 CU3 to R2 CU6 in NEW DEV and NEW TEST environments according to upgrade scenario. We were succeed. Now we want to update old TEST environment and try it before PROD upgrade but there are some problems.

  1. Database was upgraded successfully with exported model store and restored model database - no warnings and no errors.
  2. During AOS installation there are warnings related to partition column what we experienced at the beginning of the upgrade process in NEW TEST environment. Database synchronization helped then but now we get missing partition column in the infolog after 30 minutes of synchronization.
  3. I tried to recompile application, even manually add partition column in the database - no success:(
  4. It's not possible to run any checklist.
Any ideas how to solve that?
BTW: when should partition columns be created? During first synchronization or during database upgrade or new AOS (R2) installation?
Thanks,
xaze

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Tommy Skaue Profile Picture
    Tommy Skaue Moderator on at

    Please head back to the upgrade guide and search for the term "installmode" and see how that step correlates to your current progress. You are most likely trying to apply a modelstore that is not in "installmode". You can set the installmode on the modelstore by using axutil or powershell. Basically it sets a series of dirty-bits on several layers, and when you start the AOS it will honor these flags and bypass some initialization steps, the same steps that is giving you some headache right now.

  • lcwik Profile Picture
    lcwik 480 on at

    Oh I missed that step:/ I started installation again with model store exported in install mode. I hope it will be fine now. Thank you:)

  • Tommy Skaue Profile Picture
    Tommy Skaue Moderator on at

    Well, if it helps, please mark my suggestion as the answer. ;-)

  • lcwik Profile Picture
    lcwik 480 on at

    Sure but first we need to make it working:)

    Unfortunately it didn't help.

    Steps that I performed:

    1. Model database restoration on destination database server

    2. Model database set into install mode

    3. Modelstore exported

    4. Database upgrade - no errors and warnings

    5. AOS installation - warnings related to PARTITION column

    Any other ideas?

  • Tommy Skaue Profile Picture
    Tommy Skaue Moderator on at

    There might be some warnings and errors around the Partition column before the data upgrade checklist is complete in PROD, and you need not worry about them. I can't remember which ones it was, but I remember there were a few.

    You should also make sure any batch and batchjob rows have their STATUS set to 0 before you install and start the AOS.

    Just run a SQL against the business database:

    UPDATE BATCH SET STATUS = 0

    UPDATE BATCHJOB SET STATUS = 0

    You may also want to update the Batch Server Groups:

    UPDATE BATCHSERVERGROUP SET  SERVERID = '01@MYAOSSERVER'

  • lcwik Profile Picture
    lcwik 480 on at

    Yes, we had those warnings during first environment upgrade and it was successful then.

    It also didn't help. During startup there are hundreds messages in infolog related to missing columns (PARTITION, DEL_CREATED, etc.).

    When I try to run data upgrade checklist I get:

    Cannot delete a   record in Personalization data (SysPersonalization).
    The SQL database has issued an error.
    SQL error description: [Microsoft][SQL   Server Native Client 10.0][SQL Server]Invalid column name 'PARTITION'.
    SQL statement: DELETE FROM   SYSPERSONALIZATION WHERE ((PARTITION=?) AND (((USERID=?) AND (ELEMENTTYPE=?))   AND (ELEMENTNAME=?)))
    Cannot create a record in SQL statement   trace log (SysTraceTableSQL). Trace type: Error, Admin.
    The SQL database has issued an error.
    SQL error description: [Microsoft][SQL   Server Native Client 10.0][SQL Server]Invalid column name 'DEL_CREATEDTIME'.
    SQL statement: INSERT INTO   SYSTRACETABLESQL   (TRACECONTAINER,STATEMENT,CALLSTACK,TEXT,TEXTDETAILS,TRACETIME,CATEGORY,CODE,CONNECTIONTYPE,CONNECTIONSPID,CONNECTIONID,ISLOBSINCLUDED,ISMOREDATAPENDING,ROWSAFFECTED,ROWSIZE,ROWSPERFETCH,ISSELECTEDFORUPDATE,ISSTARTEDWITHINTRANSACTION,STATEMENTTYPE,STATEMENTID,STATEMENTREUSECOUNT,DETAILTYPE,CREATEDDATETIME,DEL_CREATEDTIME,CREATEDBY,DATAAREAID,RECVERSION,PARTITION,RECID)   VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
    . Unable to save User Menu My favorites

     

    Interesting that we had similar problem after two new model imports in upgrade environment but we restored business data database and then it was fine. What about SQLDictionary table? Maybe it should be modified somehow - just a thought.

  • Tommy Skaue Profile Picture
    Tommy Skaue Moderator on at

    There should not be hundreds of infolog messages, then something else is wrong. You need to revert back in your upgrade progress. You wrote that you are trying to upgrade "old test". What is old test compared to the test you have already successfully data upgraded? Is it a copy of RTM/FP test prior to the first database split, or is it a backup of TEST before the code upgrade process?

  • lcwik Profile Picture
    lcwik 480 on at

    According to upgrade scenario we created a NEW TEST environment with database copied from Acceptance environment. We upgraded database and AOS in NEW TEST. Then we duplicated NEW TEST to NEW DEV where we performed code merge with success. Data upgrade checklist was performed. NEW TEST and NEW DEV are now updated and tested - everything is ok with them.

    Now berfore PROD upgrade we want to test the process in "old" TEST which has slightly different data from Acceptance that was used for at the beginning for NEW environments. Some time ago "old" TEST and Acceptance were updated with database from PROD and now they might be slightly different.

  • lcwik Profile Picture
    lcwik 480 on at

    BTW: should I remove also base classes from higher layers on this stage of the process? Or it's not necessary?

  • Tommy Skaue Profile Picture
    Tommy Skaue Moderator on at

    Any changes needs to be completed and Quality Assured in the code upgrade process stage. The only artifacts you need to remove are the ones causing unwanted conflicts and prohibits the upgrade.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans