Wednesday, July 24, 2013

AX2012 R2 : Synchronize Table – Failed to create a session

Hi All

Today during a DB Sync compare at the end the follow error:

Failed to create a session; confirm that the user has the proper privileges to log on to Microsoft Dynamics

The code in error was on class SysSetupInstaller Method loadAllData on RunAs command.

After some investigation, I have found on Table USERINFO two records with ADMIN ID ( I have two Partitions ) where the first one had a wrong SID !
After update with the right SID, the Sync process finished with success.

See also AX2012 R2 : DB Sync – Failed to create a session

Enjoy !


Ira Siva said...

P0001 job is running for 10 stores.
1. sometime pulling the sales transactions from Retail POS
2. sometime don't.
3. Sometime disappear without any record/history in the upload Session
4. sometime pull only partial data
can someone give us solution please..
Ira Siva

Anonymous said...

I have the same error while synchronizing, but absolutely no problems with Sid. Another idea?

Anonymous said...

i am having a issue , i ran P job , file are in upload folder and in DB it is showing the record with status "2" but i am not getting any information into upload session link .
do you have any clue ?

Anonymous said...

We are encountering the same issue, the data from Store DB was partially pulled.

Have you resolved this issue?

Mansi Rao said...

Most error messages in AX appear in the Infolog (I am going to discuss that in a future post). The errors range between being completely useless and exactly describing what needs to be done to fix the issue. Most are somewhere in between. Hopefully the user saved or took a screen-shot of the message. But what do you do with it?

First you need to determine the source of the error, then you can figure out how to fix it.

Finding the Source of the Error

Search the error message on Bing or Google. Frequently the error will show up along with information about how to fix. Other sites to check - Microsoft CustomerSource, Dynamics Community and AXUG Collaborate.

If the error is easily repeatable, use a development or test environment and reproduce the error. When you get the Infolog, double click on it and this will bring up the development window with the code stack that produced it. If this does not work, go to step 3.

Step 3 uses the cross-reference tool ( in Microsoft Dynamics AX. Side note, the cross-reference should always be kept reasonably up to date in your development environment. Steps on how to use this below.