Microsoft Dynamics NAV (Archived)

Navision 2009 Backup Fails

(0) Share

Report

Posted on by Community Member

Hi All,

I'm facing an issue with the navison 2009 backup, i keep getting this error.

Any ideas how to solve the above error?

Thank you.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Verified answer

Ashwini Tripathi 4,624 on at

Like (0)

Report
Copy link

Link copied!

Seems some data which is breaking the integrity of database. I think checking Page will be helpful.

ALTER DATABASE [MY_Database] SET PAGE_VERIFY CHECKSUM WITH NO_WAIT;

But will sugest to read in detail before performing any action.

check this link if it may give idea about what else you can do. msdn.microsoft.com/.../bb522682.aspx

Also will suggest to check even log where you can get more details where to concentrate.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report
Copy link

Link copied!

Most likely you have database integrity failure. In SQL Management Studio, execute this query:

DBCC CHECKDB (DatabaseName);

GO

and publish the result here in a screenshot.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Alexander,

when i run the command above, i get this message error:

Object ID 642309548, index ID 1, partition ID 72057594901168128, alloc unit ID 72057594920632320 (type In-row data): Page (3:159620) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 2

Table error: Object ID 642309548, index ID 1, partition ID 72057594901168128, alloc unit ID 72057594920632320 (type In-row data), page (3:159620). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270729 and -4.

Msg 8928, Level 16, State 1, Line 2

Object ID 642309548, index ID 1, partition ID 72057594901168128, alloc unit ID 72057594920632320 (type In-row data): Page (3:159621) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 2

Table error: Object ID 642309548, index ID 1, partition ID 72057594901168128, alloc unit ID 72057594920632320 (type In-row data), page (3:159621). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270729 and -4.

There are 10680 rows in 681 pages for object "access$Vendor Ledger Entry".

CHECKDB found 0 allocation errors and 4 consistency errors in table 'access$Vendor Ledger Entry' (object ID 642309548)

And at the end of log:

CHECKDB found 0 allocation errors and 4 consistency errors in database 'dbase'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbase).

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately, there is a problem with clustered index (index ID 1). Best option is to restore a valid backup (use RESTORE VERIFYONLY msdn.microsoft.com/.../ms188902.aspx to check if the backup you are restoring is consistent). Also, examine event logs and sql errorlogs to learn from where such error came from; usually it is a hardware issue.

If you do not have your backup in place, there are three options:

1. Try taking full backup and restoring a database from that back. Run checkdb, sometimes errors go away after that. If so, use it as your live database further.

2. Try modifying the files of the database manually in hex editor in the places where there is the error. Quite challenging task, if you are not SQL person I'd recommend you not to do it yourself and refer to the help of some pros.

3. Take a backup and run database repair and pray that it would be ok; if you get lucky, you will have your database repaired without data loss (use checkdb with repair_allow_data_loss parameter). Check the result for data availability.

For now, try running

select * from (yourdatabase) - perhaps it would give you more informative message (post it here).

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

HI ashwini,

Thank for the reply.

i followed the steps below and everything went well :)

--use master;

--alter database [MY_Database] set emergency;

--ALTER DATABASE [MY_Database] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

--dbcc checkdb ('MY_Database', repair_allow_data_loss)

--alter database [MY_Database] set multi_user

--ALTER DATABASE [MY_Database] SET PAGE_VERIFY CHECKSUM WITH NO_WAIT

BR,

Youssef

Was this reply helpful? Yes No