Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of jezzar
jezzar

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\CurrentControlSet\Control\Session Manager\Subsystems\Windows , but it is already there!

If I don't get this solved yesterday I'm a dead man!

Any ideas?

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of WeHeWeHe🇷🇴

Maybe you can provide us the eventlog entry a bit more detailed?
Event Id, Source and Data would be nice.
Avatar of jezzarjezzar

ASKER

Good idea!

Source: MSExchangeMU
EventID: 1009
Description: Failed to access the metabase, error code is 80080005 (Server execution failed).
ASKER CERTIFIED SOLUTION
Avatar of WeHeWeHe🇷🇴

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account
Avatar of ctsmequonctsmequon

I was able to correct this problem by restoring the MetaBase.xlm file, which had become corrupted. This file is located in %SystemRoot%\Windows\System32\Inetsrv. 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\History. 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
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of KKOS-KSKKOS-KS🇺🇸

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.
Avatar of unrealone1unrealone1🇬🇧

Thanks for that solution, Its really appreciated - Give yourself a pat on the back that man! (ctsmequon)
Avatar of AJODOHERTYAJODOHERTY🇬🇧

Replacing the MetaBase.xlm worked for me - much appreciated....
Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of swper-itswper-it

ctsmequon,
I owe you a pint

Cheers
Avatar of 1stopit1stopit

Sorted my problem!   Thanks guys.
Avatar of tcssupporttcssupport

ctsmequon,

that did the trick for us as well!  Thanks!
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of lanprolanpro

In my situation, I needed to replace both the schema and metabase xml files...

See this. Thanks LazyJeff...
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).