The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start – 0xc00e03f1

Our Microsoft Office SharePoint Server 2007 production machine did something strange today.

I did a simple IISRESET for the 132.230th time, and I suddenly got this error:

The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had anerror during its startup or may be disabled.

I attempted to restart the IIS Admin Service and www service, but it did not help.

After a quick look in the Event Log I noticed 4 errors popping up for every IISRESET.

3 times: The incoming sequences checkpoint file failed to initialize. The file MQInSeqs.lg1 or MQInSeqs.lg2 in the Msmq\Storage folder is corrupted or absent. Error 0xc00e03f1:

1 time: The Message Queuing service cannot start. The checkpoint files cannot be recovered. To start the Message Queuing service without losing consistency, you must correct or recover corrupted checkpoint and log files. To start the service for emergency use (with a potential loss of data consistency), delete the files QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, and MQInSeqs.lg2 from the Msmq\Storage folder and add the DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\LogDataCreated with a value of 0. Error 0xc00e03f1:

So basically it’s a pretty safe assumption that Message Queue is the culprit here. Something got messed up in the transaction files.

To fix the error go through these steps:

1: File deletion

Go to the Message Queue folder which is here C:\Windows\System32\msmq\storage.

Delete these 3 files: MQInSeqs.lg1, MQInSeqs.lg2 and QMLog

Registry editing:

Remember to backup your registry before you edit anything. You never know.

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.

See if there is a key named LogDataCreated.

If it is not there, rightclick the Parameters “folder” to the left and choose “New” -> “DWORD (32-bit) Value”.
Name it LogDataCreated and make sure its value is 0.

If there is such a key, double click it and edit its value to 0.

Start or restart Message Queue

Start it using “Start” -> “Administrative tools” -> Services and rightclicking “Message Queuing” and choose start or restart depending on its state.

Using console you can type: net start msmq

Do an issreset now and see if it works.

If it works, go to your event log and check everything is fine.

The problem doesn’t really have anything to do with Windows SharePoint Services or Office SharePoint Server and I am not quite sure exactly what caused it.