SQL Server Collation Problem

prasslprassl Member Posts: 24
Good morning everybody...

I am in trouble with my Navision SQL Server Installation, and I m really curious if someone of you knows the cause for that specific error...

Ok, these things in advance, I m using a SQL Server for hosting my database, Standard Edition, on a NT 5.2 SP3 Operating System, the client I m using is a NAV 4.0 SP 1...
The SQL Server sorting option is set to : Latin1_General_CI_AS..

However, I ll include a few screenshots to maybe give you a better idea of what causes the error (Assume that the settings, DB Connection, DB name and user authentication are correct, just had to blacken it out...)
On a standard DB, one that s been automatically generated during installation, the properties show the following sorting option:
http://www.e-prassl.at/manu/images/SQL_Server_Enterprise_Manager_TestDB_Properties.JPG
On my own DB, though the settings have been set also, the system doesn t save them properly, resulting in this:
http://www.e-prassl.at/manu/images/SQL_Server_Enterprise_Manager_DB_Properties.JPG

With that problem, the SQL Server returns the following error message on Navision Connect:

http://www.e-prassl.at/manu/images/Nav.Starting_Error.jpg
German though, the error message says that "The collation "?" is not supported by MBS Navision"

Restoring a backup didn t help, nor creating a new DB and importing data + objects...

Question now, please, how to solve this ?
Any help would be greatly appreciated

many thanks in advance
cheers,
PM
... I am not a programmer, I just write code.

Comments

  • prasslprassl Member Posts: 24
    another interesting feature:

    if the enterprise manager on the sql server is being executed, one can connect, if not, one cannot...

    help, please ](*,)
    ... I am not a programmer, I just write code.
  • Miklos_HollenderMiklos_Hollender Member Posts: 1,598
    I could not even install SP1 for SQL2005 with Hungarian collation - MSFT told me to set "Validate Code Page" to No, which is dangerous. I think it's the same problem - SQL2005 support is not yet perfect in SP1.
Sign In or Register to comment.