Data Protection Manager SP1 throws error 0x80004002 or ID 207
Filed Under (Data Protection Manager) by Just An Admin on 23-12-2008
After installing Service Pack 1 for Data Protection Manager 2007 and upgrading each of the agents on my servers, most of my protected servers would fail to back up with one of the following errors:
- Replica is inconsistent
- Recovery point creation failed
Only a hand full of jobs completed successfully. Consistency checks would fail also.
Looking more closely at the messages in DPM, you may see errors like:
- ID 207 Details: No such interface supported (0x80004002)
Some searching provided the answers. It seems that Service Pack 1 has a minor flaw as it does not register the VSS Writer completely, specifically the IVssDifferentialSoftwareSnapshotMgmt3 interface.
To fix run the following command on the DPM server:
regsvr32 %windir%\System32\vss_ps.dll
Update 30/12/2008: It was brought to my attention that you may need to restart the Volume Shadow Copy service afterwards.
If this does not fix your problem, you may look at article KB940032 – http://support.microsoft.com/default.aspx?scid=kb;EN-US;940032
Perfect… Just saved the day 🙂
Thumbs up
All was fine until I installed SP1. Now I get replicas inconsistent for most of my servers. When I run the consistency check, they are OK for about 5 minutes. Oh why oh why did I install this SP? I ran the command to register the vss, but no luck in fixing my issue. I an getting ID 112.
Hi,
Thanks for posting this. Feel free to ping me – looking forward to hearing you.
Balaji
@Marc Abbaticchio:
This is a long shot, but could it be that a virus scanner is messing things up? Could you disable the virus scanner on the protected server AND on the DPM server for just a short test and see if this fixes the problem?
If it does, exclude the DPM Agent install directory from being scanned.
I did disable the AV completely. Even went as far as deleting all replicas and recivery points on disk. In the end, I went back to the original version that I had, restored the DB, re-installed all agents back to original version, and all is well again. Maybe SP2 will be a charm for me since SP1 did not really add any functionality that I need at this point.
I must say that this was a good drill for me in learning first hand how to re-install DPM and restore the database. It just took FOREVER to get everything done.
Thanks for finding this. This fixed my issue as well.
I also have had problems with SP 1, and ID 112. Seems like random files on my file server suddenly creates an error during a sync. Tried the above fixes, and its a no go. Everything was fine before SP1. Looks like I”m “down grading”.
I had to down grade and it is working fine as it was before.
Hey Marc;
I just talked with Microsoft Support and they said sometime this month, they will have a roll up package to fix the SP 1 issue we are having ID 112.
Thanks for inquiring with Microsoft. At least they are aware of the issues. I just do not understand how they can release SP1 with such obvious issues. I guess we will see what happens when the rollup in released. Thanks again E.J.
Great news, E.J. I agree that SP1 release is somehwat questionable
Microsoft Australia posted this fix, with some additional information: http://blogs.technet.com/askcore/archive/2008/12/24/error-207-no-such-interface-supported-0x80004002-after-installing-dpm-sp1.aspx
@Marc A: I don’t know if you are still open for DPM SP1, but the error ID 112 you mentioned in your first comment may have been fixed:
http://www.jadota.com/2009/01/hotfix-replica-is-inconsistent-error-with-id-112-0x8007007b-with-dpm-2007-sp1-on-a-windows-server-2003-x64/
Wow, that describes my problem exactly. And I am running a 64bit Server. Maybe I will give it another shot. Thank you for pointing this out for me.