locked
Port is Busy: All pipe instances are busy RRS feed

  • Question

  • Hi

    This error message keeps poping up in the event viewer.
    The solutions works fine.

    Any ideas what it can be?


    MOSS2007 SP1 - Windows server 2003 R2 Stand. SP2 32-bit
    SQL 2008 - Windows Server 2008 Ent SP2 64-bit




    Event Type:    Error
    Event Source:    Office SharePoint Server
    Event Category:    Office Server Shared Services
    Event ID:    7119
    Date:        11/18/2009
    Time:        11:50:54 AM
    User:        N/A
    Computer:    **SharePointServer**
    Description:
    A service provisioning cannot be completed. The SPAdmin service might be stopped. Start the SPAdmin service and try provisioning again.

    Message: Port is Busy: All pipe instances are busy.


    Techinal Support Details:
    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 Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisWebSite(String serverComment, String[] serverBindings, String[] secureBindings, Int32 authenticationMethods, String[] authenticationProviders, String path, Int32 accessFlags, String applicationName, String applicationPoolId, String[] scriptMaps, String sslCertificateSubjectName)
       at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisWebSite(String serverComment, String[] serverBindings, String[] secureBindings, Int32 authenticationMethods, String[] authenticationProviders, String path, Int32 accessFlags, String applicationName, String applicationPoolId, String[] scriptMaps, String sslCertificateSubjectName)
       at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Wednesday, November 18, 2009 1:05 PM

Answers

All replies

  • Hi,

    Do you use ASP.NET 3.5?
    If yes, did this happen after the installation of ASP.NET 3.5?
    If it is the case, ASP.NET 3.5 might be the issue here.

    Best Regards.


    Lily Wu
    Friday, November 20, 2009 5:06 AM
  • Hi Lily

    Yes this actually hapend after the .NET 3.5 Service pack installation.
    Except the messages in the error log, how "dangerous" is this error?

    We have not noticed any change in the functions on the sites.
    Friday, November 20, 2009 7:32 AM
  • Hi tbs0,

    Have you resolve this error?

    Since you've mentioned that the solution works fine in your post, I thought you've walk through it and error disappeared from error log. If so, I think there shouldn't be any "dangerous" there.

    Let me know if I misunderstand you. Thanks.

    Best Regards.
    Lily Wu
    • Marked as answer by Lily Wu Friday, November 27, 2009 6:20 AM
    • Unmarked as answer by CH Lundstrom Sunday, March 28, 2010 10:50 AM
    Friday, November 20, 2009 8:21 AM
  • hi tbs0,
    Have you fixed this? I am having the same issue- it started after installing dotnet  3.5 and doing the loopback change.
    Tuesday, February 23, 2010 5:19 PM
  • rolling back dot net 3.5 and installing this hotfix http://support.microsoft.com/kb/971521  on the indexer fixed the problem.

     

    • Proposed as answer by OHar Friday, March 26, 2010 2:27 PM
    • Marked as answer by CH Lundstrom Sunday, March 28, 2010 10:50 AM
    Friday, March 26, 2010 2:27 PM
  • Hi,

    The hotfix link is not working...


    Saturday, September 12, 2020 12:08 AM