keey having database corruption error

scott

I am continously having the following error:

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.
Warning! This error MUST be corrected before you can continue. Do not use any type of disk utilities on the database. AND SO ON...

1) If I backup the database then restore it to a new blank database, the error will go away for a few days.
2) Navision's Maximum Database test reports no problems.
3) The database is 3GB and splited onto 5 hard drives.
4) It is Navision Financials 2.5 C/Side.

Can anyone help?
Thanks for your time.

bthor

We have hade the same problem. But after changing the hardware the problem disappeared.

horrigan

Are the 5 different files on 5 different PHYSICAL hard drives or 5 different partitions on less than 5 hard drives.

Performance suffers when you split a Navision DB amongst multiple files on a single hard drive. That could be the source of the problem...

scott

The database consists of 5 different files on 5 DIFFERENT hard drives.

Lars_Westman

Do You have a write back cache enabled in Your adapter? If so turn it off. You must not use any write cache.

If this isn't Your problem there should be some error on some of Your disks. Also check that You have the latest frimware to Your adapter.

//Lars

[This message has been edited by laweume (edited 21-03-2001).]

TheDoubleH

Do You use Small Buisness Server????

I had a client, with a similar problem. After reinstaling the server with "real" NT, the problem was gone...

Kind regards

Henrik Helgesen

Samsonite

We had exactly the same problem at one customer..., every time it occured we took a backup and restored into a new database.
But after a few days or sometimes weeks, the error was back again.
We tried everything, started with changing HD, then RAM modules....finally after 4 month the whole server...
After that no more problems occured.
So my guess is also HW ...

markborges

Disabling write back cache worked perfectly for me!

Savatage

I hope they haven't been waiting 5 years for that answer

- wow 5 hd's for 3gb - hope it wasn't a raid 5