Dear Customer,
Based on my research, the issue can be caused by various factors. I suggest you test the following steps for this issue:
1. Please install the hotfix for the VSS as described in the article below and then check the status:
Event ID 21 is logged when you create a shadow copy backup on a Windows Server 2003-based computer
http://support.microsoft.com/kb/907875/en-us
A Volume Shadow Copy Service (VSS) update-2 package is available
http://support.microsoft.com/kb/887827/en-us
To work around this problem, remove the /3GB switch in the Boot.ini file to relieve pressure on pool memory.
2. Check HKEY_LOCAL_MACHINE\SYSTEM\Setup\FactoryPreInstallInProgress (should be 0 or missing)
- check reg keys:
[HKEY_CLASSES_ROOT\CLSID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}]@="VssEvent"
"AppID"="{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}"
[HKEY_CLASSES_ROOT\CLSID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}\InprocServer32] @="C:\\WINNT\\system32\\ES.DLL"
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}\ProgID]@="VssEvent.1"
[HKEY_CLASSES_ROOT\CLSID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}\VersionIndependentProgID]@="VssEvent"
3. Disable/remove any third-party shadow copy providers, specifically anything from Veritas or Symantec.
4. This is a limitation of Windows Server 2003. On a 32-bit system we expect to safely snap about 5TB at a time (i.e on a single volume). This assumes availability of about 200MB of non paged pool. You could do larger chunks of storage if you split it into smaller volumes. With 64-bit this isn’t an issue.
Comparison of 32-bit and 64-bit memory architecture for 64-bit editions of Windows XP and Windows Server 2003
http://support.microsoft.com/kb/294418/en-us
Best Regards
Tom Zhang, MCSE 2003
Tom Zhang – MSFT
