-->

Dynamics AX 2012 R2 Fatal SQL condition during login

maqk® by MolviDSLR Khan | 6:26 PM

An interesting yet dangerous thing happened in my AX life today. Actually in one of our environments, we had previously upgraded to CU6. Now somehow the AX server VPC got restored to the earliest snapshot available forcing us to install a new fresh AOS service instance. The service was installed in no time but only to give the following error at each start and failing each time.

A peep into the event log yield the following information:





Object Server 01: Fatal SQL condition during login. Error message: "The internal time zone version number stored in the database is higher than the version supported by the Kernel (4/2). Use a newer Microsoft Dynamics AX kernel."
I have the following roadmap for the resolution now :)

  1. Install clean databases with new names
  2. Connect installed service to new database and start AOS service
  3. Compile application code and sync database
  4. Upgrade to CU6
  5. Connect AOS service with existing CU6 compatible databases
  6. Resume from whatever we left
To my retro suprise, the service failed to start with error code 110 after configuring to connect with new databases. This matter was resolved menrioned in another blog.

Now resuming from point 3 :) 

0 comments:

Post a Comment

top