Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OCS Services won't start on bootup but start manually RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Ever since we updated our network drivers and firmware on our Dell Server, whenever we start the OCS Server the following services fail.  They also failed about a week after leaving up the server.  I figured the network stack is taking a little longer to start up (we're only using Access Edge/Web Conf -- no AV) so I tried making the RTCSRV and RTCDATAPROXY dependent on the lanmanservice (server service) just to see if delaying the ocs services would work but still no go.  Any suggestions?

    We get the following errors:

    Event Type:    Error
    Event Source:    OCS Server
    Event Category:    (1000)
    Event ID:    12326
    Date:        10/22/2008
    Time:        9:59:32 AM
    User:        N/A
    Computer:    RI-OCS01
    Description:
    Failed starting the protocol stack. The service has to stop

    Error code is:0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED).


    Event Type:    Error
    Event Source:    OCS Protocol Stack
    Event Category:    (1001)
    Event ID:    14352
    Date:        10/22/2008
    Time:        9:59:32 AM
    User:        N/A
    Computer:    RI-OCS01
    Description:
    Unable to start the stack.

    Error: 0x0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED).

    Event Type:    Error
    Event Source:    OCS Protocol Stack
    Event Category:    (1001)
    Event ID:    14336
    Date:        10/22/2008
    Time:        9:59:32 AM
    User:        N/A
    Computer:    RI-OCS01
    Description:
    A configured transport has failed to start.

    Transport TLS has failed to start on local IP address 10.10.135.41 at port 5061.


    Event Type:    Error
    Event Source:    OCS Protocol Stack
    Event Category:    (1001)
    Event ID:    14346
    Date:        10/22/2008
    Time:        9:59:32 AM
    User:        N/A
    Computer:    RI-OCS01
    Description:
    Unable to bind for socket.

    Transport:TLS, IP address:10.10.135.41, Port:5061. Error:0x80072741 (The requested address is not valid in its context.).





    Wednesday, October 22, 2008 3:08 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems that your network is not up when OCS tries to register/startup

     

    Wednesday, October 22, 2008 9:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     Deli Pro-Exchange wrote:
    It seems that your network is not up when OCS tries to register/startup

     



    Ya that's what we thought.  Especially since this started to happen right after we upgraded drivers.  The issue happens to occur on the NICs that are teamed (the internal interface).  Guess we'll try to rollback drivers and see what happens.
    Wednesday, October 22, 2008 10:32 PM