Video Screencast Help

Port is Busy: All pipe instances are busy

Created: 20 Apr 2012 • Updated: 22 Apr 2012 | 23 comments
Luis.Silva's picture

Hi,

We have installed two version of ServiceDesk 7.1 SP1 and SP2. Frequently occur this error:

 

System.Runtime.Remoting.RemotingException: Port is Busy: All pipe instances are busy.
 
Server stack trace: 
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)
   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, ExchangeAttributeQuery[] attributes, MessageQueryType queryType)
   at LogicBase.Core.Messaging.RemoteServerImpl.Get(ExchangeAttributeQuery[] attributes, MessageQueryType queryType)
   at LogicBase.Core.Messaging.AbstractDeliveryFilter.Get(ExchangeAttributeQuery[] attributes, MessageQueryType queryType)
   at LogicBase.Core.Messaging.utilities.PollingHelper.Invoke()
   at LogicBase.Framework.LocalInvokeLater.RunQueueThread()
 
When occur this error, it's necessary to restart "Symantec Workflow Server" Service, stop IIS Service, delete .NET temporary and star IIS Service. However, after 6 or 7 days we need to do the process again, because it's impossible to work, to open incident... So, all the time we need to execute the process to workaround the problem "Port is Busy: All pipe instances are busy".
 
There is a article about this problem:
http://www.symantec.com/docs/TECH139485
But not resolve this problem, because the version of "System.runtime.remoting.dll" it's "2.0.50727.4056" and current installed version it's "2.0.50727.4927". Furthermore, this article it's applicable in Servicedesk 7.0 MR1 and MR2 environment and we use SP1 7.1 and SP2 7.2.
 
Any idea?
 
 
 
 

 

Comments 23 CommentsJump to latest comment

Joshua Brown's picture

Do you have Windows 2008 R2 as your server OS?  I had the same issue, and after some research I found that the hotfix mentioned in that article is actually included in Service Pack 1 for Windows 2008 R2.  After installing SP1 on the server, we haven't seen these errors.

Luis.Silva's picture

Hi, Joshua Brown

Thak's for your attention!

We have Windows 2008 R2 without SP1. You have the article link about this problem?

Because I need a article or a document from Microsoft to install Service Pack 1. Actually, we don't have a homologation environment to do tests, because of this, I need a formal information to execute any new installation. 

 

 

Luis.Silva's picture

Joshua Brow,

What's the version of your ServiceDesk, 7.1 SP1 or 7.1 SP2?

Joshua Brown's picture

I'm using ServiceDesk 7.1 SP2.  You can get a list of the hotfixes included in 2008 R2 SP1 from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=269 - it is the last document there.  The Symantec article you mention above references Microsoft KB 971521, and that hotfix is included in the 2008 R2 Service Pack 1.   

Luis.Silva's picture

Joshua Brow,

Thank's for your help!

There is a document with information about wich Hotfixes and Security Updates included in SP1.

I'm going to test, to install SP1, and I tell you if I get successful.

Regards,

Luis Silva 

AttachmentSize
Updates in Win7 and WS08R2 SP1.xls 684 KB
toomas's picture

The KB article about these errors (TECH139485) was updated a few days ago with the recommendation of installing Windows Server 2008 SP1. We had (mistakenly) assumed that the Microsoft known issue linked in the article was fixed in newer versions like the one included in Windows Server 2008. It is not.

As Joshua pointed out, it is fixed in Windows Server 2008 SP1. Installing SP1 is fine as long as you're running ServiceDesk 7.1 SP1 or newer.

Aryanos's picture

We have this error as well and plan to install the the Windows Server 2008 SP1 on the servers but do you know if this also fixes the SQLTransaction.ZombieCheck() errors as well or is that in the separate rollup for SD 7.1 SP1?

I like my beats fast and my bass down low

toomas's picture

No, Windows Server 2008 SP1 does not fix ZombieCheck errors.

There is a fix specifically for ZombieCheck errors in SD 7.1 SP1 Rollup.

