Select the product you need help with
System may not start when creating a large number of logical units and volumesArticle ID: 277222 - View products that this article applies to. This article was previously published under Q277222 On This PageSYMPTOMS
If your system has a large number of logical unit numbers (LUNs) and volumes (over 700), when you restart Windows 2000 Server or Windows Server 2003, you may receive one of the following error messages:
Windows 2000 could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced startup options for Windows 2000, Press F8. You can attempt to repair this file by starting Windows 2000 Serveror Windows Server 2003 Setup using the original Setup floppy disk or CD-ROM. Select 'r' at the first screen to start repair. Windows 2000 could not start because of an error in the software. Please report this problem as Loader Error 3. You can attempt to repair this file by starting Windows 2000 Serveror Windows Server 2003 Setup using the original Setup floppy disk or CD-ROM. Select 'r' at the first screen to start repair. CAUSE
Windows 2000 server and Windows Server 2003 store information about LUNs and volumes that have been installed and configured in a computer in the SYSTEM hive of the registry. When a device (including a drive) is removed from a system, Windows 2000 Server and Windows Server 2003 retain the registry entries in case the device returns to the system; this is part of Plug and Play. This issue can occur after an array or set of drives is reconfigured, if they are detected as new devices and therefore create duplicate entries. If there are a large number of drives (over 700), this issue can cause the SYSTEM hive to grow large. The SYSTEM hive is limited to approximately 10.3 megabytes (MB) in size in Windows 2000 Server. This is because the SYSTEM hive and the Windows kernel files must fit below 16 MB when Windows starts. Because of design changes, Windows Server 2003 will usually not have this problem unless the /3GB switch is being used. For more information about the SYSTEM hive and Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base: 302594
(http://support.microsoft.com/kb/302594/
)
The system hive memory limitation is improved in Windows Server 2003
RESOLUTION
To resolve this issue, use one of the following methods, depending on the state that the system is in. If this issue occurs after the fact (for example, if the computer does not start), contact Microsoft Product Support Services for assistance in repairing your SYSTEM hive and restoring your Windows installation to a bootable state. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS)
How to repair a computer that you cannot restartImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756
If you already tried to restart the computer and you received the error message that is described in the "Symptoms" section of this article, follow these steps:
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
MORE INFORMATIONIf you want to be proactive because you believe that your server is at risk, use the following procedure to remove the registry entries for drives that have been physically removed. The following instructions describe how to incorporate the Scrubber utility in a Windows 2000 environment by creating a shutdown script that checks the size of the SYSTEM hive. If the SYSTEM hive is over 8 megabytes (MB), the Scrubber utility deletes the removed drives and attempts to clean up the Dynamic disk database and compress any white space. The script does not remove any drives from the Dynamic disk database that were part of any type of RAID volume, including spanned volumes and striped volumes.In addition, read the Readme.txt file that is contained in the utility package for a description of all of the files in the package.
To create a shutdown script that checks the size of the SYSTEM hive, follow these steps:
For more information about similar issues, click the following article numbers to view the articles in the Microsoft Knowledge Base: 216369
(http://support.microsoft.com/kb/216369/
)
Unable to create a large number of Dynamic Host Configuration Protocol (DHCP) scopes
244135
(http://support.microsoft.com/kb/244135/
)
Too many printers can cause unsuccessful boot
259930
(http://support.microsoft.com/kb/259930/
)
Cannot start Windows 2000 with a large number of DNS zones
269075
(http://support.microsoft.com/kb/269075/
)
Error message: "Windows could not start because the following file is missing or corrupt: \Winnt\System32\Config\Systemced"
270028 Windows Server 2003 increases the memory that is available at boot time so that the size of the System hive is not as relevant.
(http://support.microsoft.com/kb/270028/
)
Windows NT may not start with many DFS shares
For more information, click the following article number to view the article in the Microsoft Knowledge Base: 302594 If you are using the /3GB switch in Windows Server 2003, the 16-MB limit still applies until Windows Server 2003 Service Pack 1 (SP1) is available. Microsoft recommends that you create a second entry in the Boot.ini file that does not have the /3GB switch so that more memory is available.
(http://support.microsoft.com/kb/302594/
)
The system hive memory limitation is improved in Windows Server 2003
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003Windows Server 2003 hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesThere are no prerequisites for installing this hotfix.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003, Itanium-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, x86-based versionsCollapse this table
Windows 2000 hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesThere are no prerequisites for installing this hotfix.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this table
STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2. PropertiesArticle ID: 277222 - Last Review: September 11, 2011 - Revision: 11.0 APPLIES TO
| Article Translations |



Back to the top








