Serious Problem!

Angelo

When I filter for Posted Sales Invoice (press F5) and filter some Invoice No(F7),then there is error :

The following SQL Server error(s) occured while accessing the Sales Invoice Line Table :
601,"42000",[Microsoft][ODBC SQL SERVER DRIVER][SQL SERVER]Could not continue scan with NOLOCK due to Data Movement

When I close Posted Sales Invoice form,there is error again :
"Sales Invoice Header cannot modified in this form"

Then,I try to see the SQL 2000 Server and make query for show data from table [Sales Invoice Line],there is error in SQL : Dataerror(Cyclic Redundancy check).

I want to ask,why the error appear?and our client data is damage(especially in G/L)for exam,Account in Cart of Account show balance $200 but when we drilldown there is only data for $130,Why this happen?
We have to restore backup data,but the error appear again and again.Please help me soon....

kriki

It seems that the SIFT-table on SQL has gone nuts. To calculate the total of a SIFT-field, SQL has a special table so he can read only 1 record to have the information. This can be fixed by disabling the indexes and then re-enabling them again.

BUT BEFORE STARTING WITH PREVIOUS THING:

The first thing is to stop the SQL,server, copy the SQL-files of the DB and restart the SQL-server
The second thing is to make a SQL-backup.

Until here it is for making sure you can go back to the original situation (first is to put back the original files that is faster, second would be restore SQL-backup)

The third thing you should try is to make a Navision backup. See if it works without errors. If this works, the best thing you can do is to restore it in a NEW DB. This should fix the SIFT-errors and also the other errors.

merana

Have you ever used any kind of the replications on your SQL Server database, maybe?
(because of that "cyclic redundancy check" error)

DenSter

Are you moving data around directly on SQL Server? Using any Stored Procedures? Writing data in other ways? Using DTS packages? SIFT tables don't just go crazy like that, there's always a good reason.

Ravi_Thakkar

Thanks for this post.
I am also facing the same issue.

Will you please, revert with reason and step towards the solution of such kind of error. ?

Thanks in advance.