Upgrading from NAV 2009 R2 to NAV 2016, problem Syncing Schema

jwilder · 2016-06-14

Here is what I have done so far (very much summarized)
• Converted Database to NAV 2013 no problems (takes a while due to Unicode conversion, 7 hours)
• Converted Database to NAV 2015 no problems.
• Tried Syncing Schema in NAV 2015 but do not believe it will work without compiled objects. Remember that at this point there are no objects except for tables in the database.
• So continued on and converted database to NAV 2016 no problem.
• Imported NAV 2016 objects (including add-ons and our customizations)
• Compiled everything using Later option (still a few objects do not compile since not 100% done with code upgrade)
• Attempted to Sync Schema For All Tables from Dev environment but errors after about 10 seconds. Run Sync-NAVTenant DynamicsNAV90-3 –Mode CheckOnly and fills the screen with so many errors that they don’t all fit in the Admin Shell screen. I expect these errors since many fields are being dropped.
• Tried running Sync-NAVTenant DynamicsNAV90-3 –Mode Force and it runs for a minute but then errors: The following SQL Error was unexpected: Invalid object name ‘SWKTestUpgrade2016.dbo.SWKtest2016$Property Store’.
• Deleted this table from SQL as it is old andnot used anymore (I believe), restarted service tier to clear cache, reran sync (force) and get the same error.

Any thoughts on how to get past this?

jwilder · 2016-06-14

I have figured this out. There is a step earlier on in the NAV 2009 R2 to NAV 2015 toolkit that removes old unused tables. Since my license did not permit me to do this I deleted the tables via SQL using the following script:
DELETE FROM [SWKTestUpgrade2016].[dbo].[Object] WHERE ([Type] <= 1) and (ID = (9801))

This does remove the table from the Object Table in NAV but it does not remove the table on the SQL side. Even once I figured this out and manually deleted the table in SQL it still caused the same error so there must be another pointer towards that table somewhere that causes the Sync to error.

So the fix is to not do that. Instead use your partners license when running the table deletion part of the toolkit.

jwilder · 2016-06-14

I have figured this out. There is a step earlier on in the NAV 2009 R2 to NAV 2015 toolkit that removes old unused tables. Since my license did not permit me to do this I deleted the tables via SQL using the following script:
DELETE FROM [SWKTestUpgrade2016].[dbo].[Object] WHERE ([Type] <= 1) and (ID = (9801))

This does remove the table from the Object Table in NAV but it does not remove the table on the SQL side. Even once I figured this out and manually deleted the table in SQL it still caused the same error so there must be another pointer towards that table somewhere that causes the Sync to error.

So the fix is to not do that. Instead use your partners license when running the table deletion part of the toolkit.

Howdy, Stranger!

Quick Links

Categories

Upgrading from NAV 2009 R2 to NAV 2016, problem Syncing Schema

Best Answer

Answers