Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Dynamics GP 2013 Database Backup Issue

(0) ShareShare
ReportReport
Posted on by

2 out of 18 Dynamics GP 2013 databases had backup failure, with error below.

Failed to flush the commit table to disk in dbid ____ due to error 2601.

Some research done on this error showed that it's related to the Change Tracking enabled on the database.

I then tried to turn off the Change Tracking for these 2 databases, but it gave me another error. (I only managed to capture the below from the log).

Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 

In this case, what else can be done to remove the Change Tracking, or at least to get the backup fixed ? (There has been no backup for 2 months now).

-------------------------------------------

Additional details of the environment:

1. Database Server (Standalone)

   Windows Server 2012

   SQL Server 2012 SP1

-------------------------------------------

*This post is locked for comments

  • soma Profile Picture
    24,410 on at
    RE: Dynamics GP 2013 Database Backup Issue

    Please mark it as a verified, if your problem resolved. Because this will helps to some others who having the same problem.

  • Community Member Profile Picture
    on at
    RE: Dynamics GP 2013 Database Backup Issue

    Exactly... this is where i got stuck because i got no proof and explanation to the client... still owing them answers to the questions i posted earlier today..

  • soma Profile Picture
    24,410 on at
    RE: Dynamics GP 2013 Database Backup Issue

    Yes. I think so.

  • Community Member Profile Picture
    on at
    RE: Dynamics GP 2013 Database Backup Issue

    Hi Soma,

    The client environment is updated to SQL2012 SP1, so i think it may not be this bug after all ?

  • Suggested answer
    soma Profile Picture
    24,410 on at
    RE: Dynamics GP 2013 Database Backup Issue

    Ivan,

    I think this is a bug in SQL server with enable Change Tracking (Backup database may failure if we enable change tracking). That's why Microsoft has provided the cumulative updates/Hot fixes for this issue.

    Note: This error may occur in the below SQL server versions.

    Microsoft SQL Server 2008 Service Pack 1 (SP1), Microsoft SQL Server 2008 Service Pack 2 (SP2), Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012.

    Hope this helps!!!

  • Community Member Profile Picture
    on at
    RE: Dynamics GP 2013 Database Backup Issue

    Hi Nataraj,

    Thanks for the link.

    According to the article, for SQL2012 Cumulative Update 1 should already fix this error. This client environment is already updated to SP1 (11.0.3128), so it's supposed to be already fixed.

    And since it didn't, hence the post here to inquire the solution and cause of the issue.

    As at now, the issue has been resolved, pending now is the cause of the issue to revert to the client, and also on how to overcome this issue should this change tracking is required to be turned on. In other words, now that the environment is already in SQL2012 SP1, and to turn on the change tracking, would it cause the same issue yet again.

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Dynamics GP 2013 Database Backup Issue

    Ivan,

    I guess by applying hot-fix for the latest version resolves your case. please have a look on the below article

    support.microsoft.com/.../2603910  

  • soma Profile Picture
    24,410 on at
    RE: Dynamics GP 2013 Database Backup Issue

    Ivan,

    I will discuss with my DB team and let you know about the Change Tracking.

    Note: Please mark it as a verified, if your issue resolved, . Because this will helps to some others who having the same problem.

  • Community Member Profile Picture
    on at
    RE: Dynamics GP 2013 Database Backup Issue

    Hi Soma,

    Disabling change tracking did help, even though the disable process was quite tedious, going through each and every table.

    Nevertheless, the backup is now working properly, but the next question would be why change tracking could cause such error in the first place, and how to overcome this should change tracking is required to be turned on.

  • Verified answer
    soma Profile Picture
    24,410 on at
    RE: Dynamics GP 2013 Database Backup Issue

    Try to disable the change tracking for all the database and then run the backup again.

    For your reference, have a look on the below link.

    community.dynamics.com/.../attention-sql-backup-failed.aspx

    Hope this helps!!!

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Featured topics

Product updates

Dynamics 365 release plans