I am working at a site where we are running Navision 3.7 with Hotfix 12 applied running on a SQL 2000 Database. We have done a large number of customisations on the system itself. I have a strange SQL Collation error which normally occurs if you have a version conflict of some sort between the clients, all the Clients and server are using the same version and this error only occurs when the first user connects. The workaround for now id to launch to Navisions simultaneously and log in with 2 user accounts and then it goes through, once one user has logged in the problem does not again occur. We have forwarded this request to Microsoft and needless to say they have not been of any help, Please can someone help me on this one…???
What is the error message? What is the name of the database?
THE NAME OF THE 3 DATABASES ARE DEVELOPMENT, INTEGRATION AND PRODUCTION, i HAVE ATTACHED A SCREENSHOT OF THE ERROR MESSAGE ON STARTUP. THE IMPORTANT THING HERE IS THAT IT ONLY HAPPENS ON THE FIRST CONNECTION, LOGGING ON WITH 2 SESSIONS SIMULTANEOUSLY SOLVES THE PROBLEMS AND LAUNCHES THE DATABASES. I HAVE LOGGED WITH MICROSOFT AND HAVE SOMEONE HELPING ME OUT FROM THEIR SIDE IN BELGIUM, BUT SO FAR NO JOY, I HAVE ATTACHED A ZIP FILE WITH ALL THE SETTINGS AND THE ERROR MESSAGE, ANY HELP WITH THIS ERROR WILL BE GREATLY APPRECIATED. THANK YOU - TRIED TO UPLOAD NOT ABLE TO THE MESSAGE STATES “? Collation is not supported by Microsoft Business Solutions Navision 3.7”
Try this on a new database: When you create the database in Navision, ensure that the “Autoclose” check box is NOT ticked, in the Options tab of the New Database dialog. This option exploits a SQL Server bug that causes the DATABASEPROPERTYEX() function - a SQL function - to return a NULL for the collation of the database. Navision uses this function to determine the collation and when getting a NULL that is not expected gives you the error you see. The strange behaviour relating to subsequent session working ok is probably due to Autoclose freeing and is just part of the bug. Autoclose will not be available in future versions of Navision (probably from the first SP of 4.0). Hope this works. You can try to turn this option off in Enterprise Manager in your existing databases - this should get them up and running but I am not certain of that.
I had the same problem and your solution worked! Just turn off the Autoclose property from the Enterprise Manager in the faulty database. Thank you very much! Toni
I have also tested the “Autoclose”; and does resolve the “? Colation” problem; This test has been done on the same database that “roy” mentions above. Thankx.