When looking in the ServiceDesk, Workflow, or Windows System Event logs, the following error is seen "Failed to write to an IPC Port: The pipe is being closed."

System.Runtime.Remoting.RemotingException: Failed to write to an IPC Port: The pipe is being closed. 

Server stack trace: 

at System.Runtime.Remoting.Channels.Ipc.IpcPort.Write(Byte[] data, Int32 offset, Int32 size) 

at System.Runtime.Remoting.Channels.ChunkedMemoryStream.WriteTo(Stream stream) 

at System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.SendRequest(IMessage msg, ITransportHeaders headers, Stream contentStream) 

at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream) 

at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg) 

Exception rethrown at [0]: 

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) 

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) 

at LogicBase.Core.Messaging.Remoting.MessagingServer.Get(String session, String exchangeName, String ID) 

at LogicBase.Framework.Utilities.RemotingHelper.<>c__DisplayClass1`1.<CallWithRetry>b__0() 

at LogicBase.Framework.Utilities.RemotingHelper.CallWithRetry(Action func) 

at LogicBase.Framework.Utilities.RemotingHelper.CallWithRetry[T](Func`1 func) 

at LogicBase.Core.Messaging.RemoteServerImpl.Get(String ID) 

at LogicBase.Core.Messaging.Remoting.MessagingServerAccessor.GetConfigurationForGroupOfExchanges(String configurationName) 

at LogicBase.Core.SymQ.WorkflowSymQConfiguration.SetupWorkflowSymQConfig() 

at Symantec.Workflow.Installer.ServerRoles.WorkflowServerRole.Run() 

at Symantec.Workflow.Installer.InstallerManager.Run() 

Various.

This can happen for various reasons and can appear in different logs. The most common is if Server Extensions are restarted and is the case if, when installing to the SMP, Server Extentions does not restart in a timely manner. If this is the case, there is no problem.  If you are using Enterprise Management on the SMP you should make sure that the newly added server is properly included in the Workflow environment, and that the enviroment verifies properly.  The timing of this entry in the logs is an expected error while the server extensions are being restarted; this can be safely ignored.

If, however, Workflow is unable to publish a project and this error is seen in the logs, this can indicate a real issue. Please refer to the related article below for troubleshooting information:

152290 (TECH42036) "Unexpected Exception when publishing a workflow project"

Applies To

 Workflow Server 7.5 Sp1 and earlier