Knowledge Base

Conferencing Server does not start with events 10004 and 36

Article ID: 269001

Article Last Modified on 3/14/2007

APPLIES TO

Microsoft Exchange 2000 Conferencing Server

This article was previously published under Q269001

SYMPTOMS

After you install Conferencing Server as part of Exchange 2000 on a computer that is running Microsoft Windows 2000, Conferencing Server (the Microsoft Exchange T.120 MU service) may not start, and you may see the following event in the Event Viewer Application log:

Event ID: 10004
Source: DCOM
DCOM got error "Logon failure: unknown user name or bad password. " and was unable to logon .\IWAM_MYSERVER in order to run the server:
{3D14228D-FBE1-11D0-995D-00C04FD919C1}

followed by this event:

Event ID: 36
Source: W3SVC
The server failed to load application '/LM/W3SVC/1/Root/Conferencing'. The error was 'The server process could not be started because the configured identity is incorrect. Check the username and password'.
For additional information specific to this message please visit the Microsoft Online Support site located at:
http://search.support.microsoft.com/search/?adv=1.

CAUSE

This behavior occurs because the Windows 2000 Component Services and Microsoft Internet Information Services (IIS) 5.0 processes are not synchronized. The IWAM_machine account may be out-of-synchronization with the metabase, Active Directory, and COM+. Account information stored in the IIS metabase should be synchronized with Active Directory, but COM+ applications are not automatically updated.

RESOLUTION

IIS 5.0 provides the Synciwam.vbs script to update the starting identity of all IIS COM+ application packages that run out-of-process. The Synciwam.vbs script is located in the Inetpub\AdminScripts folder at the root of the drive; use Cscript or Wscript to run it (see the Synciwam.vbs file for more information).

Note If you use Synciwam.vbs, it resets all out-of-process applications (medium and high isolation) to IWAM_machine.

To use Cscript to run Synciwam.vbs, follow these steps:

At a command prompt, change directory to c:\Inetpub\AdminScripts (where c: is the system drive and Synciwam.vbs is located in the AdminScripts directory).
Type the following command:

cscript synciwam.vbs -v

You should see the script complete successfully.

To use Wscript to run Synciwam.vbs, follow these steps:

Click Start, and then click Run.
In the Open box, type:

wscript c:\Inetpub\AdminScripts\synciwam.vbs -v

The output appears in Windows in a graphical user interface (GUI) mode.

Note You can use the -v option for verbose mode or the -h option for help with the cscript and wscript commands.

Synciwam.vbs may fail with error 80110414, and you may see the following output in verbose mode:

Updating Applications:
Name: IIS Out-Of-Process Pooled Applications Key:
{3D14228D-FBE1-11D0-995D-00C04FD919C1}
Error: 80110414

If Synchiwam.vbs fails with error 80110414, see the following article in the Microsoft Knowledge Base:

269367 Synciwam utility does not function and generates error 80110414

Because this is really an issue with the Component Services and IIS 5.0, you may see the same event IDs by number in the application log, but referencing an IIS component or a component other than Exchange 2000.

After you run Synciwam.vbs successfully, verify that the Exchange 2000 Conferencing Server has started.

STATUS

This behavior is by design.

Additional query words: exch2kp2w

Keywords: kbprb KB269001

Microsoft KB Archive/269001

Contents