Hi, I am are currently involved in a Navision 3.60 implementation and received the following error message on the development database. “There is a corrupted area in the database. This type of error occurs if the database file is changed by another program or if the device driver does not function correctly.” When I reopened the Development database the error did not appear again. I have run a maximum test on the database which returns with no errors. Any ideas what causes this error message? Michele
im not sure, but it might be a corrupt area on the disk. but be safe please take a backup / export the objects. regards Prince
Is it a SQL or C/Side database? I have come across similar errors when the SQL server goes down, it doesn’t actually kick you out of Navision but I did get a Navision error message rather than one of those ghastly SQL things. cheers, Dan.
No, it is not a SQL database but the Navision propriatary database. It is occuring on Navision 3.60. I have performed a disk scan on the server but that has come up with no errors. Regards, Michele
Hi Michele, even if it is a physical disk error, it is very unlikely that you will be able to find the error using any disk utility software. The error can source from a number of areas. 1/ The most common is a network error. If you have a network card or bad cable that is causing a lot of bad packets to be sent between the Navision client and server. Eventually one may slip pass through the error checking and check sums, and pass bad data to the Hard disk that is then written as though it was a bad sector. 2/ Bad SCSI cables. With SCSI drive, you MUST (read that as MUST MUST MUST) terminators at each end of the cable. It is amazing how many people ignore this. SCSI will work with the terminators in the wrng position, but will be unreliable. Eventually, much as the network case, bad data will be written to the drives. 3/ Actual faulty hard drives. This is rare, but does happen. To try to narrow down the problem, try running multiple Navision backups simultaneously (using NAvision fbk backup). This will put a lot af network traffic on the server card, and may help you to locate the issue. BY the way, in my experience, when it was a network card, it was always a client, not the server.