locked
OCS Protocol Stack error. Event 14517 is logged. RRS feed

  • Question

  • A new installation of OCS 2007 fails to start with Event ID: 14517 logged. 

    4 errors and 0 warnings were detected.

    ERRORS:
    Two server roles at FQDN [servername.domain.com] have different 'Treat As Authenticated' options. First server has GUID {85E8EE5B-845F-4549-B3C3-A2D9D0F8C2DD} and role 'Enterprise Edition' (option is set). Second server has GUID {8674781C-B179-4E06-BF32-ABF5EEFCF93C} and role 'A/V Authentication Service' (option is not set).
    Two server roles at FQDN [servername.domain.com] have different server version numbers. First server has GUID {85E8EE5B-845F-4549-B3C3-A2D9D0F8C2DD} and role 'Enterprise Edition' (version 3). Second server has GUID {8674781C-B179-4E06-BF32-ABF5EEFCF93C} and role 'A/V Authentication Service' (version 0).
    Two server roles at FQDN [servername.domain.com] have different 'Treat As Authenticated' options. First server has GUID {85E8EE5B-845F-4549-B3C3-A2D9D0F8C2DD} and role 'Enterprise Edition' (option is set). Second server has GUID {0FF2188E-2681-54B0-B5E6-7813BD7D7316} and role 'Edge Server' (option is not set).
    Two server roles at FQDN [servername.domain.com] have different server version numbers. First server has GUID {85E8EE5B-845F-4549-B3C3-A2D9D0F8C2DD} and role 'Enterprise Edition' (version 3). Second server has GUID {0FF2188E-2681-54B0-B5E6-7813BD7D7316} and role 'Edge Server' (version 0).


    Does anyone have any experience resolving this issue?


    Friday, November 16, 2007 2:04 PM

Answers

  • This problem was resolved with a call to Microsoft Support.  The utimate cause was a beta version of OCS 2007 that I had installed months ago on a seperate server.  Even after deacitvating both the old beta server remnants where left in AD.  The support engineer removed key entries with ADSI edit, deactivated the production server, re-activated the production server and all services started successfully.   I hope this can be of some help to others who come accross this error.
    Wednesday, November 21, 2007 4:05 AM

All replies

  • Have you installed both the internal Front-End Server and external Edge Server roles on the same physical computer?

    Friday, November 16, 2007 5:19 PM
    Moderator
  • I have only installed the Front-End server.  The Edge Server has not been installed on this computer or any other.  I am attempting to only use OCS for internal use at this time.  Possibly in the future I will integrate external access. 

    Thanks,
    Jason




    Friday, November 16, 2007 8:06 PM
  • This problem was resolved with a call to Microsoft Support.  The utimate cause was a beta version of OCS 2007 that I had installed months ago on a seperate server.  Even after deacitvating both the old beta server remnants where left in AD.  The support engineer removed key entries with ADSI edit, deactivated the production server, re-activated the production server and all services started successfully.   I hope this can be of some help to others who come accross this error.
    Wednesday, November 21, 2007 4:05 AM
  • Hello Jason!

    I'm having the same problem. Can you please point me to the locations of those keys in ADSI Edit?

    Thank you!
    Sunday, December 2, 2007 1:58 AM
  • Take a look at my post in this thread to point you in the right direction:

    http://forums.microsoft.com/unifiedcommunications/ShowPost.aspx?PostID=2389058&SiteID=57

     

     

    Sunday, December 2, 2007 3:57 PM
    Moderator