OCS 2007 - Front-end suddenly will not start

Hi all.

I have OCS 2007 installed in Windows 2003 R2.  We've been using OCS 2007 for months, and suddenly the front-end service will not start (there were literally no changes).

I have reformatted, reinstalled, TWICE, and am still receiving these errors.  I need to know how to clean AD completely, as if this was never installed (unless someone has a better solution!).

I am receiving the following errors in the log (NOTE:  CAPRICORN.SMT.LOCAL WAS THE OLD IM SERVER - I had received this error WHILE the machine was named 'Capricorn', I had tried reformatting and keeping the name 'capricorn'.  The last reformat, I renamed the OCS server 'MARS'):

The server configuration validation mechanism detected some serious problems.

2 errors and 0 warnings were detected.

ERRORS:
Two server roles at FQDN [capricorn.smt.local] have different 'Treat As Authenticated' options. First server has GUID {0251506E-FA68-45A4-9442-ABFCAC069255} and role 'Conferencing Server' (option is set). Second server has GUID {A74A65D2-D2EA-52A2-8A75-378E50845582} and role 'Edge Server' (option is not set).
Two server roles at FQDN [capricorn.smt.local] have different server version numbers. First server has GUID {0251506E-FA68-45A4-9442-ABFCAC069255} and role 'Conferencing Server' (version 3). Second server has GUID {A74A65D2-D2EA-52A2-8A75-378E50845582} 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.

--

This error is also listed with OCS Protocol Stack 14352 Event, and OCS Server 12326 (this is listed below):

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.

---

We use OCS for internal use only.  Everything is on one server, with one internal IP of 192.168.1.18.

Start Free Trial