Friday, April 25, 2008

Are facing VSS crunch in NTBackup after SP2 upgradation in Windows Server 2003?

NTBackup is hanging in “Preparing to backup using shadow copy”

This is a type of problem occurring facing after the Service Pack Upgradation in Windows Server 2003.

SYMPTOMS

On a Microsoft Windows Server 2003-based computer that is running the Volume Shadow Copy Service (VSS), you experience one of the following symptoms: When you perform a backup operation by using the NTBackup tool, will hang in “Preparing to backup using Shadow copy” and the following event is logged in the Application log:

Event Type: Error
Event Source: NTBackup
Event ID: 8019
Description: End Operation: Warnings or errors were encountered. Consult the backup report for more details.



1. Note If you view the backup log file, the following information is displayed:

Error returned while creating the volume shadow copy: 0xffffffff

2. If you access the properties of a volume and then click Shadow Copies, you receive one of the following error messages:

Error 0x8004230F: The shadow copy provider had an unexpected error

3. While trying to process the specified operation you will receive following:

Error 0x80004002: No such interface supported



CAUSE

This issue occurs because the VSS system files are not registered.
Back to the top

RESOLUTION

To resolve this issue, follow these

Step 1.

Click Start > click Run > type regedit.exe and then click OK
In registry editor check the content in
HKEY_L _M/System/Current control set/Control/Backupandrestore/Nototake backup
Delete unwanted junk entries included in the given path

Steps 2.

Click Start > click Run, type cmd, and then click OK.

Step 3.

In Command prompt go to the path %windir%\system32
Then type the following commands at a command prompt. Press ENTER

• Net stop vss
• Net stop swprv
• regsvr32 ole32.dll
• regsvr32 oleaut32.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 (This command may not run successfully).

Step 4.

Perform a backup operation to verify that the issue is resolved.

How you will expertise in Windows Server 2003?

I would like to share sometechnical documnts with you all,

1.  Exporting and Importing of Active Directory Object

2.  Troubleshooting Group Policy in Microsoft® Windows® Server

3.  ACTIVE DIRECTORY – DNS – FSMO – GROUP POLICY_interview

4.  FSMO- Flexible Single Master Operations_interview