Data Protection Manager 2010 error ID 30140 Details: Internal error code: 0x80990D11

I get the following error in DPM Management console on a SQL2000 server that is protected with DPM 2010

Affected area:           

Occurred since:          8/20/2011 4:01:13 AM

Description:    Recovery point creation jobs for SQL Server 2000 database ?????? on ???? have been failing. The number of failed recovery point creation jobs = 3.

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)

DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for  SQL Server 2000 database ???? since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)

More information

Recommended action:           If you see this failure as part of a backup job, then in the Protection task area, select the SQL Server database and click Create recovery point. Choose express full backup. Alternately, you can wait for the next scheduled express full backup to run.

If this failure occurs as part of a recovery job, then try to recover from another point in time.

Review the Application Event Viewer logs on the computer running SQL Server for more details.

Ensure that this database is not already protected by another backup application.

Create a recovery point…

Resolution:     To dismiss the alert, click below

Inactivate alert

Solution:

DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for SQL Server 2005 database database <name database> since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)

Resolution: It seemed that the problem was that there were also backups performed straight from the SQL Management Studio. Stopping these backups resolved the issue. See also http://support.microsoft.com/kb/970642