Article ID: 967509 - View products that this article applies to.
You install Microsoft System Center Data Protection Manager (DPM) 2007 Service Pack 1 (SP1) on a system. However, when you perform various operations, you receive the following error message:
An Unexpected error occurred during a VSS operation.
ID 207 Details: No such interface supported (0x80004002)
Recommended action: Retry the operation
This problem can occur when you try to create new Protection Groups, run Consistency Checks, or perform other DPM operations.
Additionally, the following error is logged in the MSDPMCurr.errlog file:
GetDifferentialSoftwareSnapshotMgmt3Interface () failed: (0x80004002).
This error occurs when the IVssDifferentialSoftwareSnapshotMgmt3 interface is registered incorrectly with Volume Shadow Copy Components.
To have us fix this problem for you, go to the "Fix it for me" section. To fix this problem yourself, go to the "Let me fix it myself" section.
To fix this problem automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Fix this problem
Microsoft Fix it 50260
Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Next, go to the "Did this fix the problem?" section.
To resolve this problem, follow these steps:
Note You have to restart the Volume Shadow Copy Service after you perform this method.
If this method does not resolve this issue, follow the steps that are described in the resolution section of KB 940032:
(http://support.microsoft.com/kb/940032/ )Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service
Note If you use the method described in KB 940032 in Windows Server 2008, make sure that you perform the steps at a command prompt with elevated credentials. For example, use administrator credentials when you run the command prompt.
Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support
Article ID: 967509 - Last Review: July 15, 2009 - Revision: 3.0