Cluster Service Does Not Remove File Share Entries from LANMANSERVER

Article translations Article translations
Article ID: 302829 - View products that this article applies to.
This article was previously published under Q302829
Expand all | Collapse all

SYMPTOMS

The Cluster service may not remove all file share entries from the LANMANSERVER key during shutdown if there is a large number of shares. This may cause problems when you next start the computer, depending on the size of the SYSTEM hive. The SYSTEM hive is where the LANMANSERVER key is located. The following log may be generated in the Event log for each value that is left in the key:

Event Type: Warning
Event Source: Server
Event Category: None
Event ID: 2511

Description:
The server service was unable to recreate the share user12604 because the directory r:\users\user12604 no longer exists. Please run "net share user12604 /delete" to delete the share, or recreate the directory r:\users\user12604.

If the node is running Windows 2000, the computer may fail to start, and you receive the following error message the next time you restart it:
Windows 2000 could not start because the following file is missing or corrupt:

\WINNT\SYSTEM32\CONFIG\SYSTEMced startup options for Windows 2000, Press F8.

You can attempt to repair this file by starting Windows 2000 Setup by using the original Setup floppy disk or CD-ROM. Select 'r' at the first screen to start repair.

CAUSE

This behavior occurs because the Cluster service may not have enough time to remove all of the values from the LANMANSERVER key.

Services typically have 20,000 milliseconds (20 seconds) to shut down. If a service requires more time to shut down, it can be written to work with Service Control Manager (SCM) to extend the amount of time it requires to shut down. The Cluster Service does not adhere to this registry value. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
146092 How to Increase Shutdown Time For Services To Close Properly
The Cluster service normally does not require more than 20 seconds to shut down. Programs that are running on a cluster, such as Microsoft Exchange and Microsoft SQL Server, may require more than 20 seconds and work SCM to allow for longer times to shut down. Because the Cluster service shuts down in 20 seconds, it may not have enough time to remove all the values from the LANMANSERVER key.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For Windows 2000, if the SYSTEM hive grows beyond 10 to 12 megabytes (MB), the node may not be able to start. If you have a large enough amount of files shares on the cluster that it could cause the SYSTEM hive to grow to an unacceptably large size, use the following procedure to recover the node so that it will start. After you can start the node, migrate some of the file shares to another server to reduce the possible size of the SYSTEM hive, and to prevent this behavior from reoccurring.

For additional information, click the article number about the SYSTEM hive and Windows 2000 below to view the article about the SYSTEM hive and Windows 2000 in the Microsoft Knowledge Base:
269075 Error Message: Windows 2000 Could Not Start Because the Following File is Missing or Corrupt: \Winnt\System32\Config\Systemced
If the resolution in article Q269075 fails, use the following method:
  1. Install a parallel installation of Windows 2000 on the computer.

    Note: For the purposes of this article, the original installation is in C:\Winnt and the new parallel installation is Winnt.new. For additional information about how to perform a parallel installation, click the following article number to view the article in the Microsoft Knowledge Base:
    266465 How to perform a parallel installation of Windows 2000 or Windows Server 2003
  2. After you complete the parallel installation, log on locally to the computer in the parallel installation as "Administrator".
  3. Back up the original installation's copy of the SYSTEM hive by locating the C:\Winnt\System32\Config folder, and then backing up (or copying to another location) the file called "System" (no extension).

    Note: Verify that you are backing up the System file, not System.log.
  4. Start Registry Editor (Regedt32).
  5. Click the HKEY_LOCAL_MACHINE on Local Machine window to place it on top.
  6. Click the root folder HKEY_LOCAL_MACHINE.
  7. On the Registry menu, click Load Hive.
  8. Locate the SYSTEM hive by browsing to the C:\Winnt\System32\Config folder.
  9. Click the System file, and then click Open.

    Note: Verify that you are opening the System file (no extension) and not the System.log file.
  10. In the Key Name box, type OriginalInstall, and then click OK.

    Note: The name that you choose is not important, as long as it is unique to the subhive that is displayed.
  11. The loaded subhive named "OriginalInstall" is now listed. Double-click OriginalInstall to expand the branch.
  12. Click the Select key.
  13. Document the Current, Default, Failed, and LastKnownGood values.
  14. These numbers represent the CONTROLSETS that are listed above. Under normal circumstances, CONTROLSET001 and CONTROLSET002 are displayed. The Select key normally indicates that CONTROLSET001 is the Current and Default value. CONTROLSET002 is usually the LastKnownGood value. The Failed value often has a value of 0.For additional information about using the Select key and ControlSets, click the article number below to view the article in the Microsoft Knowledge Base:
    102984 REG: ControlSet\Select Subkey Entries
  15. Click the CONTROLSET that corresponds to the Failed value that you documented in step 13.
  16. On the Security menu, click Permissions.
  17. Click to clear the Allow inheritable Permissions from parent to propagate to this object check box.
  18. Click Remove.
  19. Remove the users and groups that are listed.
  20. Add the local Administrator account, and make sure that it has Full Control permissions.
  21. Click Advanced.
  22. Click to select the Reset Permissions on all child objects and enable propagation in inheritable permissions check box, and then click OK.
  23. In the Security dialog box, click Yes.
  24. In the Permissions dialog box, click OK.
  25. Delete the CONTROLSET that corresponds to the Failed set.

    Note: These steps are required to remove security on the hive so that you can delete it. Make sure that you have backed up the SYSTEM hive.
  26. Repeat steps 6 through 12 to delete the CONTROLSET that corresponds to the LastKnownGood value.
  27. Double-click the CONTROLSET that corresponds to the Current value.
  28. Under HKEY_LOCAL_MACHINE, click OriginalInstall.
  29. On the Registry menu, click Save Key, and then save the file to the desktop as System with no extension.

    Note: Saving the file removes any white space in the hive and reduces the size of the file.
  30. Make sure that OriginalInstall is still selected.
  31. On the Registry menu, click Unload Hive, and then click Yes for confirmation.
  32. Quit Regedt32.
  33. Open My Computer to browse to the C:\Winnt\System32\Config folder, and then rename the existing System file to System.org.
  34. Copy the System file from the desktop to C:\Winnt\System32\Config.
  35. Restart the computer and choose the original installation.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Properties

Article ID: 302829 - Last Review: February 28, 2007 - Revision: 4.4
APPLIES TO
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
Keywords: 
kbbug kbenv kberrmsg kbpending KB302829

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com