Error during Upgrade to NAV 2013 R2

Minu63 · 2014-08-07

In step 1 "Prepare the existing data for the upgrade" / task 4 "Data conversion" I always get an error while I'm converting the NAV2013 database to NAV 2013 R2. The message is:

The following SQL Server error or errors occured:
4924,"42S22",[Microsoft][SQL Server Native Client 10.0][SQL Server]Fehler bei ALTER TABLE ALTER COLUMN, da die 'Version List'-Spalte in der Object-Tabelle nicht vorhanden ist.

SQL:
ALTER TABLE [dob].[Object] ALTER COLUMN[Version List][VARCHAR](248) NOT NULL

It's the last step of processing an upgrade from version 2.60.A to 2013 R2. Does anybody has an idea how to fix it?

In the NAV Development Environment I cannot change the field name in the object table 2000000001. And when I change the field name in the SQL table, I got the error "The Version List field on the Object table does not exist in the SQL Server table or view.

postsaurav · 2014-08-07

Hey,

If the problem still exist please read it here -

https://community.dynamics.com/nav/f/34/t/124256.aspx

You need to upgrade the NAV 2013 R2 Build to at Least rollup 5. I would suggest to use the latest build of NAV 2013 R2 ie. Update Rollup 9(Cumulative Update) for Microsoft Dynamics NAV 2013 R2 (Build 37221) - W1.

For Download details of Latest Rollup Please Refer -http://saurav-nav.blogspot.in/2014/07/nav-2013-r2-cumulative-update-9-released.html

How to Apply Rollup Please refer - http://saurav-nav.blogspot.in/2014/04/how-to-download-rollup-for-nav-2013-and.html &
http://saurav-nav.blogspot.in/2014/04/how-to-apply-rollup-of-nav-2013-and.html

Let me know if you have any issues.

VectorK · 2014-08-07

And rememeber that in the 2nd Step of the process, Sync-NAVTenant will be your best friend

Minu63 · 2014-08-08

I found at last the solution! I think it was a language layer problem. I replaced the fin.stx and fin.etx in the client directory by those versions from the ..\ENU subdirectory and it worked!

I made this for both clients (2009R2 and 2013). Therefore I don't know, if this have been really necessary or if it would have been sufficent to replace then in 2013.

Error during Upgrade to NAV 2013 R2

Answers

Categories