I am writing this post to resolve the bellow error in Microsoft Dynamics Axapta 2012 R3
"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 (8/7). Use a newer Microsoft Dynamics AX kernel."
I was a task to restore the database of LIVE server on test server i.e means create the replica of live on test environment.
Database and Model store has been restored successfully. Now i have to start the services of Microsoft Dynamics Ax. It gives the error -
"Windows could not start the Microsoft Dynamics Ax Object Server on Local Computer, refer to service- specific error code 100."
Then i have to check the event viewer to observe the problem exactly.
Error message:
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 (8/7). Use a newer
Microsoft Dynamics AX kernel."
login. Error message: "The internal time zone version number stored in the
database is higher than the version supported by the kernel (8/7). Use a newer
Microsoft Dynamics AX kernel."
Solution -
For the resolution you need to change the value for the column value SYSTIMEZONESVERSION in the table "SQLSystemVariables". if you look into the event viewer you can see that it find the value 8, but you need 7 (8/7).
Hence,
The solution is to set the value to 7.
select SYSTIMEZONESVERSION from SQLSystemVariables
update SQLSystemVariables
set SYSTIMEZONESVERSION = 7
Thank You!
SytemTimeZoneVersion was a value, and not a column at last the the R3 version I just worked in. Here's my sql query.
ReplyDeleteselect * from SQLSystemVariables
WHERE PARM = 'SYSTIMEZONESVERSION'
UPDATE SQLSystemVariables
SET VALUE = 7
WHERE PARM = 'SYSTIMEZONESVERSION'
Thanks this helped.
ReplyDeleteThanks this helped.
ReplyDeleteselect * from SQLSystemVariables
ReplyDeletewhere PARM='SYSTIMEZONESVERSION'
update SQLSystemVariables
set VALUE=1
where PARM='SYSTIMEZONESVERSION'
same issue with CU9. This fix works as well.
ReplyDeleteThis is valid for Dynamics365 for Operations as well!
ReplyDeleteIt really helped a lot. Kudos!
ReplyDeleteThank you
ReplyDelete