Office Communications Server 2007 Front-End Service Status: Error Failure [0xC3EC79E6] Service failed to start as requested.
Hello
i just remove the beta 3 of OCS 2007 Uk and reinstall Windows 2003 Std UK Edition from scratch
i have installed the commercial version of OCS 2007 Std UK edition and follow all the task in the setup
when i try to start all the services the front end services doesnt start anyway
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 9/20/2007
Time: 7:32:24 AM
User: N/A
Computer: SRVOCS-NA
Description:
The Office Communications Server Front-End service terminated with service-specific error 3286842439 (0xC3E93C47).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
any ideas ?
Все ответы
Hello
I am having exactly the same issue
Fresh install followed all the instructions an easy install (compared with previous versions)
The last wizard start services
Failure
[0xC3EC79E6] Service failed to start as requested.on all services.
Spent many ours looking around the web and checking my settings with no joy.
Any help would be appreciated.
Thanks.
- Same error even after reinstall the server...
Any help is welcome
Thanks! It was the certificate (don't use a wild card)
If you look in the event viewer their is a communicator section check out the errors in there.
Burn Man
Hi,
I cannot find any information about a certificate problem in the communicator event viewer ...
What have you done to solve your issue ?
- I have run into the same issue as I am trying to productionise an OCS installation and parrallel run it with LCS so there are new DNS entries and don't really want to have to explain that we need to purchase several new certificates when they have a perfectly good wildcard.
Is there a good reason for this?
I remember in LCS that it did not like wildcards (at least the Access Proxy actually refused to install them), but they are valid certificates. Surely if someone wishes to use *. certs then they are entitled.
OCS or IIS for that matter had no problem installing them. - Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 13.11.2007
Time: 8:07:29
User: N/A
Computer: *****
Description:
The Office Communications Server Front-End service terminated with service-specific error 3286842439 (0xC3E93C47).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------
Setup gave me:
Service Name: RTCSRV
Descriptive Name: Office Communications Server Front-End
Service Status: Error
Failure
[0xC3EC79E6] Service failed to start as requested.
-----------------------------------------------------
For me also and when i messed with certificates, i got the following error
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 13.11.2007
Time: 9:18:44
User: N/A
Computer: OFFICECOM
Description:
The Office Communications Server Front-End service terminated with service-specific error 3286842381 (0xC3E93C0D).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
no communicator certificate error in event log also Philip,
It has been discussed and stated in the OCS forum that OCS 2007 also does not support wildcard certificates.
ok, so got a non wild cert and still the same errors. Has anyone got OCS working?
Any ideas?
Thanks!
hami
- Do you have any more information on the certificate? E.g. who was the issuing CA?
I got a free one from the internet. Trial for 90 day. I get an error on all services.
Starting Service Service Name: RTCSRV
Descriptive Name: Office Communications Server Front-End
Service Status: ErrorFailure
[0xC3EC79E6] Service failed to start as requested.Starting Service Service Name: RTCACPMCU
Descriptive Name: Office Communications Server Telephony Conferencing
Service Status: ErrorFailure
[0xC3EC79E6] Service failed to start as requested.Starting Service Service Name: RTCIMMCU
Descriptive Name: Office Communications Server IM Conferencing
Service Status: ErrorFailure
[0xC3EC79E6] Service failed to start as requested.Starting Service Service Name: RTCDATAMCU
Descriptive Name: Office Communications Server Web Conferencing
Service Status: ErrorFailure
[0xC3EC79E6] Service failed to start as requested.Starting Service Service Name: RTCAVMCU
Descriptive Name: Office Communications Server Audio/Video Conferencing
Service Status: ErrorAny ideas?
- Предложено в качестве ответаTigoInnocent 20 ч. 17 мин. назад
- Is the certificate valid on the server that you are installing it on? Did you need to install any CAs to make it work?
In my server All the services except front-end service are running fine.....
When I tried to run the service " Office Communications Server Front End " from Services.msc, it says " The System cannot fint the file specified" & the concerned file "RTCSrv.exe" is missing from the folder :- " C:\Program Files\Microsoft Office Communications Server 2007\Server\Core\ " .
if anyone out here can say how to restore this file in the desired folder, ll be greatful................
Thanks All..
Subrat.............
All, I'm having this problem also. Does anyone have a solution on this? I've looked all over. All other services are running but I can't get the "Front End" service to start.
This thread has dragged on for sometime. Does this mean we can the idea of using OCS??
Sytech
I have been troubleshooting this issue as well and there just doesn't seem to be an answer for this issue other than deactivating and uninstalling OCS and then make sure that you clean up the Schema before you reinstall. I have an internal CA that I use for certificates that has not been an issue.
I have had OCS up and running several times in a lab invironment and it has crashed twice once after an update was applied to the server and after the update was uninstalled I still could not get past the errors reported above and the other time was a hardware issue from I tried restoring from a backup and that also produced these same errors.
I am currently stuck trying to resolve the following error "The Office Communications Server Front-End service terminated with service-specific error 3286842439 (0xC3E93C47)." When I try to start the Front End Service which uses the RTCService.exe just the same as the IM Conferencing and Telephony Conferencing services and the same RTCService domain account. This tells me that there is not a problem with the login credentials.
I am currently using the Best Practices analyzer to see it that will help in resolving this issue. Will keep you all posted
http://support.microsoft.com/kb/937302
Message d'erreur lorsque vous essayez de démarrer un Multipoint Control Unit dans Communications Server 2007 : "0xC3EC79E6"
Numéro d'article : 937302 Dernière mise à jour : mercredi 15 août 2007 Version : 1.3 j'ai eu le même probléme dans mon serveur de prod.Symptômes
Lorsque vous essayez de démarrer un Multipoint Control Unit dans Microsoft Office Communications Server 2007, vous recevez le message d'erreur suivant :0xC3EC79E6Cause
Ce problème se produit lorsque Communications Server 2007 utilisent un certificat incorrect.Résolution
Pour résoudre ce problème, procédez comme suit :1. Exécutez l'Assistant de validation pour valider le serveur et pour situer le certificat incorrect sur le serveur. Exécutez les procédures pour cela : a. Dans les Communications Server 2007 Microsoft Management Console (MMC), cliquez avec le bouton droit sur le serveur que vous souhaitez valider et puis cliquez sur Validation. b. Dans l'Assistant de validation, cliquez sur Suivant et puis cliquez sur Validate local server configuration.
Note Cela situe le certificat incorrect sur le serveur.2. Utilisez l'Assistant Certificat pour créer un nouveau certificat. Exécutez les procédures pour cela : a. Dans les Communications Server 2007 MMC, trouvez le serveur qui a le certificat incorrect. b. Cliquez avec le bouton droit sur le serveur et puis cliquez sur Certificats. c. Dans l'Assistant Certificat, créez un nouveau certificat qui dispose du nom adéquat et n'importe quel Autres requis Noms (SAN) Sujet. d. Demandez le certificat auprès d'une Autorité de certification (CA) appropriée. 3. Lorsque le certificat est émis par l'autorité de certification, réexécutez l'Assistant Certificat pour attribuer le certificat nouvel au serveur. I tracked this back to the password for the RTCService domain account was out of sync with the password being used to start the service on the OCS server.
Sync'd em up and started all stopped services! On to the next problem....
- Hi,
Be sure to install a certificate the contains the FQDN of the RTC service.
Changing the certificate to one that has the FQDN will allow the service to start.- Предложено в качестве ответаKeep on Truckin 11 декабря 2008 г. 18:43
- How would I check to see if the passwords are out of sync? Help would be appreciated greatly.
Sgarvie IT Guy - this did the trick for me
Go to forest global properties and check the OCS FE FQDN should not be listed under "Edge Servers" tab- Предложено в качестве ответаsandokan75 14 сентября 2009 г. 11:19
- Thanks! this worked for me too. Went to forest global properties and removed the entry under "Edge Servers" tab. Mine was working fine until I had to reboot after a windows update.
- I am also facing same problem can any1 help meI have worked also with global propertiesBut yet not getting any successI need quick helpThanks in advanceRegardsSohaib Qazi
I had the same issue. Used a wildcard certificate at first. Created a new with an internal CA and finally the services are up.
- Thanks so much Grahamer, that worked for me...i spended all day trying to fix this and now its done...thansk again for the trick...
