As you might know, I'am a big fan of the Microsoft Dynamics products line, and Dynamics NAV solutions are always have my special interests. Recently, a colleaque of mine, lets call him "Paul"; investigated an issue with one of our clients that got an error on importing a custom build FOB into their production environment. They have a test-, as well as an acceptance environment and the FOB has been gone through all the right procedures. On importing the FOB into the production database, our customer got the error:


"The following SQL Server error or errors occurred when accessing the NAME table: 650,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server] You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. SQL: ALTER TABLE "DATABASENAME"."dbo"."Company$tablename" ADD "NewTableFieldName" TINYINT NOT NULL CONSTRAINT "$ndodefault$138xxxxxxx$xxxxx" DEFAULT 0"  

Microsoft Dynamics NAV Classic error on importing a custom FOB - www.Oostdam.Info - picture 1

The above text is just like the picture here on the left, but the specific database, company and tablenames are blocked on purpose. We like to share with others, but we keep in mind our customers privacy along the side.




The production database has a full database replication, on another server, and some thight extra SQL-log backups on the side.


This tricked me, as we just recently implemented the replication server for this customer, and I expected this change to be the cause of this error. No $#$%$# way,... but it took a couple of days to find that out....

Another person could import the specific FOB without any problems and without evaluated rights; and we started to investigate this issue, wanting to learn and benefit for future use. And we did, because now we even share it with the world!!

We looked at, and compared the access rights on the SQL databases but couldn't determine any differences. There was a tiny difference in some local administrator rights on the replication server but eventually it turned out to be the NAV Dynamics Classics client, from which the FOB was initial mented to be imported from, the real issue. What a same.... Pfff... Wasted some time on that one, and so did my collegue "Paul" ....

The Microsoft Dynamics NAV Classic client build that was used to import the FOB was older than the client that the production database was expecting. I didn't see that coming, but thats exactly why I want to share this information with the rest of the world!!

Have fun and work effiëntly with Microsoft Dynamics NAV !


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Ben OostdamBen Oostdam has been working with Windows systems since 1993. Worked for several companies as a system administrator, and is currently a Senior Support Engineer for a large company in the Netherlands.

Disclaimer: The information contained in this website/article is for general information purposes only. The information is provided as is, by Ben Oostdam and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website. Through this website you are sometimes able to link to other websites which are not under my control. I have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them. Every effort is made to keep the website up and running smoothly. However, I take no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control. All entries in these articles, are my individual opinion, or from co-writers and they don't necessary reflect the opinion of my employer.


 

Wednesday the 17th, July 2019. All rights reserved.. // Oostdam WebDesign