Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Front-End service terminated (won't start) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Cheers,

    Installation went quite ok, except for the fact the the Front-End service won't start.

    From Event log:

    The Office Communications Server Front-End service terminated with service-specific error 3286842439 (0xC3E93C47)

    Is there a log somewhere that would give more details about the problem?

    Best regards,

    Mikael

    Monday, March 26, 2007 6:48 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    @Anonymous:

     

    Could you please open a new thread and provide a mail address where we could contact you. As the following possible solutions did not help, I will need log files from your machine.

     

     

    Solutions fixing Error 14517 up to now:

     

    Remove references to the own pool under

     

    - "Global Properties" | "Edge Servers" | "Access Edge and Web Conferencing Edge Servers"

    - "Global Properties" | "Edge Servers" | "A/V Edge Servers"

    - "Front End Properties" | "Host Authorization"

     

    Thanks

    Bernd

    Thursday, May 31, 2007 1:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    The best logs are now pushed to your system logs - you should have a bunch of errors listed in there. After installation, were you able to configure the system, attach certificates, etc.?
    Monday, March 26, 2007 7:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same problem.  I've tried to deauth/uninstall/reinstall a few times, but same error each time.
    Tuesday, March 27, 2007 6:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Im not sure if this helps, but

    LCSError.exe" 0xC3E93C47
    0xC3E93C47 -> (SIPPROXY_E_BAD_SERVER_CONFIGURATION)

     

    Well this dont tell me so much so post the errors from the event log.

    Tuesday, March 27, 2007 6:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My bad probably-- I didn't read the deployment instructions properly.

     

    I'll have another go at a fresh installation and see if it works better this time around.

    Tuesday, March 27, 2007 8:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Definately need more detailed information...can you attach setup logs, system logs, etc.?
    Tuesday, March 27, 2007 8:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The 2 service accounts are members of the correct groups according to the documentation. I even tried adding the service accounts to the Domain Admins group. A little more background: LCS2005SP1 server crashed. So I tried to set up a new server with OCS2007. Luckily, only our IT dept. uses this, but others are wanting it and the CIO wants it too. Any direction I should be looking?
    Tuesday, April 24, 2007 2:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi MarkO,

    Can you let us know the status of your issue? Did you find a solution? If so, can you post it for the rest of the forum to see? If you still have the issue please let us know ASAP?

    Monday, May 7, 2007 9:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm getting this error too.  I'm trying to run it on Windows Server 2003 with SP2.  Everything durring the install worked fine, until I tried to start services.  Everything else starts up but this.

     

    Here is the Windows Event entry:

     

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7024
    Date:  5/16/2007
    Time:  9:19:31 AM
    User:  N/A
    Computer: OFFICESVC1
    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.

     

     

     

    Here are event records from MOCS:

     

    Type: Date: Time: Source: Category: Event Id:
    5/16/2007 9:19:27 AM OCS Server 1000 12326
      Failed starting the protocol stack. The service has to stop

    Error code is:0xC3E93C47 (No Message Text Found).
    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.
    5/16/2007 9:19:27 AM OCS Protocol Stack 1001 14352
      Unable to start the stack.

    Error: 0x0xC3E93C47 (No Message Text Found).
    5/16/2007 9:19:27 AM OCS Protocol Stack 1001 14497
      One or more configuration errors were detected at startup.

    Cause: There are serious problems with the server configuration that prevented it from starting up.
    Resolution:
    Review the previous event log entries to identify failures. Alter the server configuration as required. If problems persist, contact product support.
    5/16/2007 9:19:27 AM OCS Protocol Stack 1001 14517
      The server configuration validation mechanism detected some serious problems.

    10 errors and 0 warnings were detected.

    ERRORS:
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {3669185A-48EA-F146-88FA-133177CB396A} and role 'Enterprise Edition' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {3669185A-48EA-F146-88FA-133177CB396A} and role 'Enterprise Edition' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A87E305F-AE6B-A54B-AAA1-9FFC665CEB62} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A87E305F-AE6B-A54B-AAA1-9FFC665CEB62} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A882188B-DD63-6247-8482-1DFA625CC71B} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A882188B-DD63-6247-8482-1DFA625CC71B} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {647BBD8D-D8F8-844F-9394-26135EDAED3C} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {647BBD8D-D8F8-844F-9394-26135EDAED3C} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A13C1A98-D638-BB42-86B8-ABFA305B3226} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A13C1A98-D638-BB42-86B8-ABFA305B3226} and role 'Conferencing Server' (version 3).

    WARNINGS:
    No warnings

    Cause: The configuration is invalid and the server might not behave as expected.
    Resolution:
    Review and correct the errors listed above. You also wish to review any warnings present.
    5/16/2007 6:05:17 AM OCS MCU Infrastructure 1022 61013
      The process DataMCUSvc(2532) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 3489, since 5/15/2007 3:32:51 PM.
    5/16/2007 6:04:26 AM OCS MCU Infrastructure 1022 61013
      The process AVMCUSvc(2440) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 3486, since 5/15/2007 3:32:44 PM.
    5/16/2007 6:04:03 AM OCS MCU Infrastructure 1022 61013
      The process AcpMcuSvc(2260) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 3486, since 5/15/2007 3:32:22 PM.
    5/16/2007 6:04:03 AM OCS MCU Infrastructure 1022 61013
      The process IMMcuSvc(2644) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 3486, since 5/15/2007 3:32:22 PM.
    5/16/2007 12:05:12 AM OCS MCU Infrastructure 1022 61013
      The process DataMCUSvc(2532) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 2049, since 5/15/2007 3:32:51 PM.
    5/16/2007 12:04:20 AM OCS MCU Infrastructure 1022 61013
      The process AVMCUSvc(2440) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 2046, since 5/15/2007 3:32:44 PM.

    Wednesday, May 16, 2007 2:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Patrick,

    OCS public beta is not supported on WIndows Server 2003 with service pack 2, only sp1 and R2.

    Thursday, May 17, 2007 10:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I get these identical error messages and I'm running on Server 2003 SP1.  I've gone as far as rebuilding my server with a new OS load and a new OCS install.  As soon as I install the Communicator Web Access on another server, the front-end service stops and will never start again.  It just generates these errors in the event viewer.  As soon as I uninstall the Communicator Web access from the front end server, the service will start just fine.  I even reloaded the front end server with a fresh OS install and a fresh Communicator web access deployment.
    Friday, May 18, 2007 3:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same error for me and I'm using SP1:

     

    The Office Communications Server Front-End service terminated with
    service-specific error 3286842439 (0xC3E93C47).

    I have uninstalled it and reinstall, no change.

     

    where can we get more details?

     

    Friday, May 18, 2007 6:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Also getting this same issue on an SP1 installation and now an SP2 installation.  Did a complete re-install and still no go.. Oddly enough, it was working when i first installed and then lost power on the server and upon reboot now the front-end service is not starting.  Still researching feverishly and will update when i find something....any updates for you?
    Sunday, May 20, 2007 12:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Patrick,

     

    I would guess two different things according to your logs:

     

    5/16/2007 9:19:27 AM OCS Protocol Stack 1001 14517
     

    The server configuration validation mechanism detected some serious problems.

    10 errors and 0 warnings were detected.

    ERRORS:
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {3669185A-48EA-F146-88FA-133177CB396A} and role 'Enterprise Edition' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {3669185A-48EA-F146-88FA-133177CB396A} and role 'Enterprise Edition' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A87E305F-AE6B-A54B-AAA1-9FFC665CEB62} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A87E305F-AE6B-A54B-AAA1-9FFC665CEB62} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A882188B-DD63-6247-8482-1DFA625CC71B} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A882188B-DD63-6247-8482-1DFA625CC71B} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {647BBD8D-D8F8-844F-9394-26135EDAED3C} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {647BBD8D-D8F8-844F-9394-26135EDAED3C} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different 'Treat As Authenticated' options. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (option is not set). Second server has GUID {A13C1A98-D638-BB42-86B8-ABFA305B3226} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [officesvc1.msdemo.masu.nodak.edu] have different server version numbers. First server has GUID {B2C03D09-F856-510E-8FE3-AFB5E0520FD3} and role 'Edge Server' (version 0). Second server has GUID {A13C1A98-D638-BB42-86B8-ABFA305B3226} and role 'Conferencing Server' (version 3).

    -> There seems to be a remainder from an old installation in AD. Did you check the RTC container in AD?

     

     

    5/16/2007 6:05:17 AM OCS MCU Infrastructure 1022 61013
      The process DataMCUSvc(2532) failed to send health notifications to the MCU factory at https://officesvc1.msdemo.masu.nodak.edu:444/LiveServer/MCUFactory/.
    Failure occurrences: 3489, since 5/15/2007 3:32:51 PM.

     

    -> I have seen these failures when using incorrect certificates. Did you check the certificates you configured? Did you use SelfSSL for obtaining a cert or did you install a Certificate Authority in your domain?

     

    Thanks

    Bernd

    Monday, May 21, 2007 4:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I actually have the same errors as well and have publicly CA certificates installed that match my front-end pool name but differ from the FQDN of my server name.  I don't see any refernece anywhere or a website listening on port 444.  what is that referencing?  Thanks. 

     

    Chris

    Monday, May 21, 2007 4:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The certificate was issued by an authority in the domain.
    Monday, May 21, 2007 4:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Patrick,

     

    Could you please check the following:

        Open the OCS MMC | your pool | properties | Host Authorization tab

     

    Do you have an entry in this list for the server FQDN? When removing this entry, does the Front-End service start?

     

    (This tip was provided by Roosenrunge in another thread)

     

    Thanks

    Bernd

    Tuesday, May 22, 2007 9:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bernd.

     

    Under the pool itself, i only have application properties (IM filter and Client version filter).  Under the status window for the general settings for the pool, the federation or global route FQDN comes up as blank.  RTCSRV Service still not starting...

    Tuesday, May 22, 2007 12:13 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

     

    I cannot ad a picture, so I am trying to describe where to find that information:

     

    - OCS Standard Edition:

    Open OCS MMC -> expand the "Forest" -> expand the "Standard Edition Servers" -> choose your pool -> right click "Properties" -> choose "Front End Properties" -> Check the "Host Authorization" tab

     

    - OCS Enterprise Edition:

    Open OCS MMC -> expand the "Forest" -> expand "Enterprise Pools" -> expand your pool -> choose "Front Ends" -> right click "Properties" -> Check the "Host Authorization" tab

     

    HTH

    Bernd

    Tuesday, May 22, 2007 12:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes i see.

     

    It is actually empty right now.  if i put my fqdn in there, still same error.

    Tuesday, May 22, 2007 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Christopher,

     

    By default, this list is empty and should not contain the pool FQDN. So your initial configuration was fine, please keep it.

     

    I would like to exchange some troubleshooting data with you. Where could I send you a mail with more details?

     

    Thanks

    Bernd

     

     

    Tuesday, May 22, 2007 1:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    send an email to winxnet@yahoo.com and i will reply with an actual email.  thanks!
    Tuesday, May 22, 2007 1:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     Bernd Ott [MSFT] wrote:

    Hi Patrick,

     

    Could you please check the following:

        Open the OCS MMC | your pool | properties | Host Authorization tab

     

    Do you have an entry in this list for the server FQDN? When removing this entry, does the Front-End service start?

     

    (This tip was provided by Roosenrunge in another thread)

     

    Thanks

    Bernd

     

    The FQDN entry list was empty.

    • Proposed as answer by mitchvs Tuesday, April 14, 2009 2:41 PM
    Tuesday, May 22, 2007 1:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Patrick,

     

    I would also like to get some data from your environment. Where could I send you a mail?

     

    Thanks

    Bernd

    Wednesday, May 23, 2007 1:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can send mail to demo@eddycs.com, thanks.

    Wednesday, May 23, 2007 1:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Similar problem here. Had an existing Server running ComServer2005SP1 and installed a new Server with Windows Server 2003 SP1 and Office Communicator 2007 Beta and after a reboot for Windows Updates neither server would start. The 2005 Server the LCS Service refuses to start and the ComServer2007 the Web Front-end will not start. We are actively working through our Premier Support Agreement on a solution.
    Wednesday, May 23, 2007 11:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    I just want to summarize several of the possible reasons for the Front End service not starting, together with the following Events in the System Eventlog:

     

    Event ID: 61013

    Source: OCS MCU Infrastructure

    The process <some MCU name here> failed to send health notifications to the MCU factory at https://<some FQDN here>:444/LiveServer/MCUFactory/.

     

    Event ID: 30710

    Source: OCS Snap-in

    Office Communications Server Snap-in failed to start service:

    Service Name=RTCSRV

     

    HRESULT = 0x8007042A

    Error Description = The service returned a service-specific error code

    Event ID: 12326

    Source: OCS Server

    Failed starting the protocol stack. The service has to stop.

     

    Error code is: 0xC3E93C47

     

    Event ID: 14352

    Source: OCS Protocol Stack

    Unable to start the stack.

    Error: 0x0xC3E93C47

     

    Event ID: 14497

    Source: OCS Protocol Stack

    One or more configuration errors were detected at startup.

    Cause: There are serious problems with the server configuration that prevented it from starting up.

     

    Event ID: 14517

    Source: OCS Protocol Stack

    The server configuration validation mechanism detected some serious problems.

     

    <xx> error and <yy> warnings were detected.

     

    ERRORS:

    <Here follows a list of errors>

    The details in the ERRORS section of Event 14517 can give you a hint in which section the wrong setting was applied.

     

    These errors indicate a problem with the current OCS configuration. Up to now, I saw this problem when there were references configured to the own pool under:

    - "Global Properties" | "Edge Servers" | "Access Edge and Web Conferencing Edge Servers"

    - "Global Properties" | "Edge Servers" | "A/V Edge Servers"

    - "Front End Properties" | "Host Authorization"

     

    HTH

    Bernd

     

     

     

     

     

     

     

     

    Thursday, May 24, 2007 11:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm getting errors 14517, 14497, 14352, and 12326.  I have checked the items that you suggested below and I have nothing referenced in those areas.  My host authorization is empty and I have no edge servers defined.  Like I mentioned before, both of the servers have been re-installed with a fresh install of the OS and the OCS installation.  The front-end service will start fine as long as I don't deploy the communicator web access to another server.  As soon as I deploy this to my front end server, the service stops running and it generates these errors.  Immediately upon removal the service will start again.

     

    Any other suggestions?

    Thursday, May 24, 2007 1:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Brilliant... got it.  Once I removed "Front End Properties" | "Host Authorization" reference to itself, it started up.  Now it's playtime.
    Thursday, May 24, 2007 2:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Not sure if this worked for others, but this solution did not work for me.  I was wondering if there were other suggestions that I could try.
    Wednesday, May 30, 2007 7:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    @Anonymous:

     

    Could you please open a new thread and provide a mail address where we could contact you. As the following possible solutions did not help, I will need log files from your machine.

     

     

    Solutions fixing Error 14517 up to now:

     

    Remove references to the own pool under

     

    - "Global Properties" | "Edge Servers" | "Access Edge and Web Conferencing Edge Servers"

    - "Global Properties" | "Edge Servers" | "A/V Edge Servers"

    - "Front End Properties" | "Host Authorization"

     

    Thanks

    Bernd

    Thursday, May 31, 2007 1:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Bernd.

     

    I created a new thread and included my email address.

     

    Front-end Service stops after deploying CWA

    http://forums.microsoft.com/Ocs2007publicbeta/ShowPost.aspx?PostID=1673986&SiteID=57

     

     

    Thursday, May 31, 2007 4:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     

    I can't tell you how happy I am to have found this solution that fixed my issue. It is absolutely ridiculous that the error codes don't directly reflect more of an answer. But, of course if they did that, I guess ultimately we would be out of a job, right.

    Monday, January 19, 2009 11:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having this same issue.  we are using a symantec product for virus checking and they require the fqdn of the front end servers in the host authorization tab.  When I do that I get the above error.  Any ideas?
    Wednesday, March 4, 2009 8:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This was exactly our problem.  When we removed the FQDN, the FE service started. 

    Thanks!

    Mitch
    Tuesday, April 14, 2009 2:42 PM