web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / We are having problem ...
Microsoft Dynamics SL (Archived)

We are having problem backing up one of our Dynamics SL database.

(0) ShareShare
ReportReport
Posted on by Community Member

We are having problem backing up one of our Dynamics SL database.

Here's the error message:

ERROR CODE [30:325]: Error encountered during backup. Error: [Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (4061067). Failed to flush the commit table to disk in dbid 17 due to error 2601. Check the errorlog for more information. A nonrecoverable I/O error occurred on file "e0627f3e-9170-4523-b0f1-62a3092e45df:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). BACKUP DATABASE is terminating abnormally. The statement has been terminated. An exception occurred while executing a Transact-SQL statement or batch.]

Any help will be appreciated.

Thank You

Kalban

*This post is locked for comments

I have the same question (0)
  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    Is this a back using CommVault or another product?

  • Community Member Profile Picture
    Community Member on at

    CommVault

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    The first thing I would do is see if a backup can be taken from SSMS. I suspect CommVault is the culprit here.

  • Community Member Profile Picture
    Community Member on at

    We had tried that previously, and again just moments ago, but the attempt in SQL Server Management Studio (SSMS) failed also. CommVault is working for all the other databases on the server.

    The error message received from the SSMS attempt is:

    Failed to flush the commit table to disk in dbid 17 due to error 2601. Check the errorlog for more information. (Microsoft SQL Server, Error: 3999)

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    It reminds me of the Change Tracking issue in some versions of SQL Server. Is Management Reporter running against that database?

    There is this: support.microsoft.com/.../2603910

  • Community Member Profile Picture
    Community Member on at

    No, Management Reporter is not running against this particular database.

    Management Reporter Integration failed when we were running against databases that are in the same System database as this database is.  I have a case open with Microsoft regarding the MR integration.

  • Community Member Profile Picture
    Community Member on at

    Hi Butch, I'm curious to know why you asked if MR was running. We have just encountered this error. And we installed MR several weeks ago. The only occurring on one app db, sys is fine and the other db that MR hasn't been run against is fine.

    Thanks

    Renee

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    Renee,

    The MR DDM uses change tracking to keep the data mart in sync with the GL.

    Based on the link above and the fact that you recently installed MR, I'd take a look down that path.

    ...b

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans