locked
Server Front-End service terminated with service-specific error 2147749891 (0x80041003). RRS feed

  • Question

  • Trying to get ths running and have only the following error in the event log and haven't been able to find an information on it.

     

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7024
    Date:  5/10/2007
    Time:  3:18:56 PM
    User:  N/A
    Computer: BATTLESTAR
    Description:
    The Office Communications Server Front-End service terminated with service-specific error 2147749891 (0x80041003).

     

    Thanks for whatever you can provide.

     

    Mike S.

    Thursday, May 10, 2007 9:14 PM

Answers

  • Hi Mike,

     

    It is difficult to tell what went wrong.

     

    Did you open wmimgmt.msc and check the Security tab?

     

    For the namespace root\CIMV2, you should have entries for "RTC Component Local Group", "RTC Local Administrators", RTC Local Read-only Administratory", "RTC Local User Administrators" and "RTC Server Local Group".

     

    1. Can you run wbemtest.exe
    2. Connect to the namespace "root\cimv2"
    3. click "Enum Classes"
    4. leave the superclass name field empty
    5. click OK
    6. select MSFT_SIPMCUSetting and double click on it
    7. click "Instances" and select one instance
    8. check the FQDN setting

    This should give you a hint at which state WMI access fails.

     

     

    As a second step in troubleshooting, I would enable verbose logging for WMI

     

    Click Start, and then click Run, type wmimgmt.msc, and then click OK.

    1. Right-click WMI Control (Local), and then click Properties.
    2. Click the Logging tab.
    3. Change the Logging Level to Verbose.
    4. Increase the maximum log size (for example, change it to 4000000).
    5. Click OK, and then close MMC.
    6. Stop the WMI service (net stop winmgmt), and then allow it to auto restart.
    7. Reproduce the error

    A good starting point should be the files in %windir%\System32\Wbem\Logs. Was there anything logged in one of the files during the error occurs?

     

    Thanks

    Bernd

    Monday, May 21, 2007 3:45 PM

All replies

  • Hi Mike,

     

    The error code indicates a problem with WMI and access rights (Access denied).

     

    Did anything go wrong during installation that got logged in the setup log files?

     

    Thanks

    Bernd

    Monday, May 14, 2007 9:28 AM
  • Hi Bernd

     

    I also get the same error messages.

     

    I've had no problems with installing OCS 2007 up to the point on starting the services

     

    I also did not create new Service Accounts, i manually created service accounts in my Domain, adding these service accounts to Full Domain Admins and Full Exchange Admins

     

    the service accounts are also part of the RTCUniversalServerAdmins, RTCProxyUniversalServices, RTCHSUniversalServices and RTComponentUniversalServices.

     

    I've tried everything from making them sysadmins on the SQL with Studio manager, but still no luck!

     

    Any suggestions?

     

    DasGood.

    Thursday, May 17, 2007 9:55 AM
  • Hi Bernd,

     

    I can find no errors in the setup log files.  I did discover that the error did not recur the next time I booted the server, so maybe this will occur infrequently.  Still, it would be nice to know how to fix it the next time.

     

    Mike

    Thursday, May 17, 2007 1:11 PM
  • Hi Mike,

     

    It is difficult to tell what went wrong.

     

    Did you open wmimgmt.msc and check the Security tab?

     

    For the namespace root\CIMV2, you should have entries for "RTC Component Local Group", "RTC Local Administrators", RTC Local Read-only Administratory", "RTC Local User Administrators" and "RTC Server Local Group".

     

    1. Can you run wbemtest.exe
    2. Connect to the namespace "root\cimv2"
    3. click "Enum Classes"
    4. leave the superclass name field empty
    5. click OK
    6. select MSFT_SIPMCUSetting and double click on it
    7. click "Instances" and select one instance
    8. check the FQDN setting

    This should give you a hint at which state WMI access fails.

     

     

    As a second step in troubleshooting, I would enable verbose logging for WMI

     

    Click Start, and then click Run, type wmimgmt.msc, and then click OK.

    1. Right-click WMI Control (Local), and then click Properties.
    2. Click the Logging tab.
    3. Change the Logging Level to Verbose.
    4. Increase the maximum log size (for example, change it to 4000000).
    5. Click OK, and then close MMC.
    6. Stop the WMI service (net stop winmgmt), and then allow it to auto restart.
    7. Reproduce the error

    A good starting point should be the files in %windir%\System32\Wbem\Logs. Was there anything logged in one of the files during the error occurs?

     

    Thanks

    Bernd

    Monday, May 21, 2007 3:45 PM
  • Hi Mike,

    Can you let us know the status of your issue? Were you able to find a resolution? If so, can you provid your fix for the rest of the forums to see? If not, can you go through Bernd's suggestions and post here?

    Thanks

    Friday, June 1, 2007 5:52 AM
  • Sorry for the delay in responding.  The error has quit occurring on it's own.  I would like to tell you what I did, except I didn't do anything.  I realize that it has been a while, but if there are logs that would be of use to you I can send them.
    Friday, June 15, 2007 2:43 PM
  • Hello Bernd,

     

    I also still have the same error as described (already had this in the private Beta).

     

    I could identify the instances, which refer to a previous Installation.

    The WMI verbose logging has created quite a lot of files and information, but since im new to WMI, w/ no meaning for me ;-)

     

    Could you please help me to find out how to fix this error?

    I could supply you with Logfiles, if that helps.

     

    Thanks,

    Marcus

    Saturday, July 21, 2007 2:58 PM
  • Why this post is marked as answered? i don´t see any solution yet for this thread.
    Capecol MCSA - MCTS Exchange Server 2007
    Sunday, September 20, 2009 7:04 PM