DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent.  (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem.  In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total).  All of the SQL environment is backing up fine except for a SQL Cluster Application.  This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them.  The other 5 SQL instances in the cluster are backing up fine; only one instance is failing.  The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:

Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs = 4.
 If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
 The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)
 More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
 Create a recovery point...
Resolution: To dismiss the alert, click below
 Inactivate alert

I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine).  The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior to when the failures started to occur.  However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem.  We are running SQL 2008 SP2 (version 10.0.4000.0) on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.

One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):

Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.

Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>


the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.

Problem Details:
&lt;DpmWriterEvent&gt;&lt;__System&gt;&lt;ID&gt;30&lt;/ID&gt;&lt;Seq&gt;1833&lt;/Seq&gt;&lt;TimeCreated&gt;6/13/2011 5:09:12 AM&lt;/TimeCreated&gt;&lt;Source&gt;f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp&lt;/Source&gt;&lt;Line&gt;815&lt;/Line&gt;&lt;HasError&gt;True&lt;/HasError&gt;&lt;/__System&gt;&lt;DetailedCode&gt;-2147212300&lt;/DetailedCode&gt;&lt;/DpmWriterEvent&gt;
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
  </EventData>
</Event>

Any help would be greatly appreciated!

June 13th, 2011 11:30pm

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem.  If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers" and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.

I would also like to add that the databases on this node that will not backup are running fine.  They run hundreds of transactions daily so we know SQL itself is OK.  Even though it is a busy SQL Server, there is plenty of available resources as the SQL buffer and memory counters show the node is not under durress.

  • Marked as answer by jmathe84 Wednesday, June 15, 2011 8:35 PM
  • Unmarked as answer by jmathe84 Wednesday, June 15, 2011 8:35 PM
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2011 12:36pm

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem.  If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers" and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.

I would also like to add that the databases on this node that will not backup are running fine.  They run hundreds of transactions daily so we know SQL itself is OK.  Even though it is a busy SQL Server, there is plenty of available resources as the SQL buffer and memory counters show the node is not under durress.

June 14th, 2011 3:36pm

Found the solution to the issue in case anyone else runs into this error in DPM 2010.  The NT AUTHORITY\System account must have sysadmin privleges for direct SQL backups to run successfully.  Somehow, these permissions had fallen out of SQL for this specific instance in the cluster while the rest of them still had the correct permissions set.  As soon as I added SYSTEM back as a sysadmin, the backups worked fine.
  • Marked as answer by jmathe84 Wednesday, June 15, 2011 8:38 PM
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2011 8:38pm

Found the solution to the issue in case anyone else runs into this error in DPM 2010.  The NT AUTHORITY\System account must have sysadmin privleges for direct SQL backups to run successfully.  Somehow, these permissions had fallen out of SQL for this specific instance in the cluster while the rest of them still had the correct permissions set.  As soon as I added SYSTEM back as a sysadmin, the backups worked fine.
June 15th, 2011 11:38pm

Good solution! and works fine.

When creating new instanse in SQL 2012 do not forget to modify NT AUTHORITY\System permission within sql using Management Studio. See print screen

Hope this problem solved in DPM 2012.... -:)

Shakha Mirza add Pic SYSADMIN

  • Proposed as answer by dphuk Wednesday, April 24, 2013 8:17 AM
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2012 8:36am

Good solution! and works fine.

When creating new instanse in SQL 2012 do not forget to modify NT AUTHORITY\System permission within sql using Management Studio. See print screen

Hope this problem solved in DPM 2012.... -:)

Shakha Mirza add Pic SYSADMIN

July 26th, 2012 11:36am

Thank you :)

Free Windows Admin Tool Kit Click here and download it now
April 24th, 2013 11:17am

Thank you. I was struggling for weeks and finally its working.....
June 28th, 2013 7:31pm

Good solution! and works fine.

When creating new instanse in SQL 2012 do not forget to modify NT AUTHORITY\System permission within sql using Management Studio. See print screen

Hope this problem solved in DPM 2012.... -:)


It isn't :(    (DPM 2012 SP1)

Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2013 9:08am

Thank you.
May 13th, 2014 9:11pm

Thanks dude, I couldnt backup FIMSynchronizationService DB on our DirSync server.. now its working..
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2014 12:57pm

I had the same error code. Before, the System account's "sysadmin" was unchecked. After checking the box, voila. Thanks.
September 10th, 2015 12:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics