Database Version

ArhontisArhontis Member Posts: 667
Hello,

I have an sql database and a client of 3.70.A version both.

A few minutes ago some windows updates automatically installed on the server that keeps the sql server.

After that updates the clients cannot open the database with the error of compatibility:
The ... database on the ... server cannot be opened by this version of Microsoft Business Solutions-Navision. The database has been converted by a newer program version.

You must upgrade Microsoft business solutions-Navision to the latest version in order to open the database.

The updates:

Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates.
- Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB867282)
- Security Update for Windows 2000 (KB885250)
- Security Update for Windows 2000 (KB888113)
- Security Update for Windows 2000 (KB890047)
- Security Update for Windows 2000 (KB873333)
- Security Update for Windows 2000 (KB885834)

I haven't restarted the server yet.

Anyone?

Comments

  • ArhontisArhontis Member Posts: 667
    Oops, a user has used a client of version 4.0 beta 2 and converted the database!!!!

    Anyone knows a way to bring that db back to its original version?

    I have noticed the databaseversionno field of $dbo$property table that has a value of 20 and it sould be 17, will that be all I have to change??????

    ](*,) ](*,) ](*,) ](*,)
  • SbhatSbhat Member Posts: 301
    Make a backup and restore the backup in your original version.

    SB.
  • ArhontisArhontis Member Posts: 667
    Hi,

    You mean a backup without the applications objects?

    Like:

    1. Backup from within Navision only the data.
    2. Get the fobs of all the objects.
    3. Drop the database.
    4. Create a new database.
    5. Update the database with the fobs.
    6. Restore the data.

    Am I thinking it right?
  • FeldballeFeldballe Member Posts: 26
    Hello Arhonis.

    You might be right about changing the versionnumber. You should take a look at this http://www.mibuso.com/forum/viewtopic.php?t=1544

    If that doesn't work you could allways restore the latest SQL-backup
  • ArhontisArhontis Member Posts: 667
    Hi everyone,

    First of all I would like to thank the persons that replied to my problem.

    The outcome of the situation is that the changes of Navision 4.0 to the database are not trivial. I have made an analysis of the changes in the database schema and the data of the tables and the situation was not reversible.

    I have also contacted the MBS Support team and they recommended to bring back the latest backup and redo the work that was lost. I had a backup of a day earlier and the problem was not that critical.

    I had also asked the MBS Team if we could use Nav 4.0 client with the converted database, and they said that that concept would work, but it is a legal issue to use Nav 4.0 since it is not released in our country yet.

    Anyway, the transition from 3.70 to 4.0 is something to be afraid of!!!

    Beware!!! Nav4.0 is coming!!!!
  • SorcererSorcerer Member Posts: 107
    have you any detailed information, what things have been changed / transformed by navision 4.0 in sql?
  • ArhontisArhontis Member Posts: 667
    Hi,

    Nope, no details (official), but I could make you an sql schema compare with my junk database and my productive and send you the results. It is a time and CPU consuming task (with SQL Compare v.2.03) and I can't do it during office hours, but only at night.

    As far as I remember, the changes is:

    One new table related to the main menu (left menu in Nav 4.0).
    Changes to the structure of IVIEW, Session view object.
    Changes to the structure of the Permission table.

    As far for the data changes in system tables is not easy to find them. It surely updates the extra fields that creates, and the table dbpropery.
  • geri79geri79 Member Posts: 105
    xx
    geri
Sign In or Register to comment.