• Symptom: On Windows Server 2003 (SBS, Standard, etc.), error 0x8004230f (“The shadow copy provider had an unexpected error”) occurs when running NTBackup and/or when the Volume Shadow Copy scheduled task(s) run.

    Cause: This error can occur If certain VSS DLLs are not registered properly, or if something
    is wrong with the VSS provider.  This issue is often associated with the installation of new hard drives, especially when deploying previously-created hard drive images to them.

    Resolution:

    1. Apply the latest VSS package (KB940349) on the server from Microsoft here, and reboot the server.
    2. Re-register the VSS related DLLs by running the following commands (a batch file would probably be a good idea here):
    3. 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 /i swprv.dll
      regsvr32 /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

      NOTE: The command in the final line may fail– this is normal.

    4. Delete the following registry key (after exporting for a backup):
    5. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume]

    6. Reboot the system, and the “VOLUME” key will be recreated, hopefully fixing the issue.

    Tags: , , , , , ,

  • Symptom: You schedule a chkdsk before rebooting a Windows machine (can be Windows XP or any flavor of Server 2003, possibly others as well) it appears to run through the chkdsk successfully, then reboots again and continues the cycle, continuously running chkdsks on startup, but never getting up to Windows.  Sometimes the Windows splash screen shows, sometimes not.

    Power down and cold boot doesn’t change the behavior.  Attempting to boot into Safe Mode also fails with the same behavior.

    Cause: Unknown, but probably due to a failing chkdsk operation not removing the BootExecute reg value.

    Resolution (some steps borrowed from http://windowsxp.mvps.org/peboot.htm and http://support.microsoft.com/kb/158675):

    1. Create a BartPE boot CD.  You will need the install disk for your exact edition of Windows to do this.
    2. Insert the BartPE CD into the drive, and boot the system from the CD. Once the file loading phase is over, the Bart PE desktop will be visible.
    3. Type Regedit.exe in the prompt, and press Enter. Select the HKEY_LOCAL_MACHINE hive.
    4. From the File menu, choose the Load Hive option. Browse to your Windows installation drive, for example the following location:
    5. C:\Windows\System32\Config\

    6. Select the file named SYSTEM (the file without any extensions), and click Open
    7. Type a name for the hive that you’ve loaded now. (Example: MyHive)
    8. Now the SYSTEM hive is loaded, and present under the HKEY_LOCAL_COMPUTER base hive.
    9. In order to fix the BootExecute value in the loaded hive, navigate to the following location:
    10. HKEY_LOCAL_COMPUTER \ MyHive \ CurrentControlSet \ Control \ Session Manager

    11. Double-click BootExecute and change it’s value to:
    12. autocheck autochk *

    13. After entering the correct data, you MUST unload the Hive. To do so, select MyHive branch, and then in the File menu, choose Unload Hive. It’s important to note that you’ll need to select the MyHive branch first, before unloading it.
    14. Quit BartPE and restart Windows.  The machine should now boot up normally, skipping the chkdsk.

    Tags: , , , , , , ,

   

Recent Comments

  • You actually can delete the PublishAddresses registry key. T...
  • Thanks - One step along the road to getting Vista and XP ...