datadrudge's picture

We have the same problem and have opened cases twice on this error. The last time (within the last month), support told me it had something to do with building ServiceDesk using a templated VM rather than creating the build manually. For those who have experienced the error -is this true for you?

In any case, I will definitely schedule application of SP1 on our 2008R2 server as soon as possible. Can't WAIT to see the end of this error.

Thanks for the head's up.

 

 

jmankin's picture

I installed SD 7.1 sp2 on a Windows 2008 R2 SP1 for testing and I still see the "all pipe instances are busy".

WK01's picture

We have SD 7.1 SP2 running on Windows 2008 SR2 with Service Pack 1 and we are getting this message frequently.

We see that our Event Viewer is being hammered with this message every few minutes.

Support is working on this now.  They feel it is a .NET Error.  I will post back any information they provide.

jrivard's picture

Does not appear to be fixed in the SD 7.1 SP1 RollUp fix.  I have support addresssing the issue now.

Luis.Silva's picture

Hi,

Thaks for your feedback and sorry to answer just now...

We contacted the support about this KB:
http://www.symantec.com/docs/TECH179823

we are waiting if it's necessary to apply this KB and if this KB resolved the problem.

when I have more information, inform you.

Regards,

Luis Silva

Luis.Silva's picture

This problem occurred in our new ServiceDesk SP2 too.

WK01's picture

Symantec has a fix for this: Port is Busy: All pipe instances are busy

You should contact them.  We are installing this fix on test server today.

Luis.Silva's picture

Hi WK01,

When this fix was realesed? What's the version your ServiceDesk, 7.1 SP2?

WK01's picture

Hello Luis,

This has been an open case for a few weeks.  Symantec and Microsoft have been working on it together.  This past Wednesday the Symantec Support technician working the case contacted me to tell me a fix has been created.  It is not officially released because it is so new.  We are attempting to schedule the install to our test environment this afternoon.  We are running ServiceDesk 7.1 SP2. 

FYI, as a temporary fix, Symantec recommened scheduling a reboot of the SD server once a week.  This has actually helped.. we have seen very limited occurrences.. infact none since our last reboot a week ago.

WK01's picture

We were unable to install it due the fact that our partner built some best practices into the ServiceDesk workflow.  We have to evaluate the risk before going forward.

jsahleen's picture

We are experiencing this same issue. (ServiceDesk 7.1 SP2, Windows Server 2008 R2 SP1)  Has anyone had a successful deployment of this "Fix"?  Anyone have any idea of when the Official fix will be released?

 

Thanks,

Aryanos's picture

You can contact support for a point-fix. We get this error randomly and when it does it creates orphaned tickets which you'll never see unless you're constantly monitoring the queue or when the requester asks about the incident which is never a good sign.

I like my beats fast and my bass down low

datadrudge's picture

We are on ServiceDesk 7.1 SP1 and I worked with support to apply the fix (Symantec Workflow 7.1 SP1 Rollup v2) right after it came out. While I still very occasionally see the error, it is greatly, greatly diminished and our ServiceDesk has been stable since its application. I have not had to reboot to resolve issues. While working with support, we also made some modifications that make reassignments instant and much more efficient. Awesome! I get very few complaints about ServiceDesk now...my issues are now the standard..."how do I?" type software request. It has been more than a month...we applied it on June 20. Happy camper. :)

mbarbaro's picture

Hello datadrudge,

We are experiencing this same issue, and I read that you have partially resolved with the Rollup V2. Does this Rollup specific for the ServiceDesk solution? Or is it a Rollup for SMP1 mentioned in this HOWTO:

http://www.symantec.com/business/support/index?page=content&id=HOWTO60937

Can you give me more information about it?

Thank's

toomas's picture

The Rollup mentioned above is a Workflow 7.1 SP1 Rollup. This does apply to the same version of ServiceDesk as well.

SMP Rollups are completely different.

To get the rollup, you should contact Symantec Technical Support.