locked
Office Communications Server Front-End - SERVICE won't start RRS feed

  • Question

  •  

    Office Communications Server Front-End - SERVICE won't start and here are the errors I am getting. If anyone has any ideas to get this working it would be appreciated.

    Office Communications Server Front-End

     

    Source: event viewer.

    Errors tossed when starting this service.....

     

     

     

    The server configuration validation mechanism detected some serious problems.

     

    2 errors and 0 warnings were detected.

     

    ERRORS:

    Two server roles at FQDN [netpool.compudok.net] have different 'Treat As Authenticated' options. First server has GUID

    {zzzxxx5A-CF41-4633-BFE4-71B9D779742C} and role 'Enterprise Edition' (option is set). Second server has GUID

    {sssvvvA8-E0F8-5C5B-8262-BDB2957C94BF} and role 'Edge Server' (option is not set).

    Two server roles at FQDN [netpool.compudok.net] have different server version numbers. First server has GUID

    {zzzxxx5A-CF41-4633-BFE4-71B9D779742C} and role 'Enterprise Edition' (version 3). Second server has GUID

    {sssvvvA8-E0F8-5C5B-8262-BDB2957C94BF} and role 'Edge Server' (version 0).

     

    WARNINGS:

    No warnings

     

    Cause: The configuration is invalid and the server might not behave as expected.

    Resolution:

    Review and correct the errors listed above, then restart the service. You also wish to review any warnings present.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

    ----------------------------------------------------------------

     

     

    Configuration indicates that the load balancer deployed for this pool operates in Source NAT (SNAT) mode. However, if the

    load balancer is operating in Destination NAT (DNAT) mode then functionality in this pool may be broken.

     

    Resolution:

    If the SNAT mode configuration for this pool is intentional, and accurately reflects the way the load-balancer is configured,

    then this warning is meant to be purely informational. However, if the load balancer is operating in DNAT mode, then set the

    'DNATMode' WMI setting to TRUE under the MSFT_SIPPoolConfigSetting instance for this pool. Note that DNAT mode does reduce

    high availability of various components in the pool.

     

    For more information, see Help and Support Center at

     

     

     

    ------------------------------------------------------------------------------

     

     

    The process AVMCUSvc(3652) failed to send health notifications to the MCU factory at

    https://netpool.compudok.net:444/LiveServer/MCUFactory/.

    Failure occurrences: 510, since 3/11/2008 9:09:53 PM.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

    -----------------------------------------------------------------------------------

     

     

    Unable to start the stack.

     

    Error: 0x0xC3E93C47 (SIPPROXY_E_BAD_SERVER_CONFIGURATION).

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

     

    -----------------------------------------------------------------------------------

     

     

    Failed starting the protocol stack. The service has to stop

     

    Error code is:0xC3E93C47 (SIPPROXY_E_BAD_SERVER_CONFIGURATION).

    Cause: Check the previous entries in the event log for the failure reason.

    Resolution:

    Try restarting the server after resolving the failures listed in the previous event log entries.

     

    -------------------------------------------------------------------------------------------

     

     

    Failed starting a worker process.

     

    Process: 'C:\Program Files (x86)\Microsoft Office Communications Server 2007\Server\Core\ABServer.exe'  Exit Code: C3E83201

    (SIPPROXY_E_SHUTDOWN_REQUESTED).

    Cause: This could happen due to low resource conditions or insufficient privileges.

    Resolution:

    Try restarting the server. If the problem persists contact Product Support Services.

     

    For more information, see Help and Support Center at

     

     

    ---------------------------------------------------------------------------------------------

    Wednesday, March 12, 2008 8:16 PM

All replies

  • We had a similar problem a few weeks ago.  Turns out that we updated the address book configuration using the absconfig tool.  We got a blank record in the address book config database and this caused it to throw an exception.  If you have made any changes there, you might want to check.

     

    gg

     

    Friday, March 14, 2008 7:57 PM
  • Wednesday, March 25, 2009 8:32 AM