Mobile Information 2001 Server HTTP Connector Does Not Seem to Start and Is Not Listed Under Services (291547)



The information in this article applies to:

  • Microsoft Mobile Information 2001 Server

This article was previously published under Q291547

SYMPTOMS

When you use Hypertext Transfer Protocol (HTTP) protocol to communicate from Mobile Information Server Enterprise Edition to Mobile Information Server Carrier Edition, the HTTPConnector service may not start, and when you view the program log, the HTTPConnector is not listed as a service.

CAUSE

This issue can occur because the HTTPConnector runs as a process in Dllhost.exe and it does not start until it is initially called upon by an HTTP push from Mobile Information Server Enterprise Edition, or until an HTTP push is received on a Mobile Information Server Carrier Edition computer.

RESOLUTION

To work around this issue, wait for the first push message to pass though the HTTPConnector. This message causes the HTTPConnector to start.

MORE INFORMATION

This behavior is by design. The following event ID message is logged in the Application event log when the HTTPConnector starts:

Event Type: Information
Event Source: Mobile Information Server HTTP Connector
Event Category: None
Event ID: 1
Date: 4/6/2001
Time: 2:18:36 PM
User: N/A
Computer: MMISSERVER
Description:
HTTPConnector is successfully loaded.

To confirm that the HTTPConnector is running:
  1. Click Start, click Run, and then click MMC.
  2. In Microsoft Management Console (MMC), click Console, and then click Add/Remove Snap-in.
  3. Click Add, add the Component Services snap-in, and then click OK.
  4. Click to expand Computers, and then click to expand My Computer.
  5. Right-click COM+ Applications, and then click View-Status View.

    The COM+ programs that are running on the server are displayed.
  6. Look for the program that contains "MMISNotify"; this program is the HTTPConnector.

    If the ball in the box is spinning and "yes" is displayed in the Running column, the HTTPConnector is started.
  7. View the process identification number (PID) of the connector, start Task Manager, and then look to see the process that HTTPConnector is running under (Dllhost.exe).
You can also use Tlsit.exe to check to see what process HTTPConnector is running under. You can find Tlist.exe in the Microsoft Windows 2000 Support Tools; it is located in the Support\Tools folder on the Windows 2000 CD-ROM. To use Tlsit.exe, open a command prompt, and then type tlist -m httpconext.dll. The process that the HTTPConnector is running and its PID is displayed. The following text is an example of the output that you receive when you run Tlist.exe :

httpconext.dll - 1376 dllhost.exe

In this example, Httpconext.dll is the in-process dynamic-link library (DLL), 1376 is the PID, and Dllhost.exe is the process that HTTPConnector is running under.

Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbprb KB291547