I seem to get this error a lot lately.
I have found out that it is due to discrepancies between the version of the objects and the schema. So all you have to do is go to the Development Environment and run the “Sync. Schema for all Tables” function, right?
No – sorry – same error.
The last resort is to go to Powershell. Open the Dynamics NAV Administration as an administrator and run the Sync-NAVTenant Command.
And now all is well:
And now the Synchronization runs fine in the development.
If there are any destructive changes in the objects the synchronization will fail. It is possible though to correct each object in the Development Environment. Just make sure that you use the “Later” option when saving and compiling the object.
Then synchronize again and everything will work fine.
I had same issue today, and Marcin solution worked for me. The real indebt explanation is, that the filed arrived in CU 07 as Anfinnur write, so if you have a database with objects before CU 07, but have build updated your executable to CU 07 or higher, then you get this error.
The simple work-around is to take the table 2000000110 "Active Session" and 2000000111 "Session Event" from a database with CU 07 or higher and restore the table objects into your database with the issue. Then start the development client as administrator and compile all tables with validation.
That worked for me.
Jesper Kenborg, MCP, MCTS
The field "arrived" in CU 07(...).
Caused much pain for me in a recent upgrade.
"Synch Schema" worked for me.
I had the same issue. Your solution didn't work for me. What I did was add fields 'Session Unique ID' as GUID data type in Active Session and Session Even tables.
Found it! Thanks to jglathe - recompile system tables and run as admin, before doing it.
That last command doesn't do it for me. Still getting the same error! :(