Error in connection to Navision SQL 3.60 Database

t.norit.nori Member Posts: 6
edited 2004-12-16 in Navision Attain
When I try to oper my database Navision (SQL 3.60) appear this message:

>>>>
The Object table has a primary key constraint in the SQL Server table description that is not compatible with Microsoft Navision Attain definition:

Key fields: Type, Company Name, ID
SQL Primary key fields: Tipo, Nome Società, ID
<<<<

Help me
Thanks very much
:cry::cry::cry::cry::(:(:(:(:(

Comments

  • TheDude27TheDude27 Member Posts: 6
    t.nori wrote:
    When I try to oper my database Navision (SQL 3.60) appear this message:

    >>>>
    The Object table has a primary key constraint in the SQL Server table description that is not compatible with Microsoft Navision Attain definition:

    Key fields: Type, Company Name, ID
    SQL Primary key fields: Tipo, Nome Società, ID
    <<<<

    Help me
    Thanks very much
    :cry::cry::cry::cry::(:(:(:(:(



    Possibly it doesnt like the "à" in your company name. Navision names its SQL tables based on the company name. Rename the company using C/SIDE then restore it to SQL see if that helps.
  • GoMaDGoMaD Member Posts: 313
    I think the text mentioned in the Error message is a field name.

    I've got the same message:
    The Object table has a primary key constraint in the SQL Server table description that is not compatible with the Microsoft Business Solutions-Navision definition:

    Key fields: Type,Company Name,ID
    SQL primary key fields: Type,Company Name,ID

    But this time it's all english.

    Does anybody know what the problem can be?

    Regards,
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!
  • kinekine Member Posts: 12,562
    Which collation you are using? Made you some changes in this settings (change collation)? It is database created in this collation or was created in another collation? :?:

    Have you enabled "MaintainViews" option?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • GoMaDGoMaD Member Posts: 313
    Found the solution.

    Open your Enterprise Manager of SQL server, click the tree view until you see your Navision SQL Database and then click on Tables so you can see the tables.

    The error is in the folowing table: $ndo$dbproperty
    If you open this table you must look for the field with the name 'identifiers'. The value that is this field must be in the same language as the values in the Objects table.

    for example on my SQL server where the error was the language of the 'identifiers' field was Dutch (see eg1) and the Language of the values in the Objects table was English.

    I search for the 'identifiers' field in the English value, found it in a standard 3.70 SQL DB (see eg2) and just copied it over the value in the DB with the error and i could log on again.

    eg1: 2000000001="Object",1="Soort",2="Bedrijfsnaam",3="ID",4="Naam",5="Gewijzigd",6="Gecompileerd",7="BLOB-referentie",8="BLOB-grootte",9="DBM Tabelnummer",10="Datum",11="Tijd",12="Versie";2000000009="Sessie",1="Verbindings-ID",2="Gebruikers-ID",3="Mijn sessie",5="Aanmeldingstijd",6="Aanmeldingsdatum",16="Databasenaam",17="Toepassingsnaam",18="Aanmeldingstype",19="Hostnaam",20="CPU-tijd (ms)",21="Geheugengebruik (KB)",22="Fysische I/O",23="Geblokkeerd",24="Wachttijd (ms)",25="Blokkerend verbindings-ID",26="Blokkerend gebruikers-ID",27="Blokkerende hostnaam",28="Blokkerend object";2000000010="Databasebestand",1="Nr.",2="Bestandsnaam",3="Grootte (KB)"


    eg2:
    2000000001="Object",1="Type",2="Company Name",3="ID",4="Name",5="Modified",6="Compiled",7="BLOB Reference",8="BLOB Size",9="DBM Table No.",10="Date",11="Time",12="Version List";2000000009="Session",1="Connection ID",2="User ID",3="My Session",5="Login Time",6="Login Date",16="Database Name",17="Application Name";2000000010="Database File",1="No.",2="File Name",3="Size (KB)"

    Hope this helps.

    Regards
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!
Sign In or Register to comment.