Posts Tagged Installation
OCS 2007 Protocol Stack Error Event ID 14517 When Starting Services
Posted by Sheen in Windows Server on January 15, 2010
You may come across this error message when you install Office Communications Server 2007 for the first time in your environment. This error generally is seen after you run through the initial steps and are trying to start the OCS services for the first time.
This event ID will contain the following message:
ERRORS:
Two server roles at FQDN [server.domain.com] have different ‘Treat As Authenticated’ options. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (option is set). Second server has GUID {BD77F03B-4451-4171-A035-FC7FB264383D} and role ‘A/V Authentication Service’ (option is not set). Two server roles at FQDN [server.domain.com] have different server version numbers. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (version 3). Second server has GUID {BD77F03B-4451-4171-A035-FC7FB264383D} and role ‘A/V Authentication Service’ (version 0). Two server roles at FQDN [server.domain.com] have different ‘Treat As Authenticated’ options. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (option is set). Second server has GUID {1719A023-DDB4-5170-836D-3299D4F067C6} and role ‘Edge Server’ (option is not set). Two server roles at FQDN [server.domain.com] have different server version numbers. First server has GUID {58BDE507-1C48-4BA4-BCDF-06FB59ADF9CE} and role ‘Enterprise Edition’ (version 3). Second server has GUID {1719A023-DDB4-5170-836D-3299D4F067C6} and role ‘Edge Server’ (version 0).WARNINGS:
No warningsCause: 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.
This error can be misleading. The primary reason you see this error is simple – You have had a previous installation of OCS in the domain and there are still a few entries in Active Directory that haven’t been cleaned up even though you did a clean uninstall of OCS.
This is what you need to do to fix the error:
Recent Comments