locked
Cannot start FE due to old Active Directory Data RRS feed

  • Question

  • Good morning everyone,

    First let me start by saying I've already gotten some good info from the guys in the edge server forum, however now I need some assistance with basic front-end service configuration.

    I've recently taken over the deployment of OCS2007 from a former employee who essentially had no clue what he was doing, and now it's my job to resolve issues he has created and get the service up and running.

    After completing a basic install and trying to verify service configuration, I'm stuck because the FE server will not start, looking through the event log, here is what I'm seeing.

    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.

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

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

    The following known servers were recognized on startup:

    Server: LCS.mycompany.local; UniqueID: {D34815DF-7039-48C8-B61C-14D93E4FF0E2}; Role: Enterprise Edition
    Server: DS9.mycompany.local; UniqueID: {821349E2-CCF4-4041-9054-0A5261F36665}; Role: Enterprise Edition
    Server: pegasus.mycompany.local; UniqueID: {A2BAC6DD-0B05-4D64-940E-E5168E7B3C6E}; Role: Enterprise Edition
    Server: OCSFE.mycompany.com; UniqueID: {95D2EFC8-60F2-4E43-8E6D-D419457E07BD}; Role: Enterprise Edition
    Server: pegasus.mycompany.local; UniqueID: {F01F4491-7629-4DFD-83B5-2ACB37B95665}; Role: Conferencing Server; Type: chat; Vendor: Microsoft Corporation
    Server: pegasus.mycompany.local; UniqueID: {91783E9F-6F9B-4831-BBC4-5B4D6FF1263F}; Role: Conferencing Server; Type: phone-conf; Vendor: Microsoft Corporation
    Server: pegasus.mycompany.local; UniqueID: {C301789B-9FB2-40DD-A9D1-6AA19D6AE374}; Role: Conferencing Server; Type: meeting; Vendor: Microsoft Corporation
    Server: pegasus.mycompany.local; UniqueID: {0CCB4A55-236E-4DD4-8516-E73FB4819841}; Role: Conferencing Server; Type: audio-video; Vendor: Microsoft Corporation
    Server: OCSFE.mycompany.com; UniqueID: {9D7C37E4-66EB-434F-88F7-1F15C2508DA9}; Role: Conferencing Server; Type: chat; Vendor: Microsoft Corporation
    Server: OCSFE.mycompany.com; UniqueID: {17416398-8633-4958-BFCB-B064E2D1CA30}; Role: Conferencing Server; Type: phone-conf; Vendor: Microsoft Corporation
    Server: OCSFE.mycompany.com; UniqueID: {8D4DDEAC-2659-42B8-9CA0-2A7C9AEAB230}; Role: Conferencing Server; Type: meeting; Vendor: Microsoft Corporation
    Server: OCSFE.mycompany.com; UniqueID: {562A11F6-458B-4EE1-B11F-6607721C0AFD}; Role: Conferencing Server; Type: audio-video; Vendor: Microsoft Corporation


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

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

    The server configuration validation mechanism detected some serious problems.

    4 errors and 0 warnings were detected.

    ERRORS:
    Two server roles at FQDN [pegasus.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {0CCB4A55-236E-4DD4-8516-E73FB4819841} and role 'Conferencing Server' (option is set). Second server has GUID {61324A14-5BE6-4DC6-9D3A-065027CEA626} and role 'A/V Authentication Service' (option is not set).
    Two server roles at FQDN [pegasus.mycompany.local] have different server version numbers. First server has GUID {0CCB4A55-236E-4DD4-8516-E73FB4819841} and role 'Conferencing Server' (version 3). Second server has GUID {61324A14-5BE6-4DC6-9D3A-065027CEA626} and role 'A/V Authentication Service' (version 0).
    Two server roles at FQDN [pegasus.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {0CCB4A55-236E-4DD4-8516-E73FB4819841} and role 'Conferencing Server' (option is set). Second server has GUID {879B4C27-EC34-51CE-96B6-F6931F92D45D} and role 'Edge Server' (option is not set).
    Two server roles at FQDN [pegasus.mycompany.local] have different server version numbers. First server has GUID {0CCB4A55-236E-4DD4-8516-E73FB4819841} and role 'Conferencing Server' (version 3). Second server has GUID {879B4C27-EC34-51CE-96B6-F6931F92D45D} 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.

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

    Now that we've got that out of the way.
    A little explanation.
    These servers no longer exist in our infrastructure.
    LCS.mycompany.local
    DS9.mycompany.local
    pegasus.mycompany.local

    The current box that I am trying to work with is OCSFE.mycompany.com

    My sip domain is mycompany.com as is our primary domain <- is this setup incorrect? does there need to be a separate domain for SIP? I didn't think there did.

    Regardless, what on earth am I to do to remove all of this old information from AD, and at least get this new installation of OCS up and running?

    Any help would be GREATLY appreciated.
    Note, this is a Standard Edition Installation as we have only 30 people right now who will be utilizing the service.

    Thanks,
    Matt
    Monday, February 18, 2008 2:09 PM

Answers

  • HI,

    It looks like your three servers that no longer exist were removed without being deactivated within the OCS admin console.  You're going to have to manually delete the references in AD using LDP or similar LDAP tool.

    Connect to the Domain Base DN tree and expand to:

    CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=MYDOMAIN,DC=LOCAL

    Under that you should see a listing of all the servers, remove all the extinct servers and try starting the service. 

    If you haven't used LDP or similar be very careful, you can muck up your AD really quick Wink

    Hope this helps

    -Joe



    Friday, February 22, 2008 7:09 PM

All replies

  • HI,

    It looks like your three servers that no longer exist were removed without being deactivated within the OCS admin console.  You're going to have to manually delete the references in AD using LDP or similar LDAP tool.

    Connect to the Domain Base DN tree and expand to:

    CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=MYDOMAIN,DC=LOCAL

    Under that you should see a listing of all the servers, remove all the extinct servers and try starting the service. 

    If you haven't used LDP or similar be very careful, you can muck up your AD really quick Wink

    Hope this helps

    -Joe



    Friday, February 22, 2008 7:09 PM
  • Joe,

    Thanks for the tip, I forgot to mark my question as answered before your post, however I went ahead and started digging around ADSIedit and found the different servers that were no longer active and wiped them out.

    Thanks again,
    Matt
    Friday, February 22, 2008 9:34 PM