Upgrade to 2013 - Invalid column name 'DBM Table No_'

ryancairns

I am currently in the process of upgrading a client from 4.0SP3 -> 2009 R2 -> 2013. I am at the stage where I have opened the db using the 2013 client and now I am trying to connect the database to the NST so I can run the final data script.
When I try and open the RTC I get the following error:



Server instance: DynamicsNAV70
Session type: UnknownClient
Session ID: N/A
User: XXXXX
Type: System.ServiceModel.FaultException`1Microsoft.Dynamics.Nav.Types.ServerFault, Microsoft.Dynamics.Nav.Types, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Message:
The following SQL error was unexpected.
Invalid column name 'DBM Table No_'.
Statement(s) could not be prepared.

StackTrace:
at Microsoft.Dynamics.Nav.Service.NSServiceBase.HandleException[T](Object& callOutput, Boolean& terminateConnection, Exception e)
at Microsoft.Dynamics.Nav.Service.NSServiceBase.ExecuteOperation[T](String operationName, ServiceOperation`1 operation, Connection connection, Boolean revertLanguageChanges)
at Microsoft.Dynamics.Nav.Service.NSServiceBase.OpenConnection(ConnectionRequest connectionRequest)
Source: Microsoft.Dynamics.Nav.Service
HResult: -2146233087


I know DBM Table No_ belongs to the Object table but I have no idea why I am getting this message.

Has anyone any ideas? It is definitely a database issue as demo database is running fine.

Thanks

ryancairns

Just an update on this - I was able to take a NAV backup from 2013 DEV Environment and restore this into a new 2013 database. However this might not be a feasible option for the actual go-live of the upgrade because of the sheer volume of data in some of the companies (I was testing a smaller company today).

So I still need to figure out what this error means and what it relates to. The database contains a number of stored procedures including the SQL Perform Tools.
Any pointers or suggestions would be greatly appreciated. Thanks

ryancairns

I am still no further with this issue. I started the whole process again however when I completed the 2009 part of the upgrade I ensured that I could at least connect the database to the 2009 R2 service and open it with the 2009 RTC client - this worked fine.

However once again the same error when I try to connect the 2013 service to the database in order to run the 2013 Step 2 data conversion I am still getting the same error.

ryancairns

I persisted and eventually found the solution for this problem:

The original database was created in NAV 3.6.
http://support.microsoft.com/kb/906164

This fixed the problem.

geordie

This meas the original upgrade 3.6 -> 4.03 hasn't been done properly?
The same resolution shown in KB page appears in upgrade toolkit manual.

Ravi_Thakkar

Using that article if problem is resolved then can you please guide me how to proceed ?
I tried but failed.

Thanks.

TFCrowther

This is because the database was from a very old version 3 database. Run the following script in SQL Server Management query against the NAV database:

update [$ndo$dbproperty] set identifiers=replace(identifiers,'.','_')
go
EXEC sp_rename 'Object.[DBM Table No.]', 'DBM Table No_', 'COLUMN'

Big_D

Had this issue too and thanks to TFCrowther - issue no more - thanks for sharing =D> !