jezzar
asked on
Error 80080005 starting IISAdmin service
I have a whole bunch opf services that won't start (SMTP, IIS, IISAdmin, DHCP, Exchange POP, Exchange Routing).
I think I have narrowed it down to the IISAdmin service as the key one, although I am not certain! Event log shows error code 80080005. I have done a search on this, and found an article telling me to add 512 into the registry key HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Co ntrol\Sess ion Manager\Subsystems\Windows , but it is already there!
If I don't get this solved yesterday I'm a dead man!
Any ideas?
I think I have narrowed it down to the IISAdmin service as the key one, although I am not certain! Event log shows error code 80080005. I have done a search on this, and found an article telling me to add 512 into the registry key HKEY_LOCAL_MACHINE\SYSTEM\
If I don't get this solved yesterday I'm a dead man!
Any ideas?
ASKER
Good idea!
Source: MSExchangeMU
EventID: 1009
Description: Failed to access the metabase, error code is 80080005 (Server execution failed).
Source: MSExchangeMU
EventID: 1009
Description: Failed to access the metabase, error code is 80080005 (Server execution failed).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I was able to correct this problem by restoring the MetaBase.xlm file, which had become corrupted. This file is located in %SystemRoot%\Windows\Syste m32\Inetsr v. If you have an independant backup of this file, it is probably best to use that. I found a usable copy in the folder ...\System32\Inetsrv\Histo ry. There is information regarding a problem similar to this at
http://support.microsoft.com/kb/234429/
This link relates more to Exchange 2000, but most of the concepts are the same. Their suggestion to pull a previous metabase file from the ...\Inetsrv\Metaback folder though does not seem to be accurate. However, be sure to stop any related IIS services using
net stop iisadmin /y
before making any changes to the metabase file.
CTSMKE
http://support.microsoft.com/kb/234429/
This link relates more to Exchange 2000, but most of the concepts are the same. Their suggestion to pull a previous metabase file from the ...\Inetsrv\Metaback folder though does not seem to be accurate. However, be sure to stop any related IIS services using
net stop iisadmin /y
before making any changes to the metabase file.
CTSMKE
ctsmequon's comment VERY helpful. IIS metabase corrupted on Win 2003 SBS Stnd x86 server due to power outtage, MS Exchange services, IISAdmin & other key services cannot launch. No current backup exists, it was discovered.
Found workable copy of the MetaBase.xml in the \System32\Inetsrv\History folder. All is well.
Found workable copy of the MetaBase.xml in the \System32\Inetsrv\History folder. All is well.
Thanks for that solution, Its really appreciated - Give yourself a pat on the back that man! (ctsmequon)
Replacing the MetaBase.xlm worked for me - much appreciated....
ctsmequon,
I owe you a pint
Cheers
I owe you a pint
Cheers
Sorted my problem! Thanks guys.
ctsmequon,
that did the trick for us as well! Thanks!
that did the trick for us as well! Thanks!
In my situation, I needed to replace both the schema and metabase xml files...
See this. Thanks LazyJeff...
See this. Thanks LazyJeff...
Event Id, Source and Data would be nice.