Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3412
  • Last Modified:

Office Communications Server 2007 Has Stopped Working

After a reboot, a perfectly working OCS 2007 installation has stopped working. I cannot start the Front End service. The event log lists a few errors, none of which I've been able to diagnose (in the order they appear)

Event Type:      Warning
Event Source:      OCS Archiving Agent
Event Category:      (1011)
Event ID:      30518
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
If you are federating, you might want to turn Archiving Notification ON for every Access Edge Server that may be deployed.

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

Event Type:      Warning
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14401
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
The current machine is not in the list of internal servers. This may cause the server to have interoperability issues.

Resolution:
Please check the Active Directory consistency or reinstall the server.

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

Event Type:      Information
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14492
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
The following known servers were recognized on startup:

Server: OCS2.mydomain.local; UniqueID: {39FEF3EE-4826-483E-A474-3D233C575E02}; Role: Enterprise Edition
Server: OCS1.mydomain.local; UniqueID: {AF0558D5-0D3D-4A95-80F5-441D10CF5ADE}; Role: Conferencing Server; Type: chat; Vendor: Microsoft Corporation
Server: OCS1.mydomain.local; UniqueID: {2AA31E32-B9D3-4E13-8574-BB783B04ADD8}; Role: Conferencing Server; Type: phone-conf; Vendor: Microsoft Corporation
Server: OCS1.mydomain.local; UniqueID: {D4A47659-B6D0-4F61-B582-04B70E464D3C}; Role: Conferencing Server; Type: meeting; Vendor: Microsoft Corporation
Server: OCS1.mydomain.local; UniqueID: {AA87CF6F-0A1D-4EC3-BD33-9FDBDE10564C}; Role: Conferencing Server; Type: audio-video; Vendor: Microsoft Corporation

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

Event Type:      Error
Event Source:      OCS Protocol Stack
Event Category:      (1001)
Event ID:      14352
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
Unable to start the stack.

Error: 0x0xC3E93C15 (SIPPROXY_E_NOT_INTERNAL_SERVER).

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

Event Type:      Error
Event Source:      OCS Server
Event Category:      (1000)
Event ID:      12326
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
Failed starting the protocol stack. The service has to stop

Error code is:0xC3E93C15 (SIPPROXY_E_NOT_INTERNAL_SERVER).
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.

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

Event Type:      Information
Event Source:      OCS AppDomain Host Process
Event Category:      (1029)
Event ID:      50004
Date:            10/27/2008
Time:            9:05:44 AM
User:            N/A
Computer:      OCS1
Description:
Stopped AppDomain - RtcAggregate, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

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

Event Type:      Error
Event Source:      OCS MCU Infrastructure
Event Category:      (1022)
Event ID:      61022
Date:            10/27/2008
Time:            9:05:45 AM
User:            N/A
Computer:      OCS1
Description:
Remote principal name is not configured in trusted server list.

The subject name OCS1.mydomain.local of the certificate assigned to process RtcHost(2224) was not found in the trusted server list.  
Certificate serial number: CN=OCS1, DC=mydomain, DC=local
Certificate issuer name: 611DC44C000000000002.
Resolution:
Verify that the Subject Name of the certificate presented by the remote peer is configured in the trusted server list.

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

Event Type:      Error
Event Source:      OCS MCU Factory
Event Category:      (1021)
Event ID:      51014
Date:            10/27/2008
Time:            9:05:45 AM
User:            N/A
Computer:      OCS1
Description:
McuFactory could not be initialized.

Office Communications Server MCU Factory could not be initialized.
Exception:
Operation is not valid due to the current state of the object..
Stack:
   at Microsoft.Rtc.Server.McuInfrastructure.HttpTransport.LoadCertificate(CertificateInfo certificate)
   at Microsoft.Rtc.Server.McuInfrastructure.HttpTransport.LoadCertificate()
   at Microsoft.Rtc.Server.McuInfrastructure.HttpTransport..ctor(String listeningUrl, ICccpConfigurationProvider config, XmlWriterSettings writerSettings)
   at Microsoft.Rtc.Server.McuInfrastructure.CccpAdapter..ctor(String listenerUri, ICccpConfigurationProvider config)
   at Microsoft.Rtc.Server.McuInfrastructure.McuFactoryCccpAdapter..ctor(String listenerUri)
   at Microsoft.Rtc.Server.McuFactory.McuFactory.TryCreateCccpAdapter()
   at Microsoft.Rtc.Server.McuFactory.McuFactory..ctor().
Resolution:
Look in previous event logs for more information about this error.




A few notes about the event logs above - one of the events reference an OCS server called OCS2.mydomain.local - this is an old deactivated server I used for testing - I'm not even sure why it's name is even showing up.
Also - the certificate authority is on the same server as the OCS 2007 machine, if that makes any difference.

Please advise. Thank you very much.
0
DVation191
Asked:
DVation191
  • 2
1 Solution
 
gaanthonyCommented:
Certificate Authority can not be colocated with any server that has OCS roles.

http://support.microsoft.com/kb/896557 might also apply so check that.
Also was the server was removed and re-added to the domain?
If the OCS 2007 server was removed from the domain and re-added, OCS 2007 Server application will not function properly as the SID, GUID property would have changed for
the OCS Server.  If this is the case the solution is to de-activate and re-activate the server roles to resolve.
0
 
DVation191Author Commented:
I deactivated the roles, re-ran the deploy server setup from the installation disc and reactivated the server. On the first reboot, everything came up okay. However, on the second reboot, all the OCS services wouldn't start. I had to manually start each service. Very odd.
0
 
gaanthonyCommented:
What was the very first and second warning or error on the second reboot?  Also look at the informational messages for clues.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now