SBS Server 2003 System State backup failing

Hi,

I am using NT Backup on an SBS 2003 server and lately when it goes to take a system state backup it fails right away.  When I look in the backup log on why it failed, I see the following error code:

"COM+ REGDB Writer" has reported an error 0x800423f4

Any assistance would be a great help.

Thanks

microsymplexAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

C3ConsultingCommented:
I found the following solution according to a tech support call to Microsoft:



"I had to call Microsoft for support... here are  the case notes.
 
 PROBLEM:Unable to Backup System State using NTbackup  
 RESOLUTION:-  
 
 Ran:- vssadmin list writers and could see all the writes but when tried  to  
 take system state backup, it failed with an error.
 
 Followed an internal article and tran
 
 Net stop vss
 
 Net stop swprv
 
 regsvr32 ole32.dll
 
 regsvr32 vss_ps.dll
 
 Vssvc /Register
 
 regsvr32 /i swprv.dll
 
 regsvr32 /i eventcls.dll
 
 regsvr32 es.dll
 
 regsvr32 stdprov.dll
 
 regsvr32 vssui.dll
 
 regsvr32 msxml.dll
 
 regsvr32 msxml3.dll
 
 regsvr32 msxml4.dll
 
 Reinstalled COM+
 
   
 
 1. Backup and then delete HKLM\Software\Microsoft\COM3
 
 2. Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll.  
 
 3. Boot to normal mode and in Control Panel, open the Add or Remove  Programs  
 tool,  
 
 and then open the Add/Remove Windows Components tool.  
 
 Ã Checked DCOMCNFG and red down arrow on Computer
 
 2.  Distributed Transaction coordinator is running and started.  
 
 3.  Followed Q315296 How to clean up a damaged COM+ catalog
 
 4.   Errored again with:   "sub-component Com+ raised an exception"  0x8007041b
 
 5.   Stopped the System event Notification serivce and attempted to  
 reinstall Com+ again  
 
 6.   This time it was successful
 
 7.    Created a Shadow Copy on C and that was successful  
 
 8.    Attempted the System State backup of the server to C   Successful"
0
Shreedhar EtteCommented:
Hi,

DO NOT FOLLOW THE ABOVE STEP ON AN EXCHANGE SERVER. IT IS HARD REBUILD OF COM+.

IF YOU DO, YOU WILL HAVE TO REINSTALL EXCHANGE.

First try the Soft Rebuild of the COM+ by following the below steps:
1.Go into control panel and reset the com configuration.

a. In control panel click "add remove programs".
b. Click "Add remove windows components".
c. Click the "Next" button (windows will re-initialize the COM
configuration).

2. Look in "Component Services" MMC and make sure that the MS Shadow Copy Provider
does not show up as a COM+ application. The software provider should NOT show up
in Component Services on Windows 2003 and above. If it is, you will have trouble
initializing the VSS coordinator and provider instances.

a. In the Component Services MMC, navigate to "Component Services\My
Computer\COM+ Applications\"
b. View the properties of the "MS Software Shadow Copy Provider" if it exists.
In the "advanced" tab, uncheck the "Disable deletion" checkbox and then delete the
"MS Software Shadow Copy Provider" from COM+ Applications.

3. VSS biniries registartion:
net stop "System Event Notification"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop Vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s Vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
net start "COM+ Event System"

4. Disable VSS tracing if it is enabled.
887013 How to enable the Volume Shadow Copy service's debug tracing features in
Microsoft Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887013 

5. Reboot the system to bring all writers into a stable state.

After that perform the System State Backup of the server.

I hope this helps,
Shree
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
microsymplexAuthor Commented:
Thanks it worked
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.