sitg
asked on
Navision error
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
server was crashed due to hardware failure
Did you reinstall the server? SQL Server included? If so you may miss some SQL Server login or permissions.
Check in the database if all users are properly matched with the expected logins.
Check in the database if all users are properly matched with the expected logins.
ASKER
I got the attached error when run DBCC checkDB()
nav-odbc-error.txt
nav-odbc-error.txt
When did you perform the backup? Hope wasn't during the server crash.
ASKER
actually DB and rest servers managed by other team and we are not able to restore database from backup because all backup compressed file is corrupted
You have a very bad scenario there. When was the last known good backups?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Not sure if you still want any advise on this matter. The Navision classic does have a feature that at least gives the user some idea as to what the issue is in certain data corruption/inconsitenance issue. At that point, the user can then read and hopefully patch the data.
Steps to run feature:
1) Login to Navision.
2) Press Alt + F. Then press B. Then press T.
3) You will see a form called Test Database.
4) Click on the Radio button Maximum.
5) Click on the tab Options.
6) Then select the radio button File.
7) Select a file location and file name.
8) Click the OK button and it will run for the database.
9) Assuming that there are drastic errors, you should be able to see the text file with issues.
If you get too many error messages, you may want to consider patching the database from the SQL. MS SQL is not my expertise so you will need some other expert to assist.
Steps to run feature:
1) Login to Navision.
2) Press Alt + F. Then press B. Then press T.
3) You will see a form called Test Database.
4) Click on the Radio button Maximum.
5) Click on the tab Options.
6) Then select the radio button File.
7) Select a file location and file name.
8) Click the OK button and it will run for the database.
9) Assuming that there are drastic errors, you should be able to see the text file with issues.
If you get too many error messages, you may want to consider patching the database from the SQL. MS SQL is not my expertise so you will need some other expert to assist.
It was a server migration? A version upgrade? The database was corrupt or you just lost the database?