You are currently offline, waiting for your internet to reconnect

XFOR: Err Msg: "All Pipe Instances Are Busy" When Starting LinkAge Controller

This article was previously published under Q168577
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
SYMPTOMS
When you attempt to start the LinkAge Controller service from Control PanelServices, the following messages are logged in the LinkAge Administratorprogram's Log Browser:
   control(01ba) 1 00001:Operating system error {WIN32:231(All pipe   instances are busy.)} from NPServer::create   control(01ba) 1 01054:Error {An unknown error condition has occurred}:   Could not create the named pipe server object   control(01ba) 3 00505:control is ending, last return code was {An   unknown error condition has occurred}   control(019f) 1 00001:Operating system error {WIN32:231(All pipe   instances are busy.)} from NPServer::create   control(019f) 1 01054:Error {An unknown error condition has occurred}:   Could not create the named pipe server object   control(019f) 3 00505:control is ending, last return code was {An   unknown error condition has occurred}				
CAUSE
There are two cases when these errors can be generated.
  • The LinkAge Controller (Lsmain.exe) is already up and running and a user is trying to start the LinkAge Controller service.
  • The LinkAge Controller (Lsmain.exe) is stopped or ends abnormally, but the rest of the underlying controller tasks are still running.
RESOLUTION
To resolve this problem, do one of the following:
  • Restart the computer. This is the easiest method.
  • Terminate the remaining LinkAge processes with the Windows NT Task Manager, and then restart the LinkAge Controller service. It should restart correctly after all the processes are stopped. Contact a Microsoft Exchange Server Support Professional to assist with this method.
MORE INFORMATION
The LinkAge controller task and all the underlying tasks talk to each otherthrough named pipes (that is, inter-process communication). Named pipes areused for such things as the scoreboard display on the LinkAge Administratoruser interface, which displays all the processes and their status, theWindows NT Services listing, located in the Control Panel under Services,and the LinkAge Connector logs.

If you are trying to start the LinkAge Controller service when it isalready running, the Named Pipe resources clash, and result in the aboveerrors. You do not need to do anything further.

If the Controller task (Lsmain.exe) is stopped for any reason and all theunderlying tasks remain, and the connector is restarted, the above errorswill be added to the log, and the connector will not appear to start. It ismost likely currently up, and mail is most likely still flowing. But nologs or status of it being up, other than the NT Task Manager, areavailable.
Properties

Article ID: 168577 - Last Review: 10/28/2006 04:57:08 - Revision: 3.3

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition
  • kbprb kbtshoot kbusage KB168577
Feedback