Windows Application Event Log Contains the Following Error Message When Sametime Services are not Available: The IMlogic Sametime Message Injector service terminated unexpectedly
|Article:TECH154643|||||Created: 2011-03-02|||||Updated: 2011-09-20|||||Article URL http://www.symantec.com/docs/TECH154643|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
The Windows System Event log contains the following error event:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Time: 12:18:15 PM
The IMlogic Sametime Message Injector service terminated unexpectedly. It has done this 143 time(s). The following corrective action will be taken in 2000 milliseconds: Restart the service.
This event may be repeated many times in succession.
- Sametime service is not available at the times the events are reported.
This is typically seen during the system startup process. The IM Manager message injector typically is started early in the boot up process. While Sametime starts up much later in the boot up process.
This may also been seen if Sametime is restarted while the computer is running.
- IM Manager implementation with Sametime.
The IM Manager message injector attempts to log into Sametime. When Sametime is unavailable the message injector exits. The Windows Service Control Manager is configured to restart the message injector service. This process of attempting a login, exit, and restart continutes until Sametime is available for login requests.
Symantec is aware of this issue. This article is updated as more information is available. Subscribe to the article to receive updates.
These events should be ignored. Once Sametime is available the events stop. If the events continue after Sametime is available another issue is causing the messages. Search the IM Manager knowledgebase for further information.
Article URL http://www.symantec.com/docs/TECH154643