Microsoft KB Archive/934160

From BetaArchive Wiki
Knowledge Base


Article ID: 934160

Article Last Modified on 11/5/2007



APPLIES TO

  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Starter
  • Microsoft Systems Management Server 2003



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista


SYMPTOMS

In Windows Vista, after you create a subfolder in a shared folder on a network, you receive the following error message when you try to rename the new subfolder:

The SharedFolderName folder does not exist. The file may have been moved or deleted.

Do you want to create it?

The message incorrectly states that the shared folder does not exist.

Additionally, if you save a file to the shared folder on a network, you may receive the following error message:

There has been a network or file permission error. The network connection may be lost.

CAUSE

This issue occurs if the following conditions are true:

  • Windows Vista was deployed to the computer from an image by using the Microsoft Systems Management Server (SMS) 2003 Operating System Deployment (OSD) Feature Pack Update.
  • The client-side cache database that the Offline Files feature uses was corrupted when Windows Vista was deployed.


WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, add the FormatDatabase registry entry to the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters


Then, set the FormatDatabase registry entry to 1.

To do this, follow these steps:

  1. Click Start[GRAPHIC: Start button], type regedit in the Start Search box, and then click regedit in the Programs list.

    [GRAPHIC: User Account Control permission ] If you are prompted for an administrator password or confirmation, type your password or click Continue.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc\Parameters

    Note If the Parameters subkey does not exist, create it. To do this, follow these steps:

    1. Click the following registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Csc

    2. On the Edit menu, point to New, and then click Key.
    3. Type Parameters, and then press ENTER.
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type FormatDatabase, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type 1 in the Value data box, and then click OK.
  7. Exit Registry Editor, and then restart the computer.

Scenarios in which to apply the workaround

Apply this workaround in scenarios that resemble the following:

  • For an image that you are currently deploying, apply this workaround in a custom action in the state restore phase. This procedure requires that you restart the computer.
  • For an image that you have already deployed, apply this workaround. This procedure requires that you restart the computer.
  • For a new image, apply this workaround and then restart the computer. Create the image after you restart the computer and before you configure network connections.
  • You can also apply this workaround to the registry of a Microsoft Windows Imaging Format (WIM) image file. To do this, use the ImageX.exe tool that is included in the Windows Automated Installation Kit (AIK). For more information about Windows AIK, visit the following Microsoft Web site:

    For more information about the ImageX.exe tool and WIM image format in Windows Vista, visit the following Microsoft Web site:

    One possible advantage of using this procedure is that you do not have to create a new image. Additionally, you do not have to restart the computer.


MORE INFORMATION

For more information about the SMS 2003 OSD Feature Pack Update, visit the following Microsoft Web site:

Keywords: kbtshoot kbprb kbexpertiseinter KB934160