Article ID: 286196 - Last Review: December 3, 2007 - Revision: 2.5 IISReset May Not Save IIS Configuration ChangesThis article was previously published under Q286196 SYMPTOMS
When you make changes to your Internet Information Services (IIS) configuration through the Microsoft Management Console (MMC) or through scripting, some changes may not be saved after you use the iisreset command from the MMC or from a command prompt with no switches.
CAUSE
The IISReset command line tool waits for a normal shutdown of the services before it starts them again. Because of the number of services that are dependent on the IISAdmin service, the shutdown may not occur in a timely manner. When this happens, IISReset forces the shutdown of the services. This can result in metabase changes that are not saved properly.
WORKAROUND
To save the IIS configuration to the metabase, use the net stop and the net start commands to stop and start your services, or stop and start the services from the MMC snap-in. To locate the snap-in, follow these steps:
To start IIS from a command prompt: For additional information on finding the short names of services, click the article number below to view the article in the Microsoft Knowledge Base: 271362
(http://support.microsoft.com/kb/271362/EN-US/
)
How to Find the Short Names of Services
MORE INFORMATION
Do not use IISReset to force IIS configuration changes to be saved to the metabase. Only use IISReset to recover from serious problems that a Web server experiences. For example, when a Web server stops responding (hangs) or crashes, or when 100% CPU utilization occurs. For more information, see the notes in the IISReset window in the MMC.
| Article Translations
|
Back to the top
