Ask a questionAsk a question
 

AnswerFailed to create COM object errors followed by DAS errors

  • Wednesday, October 14, 2009 11:12 PMrfdswa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    I've asked this question previously and although we got a answer it didn't help at all - so since we were still in the installation phase we decided to reinstall the product in the chance we stuffed the install - people have pointed me to verifying the DAS account user/pass in the COM+ configuration for MOM but this is definitely not the problem.

    Fresh install of Retail FCS on Win2k R2 - patched to latest.

    The following events appear in the Application log:

    Event Type: Error
    Event Source: Microsoft Operations Manager
    Event Category: MOM Server
    Event ID: 25100
    Date:  15/10/2009
    Time:  6:57:22 AM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: JTSRV-FCS-01
    Description:
    Failed to create a COM object for inserting events into the database. Will retry every 15 seconds.

    Details: COM+ activation failed because the activation could not be completed in the specified amount of time.

    Table: Event

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Warning
    Event Source: Microsoft Operations Manager
    Event Category: None
    Event ID: 20607
    Date:  15/10/2009
    Time:  6:57:50 AM
    User:  NT AUTHORITY\NETWORK SERVICE
    Computer: JTSRV-FCS-01
    Description:
    The Data Access Server (DAS) on computer JTSRV-FCS-01 returned an error.
     
    System error code: -2147164124
    System error text: COM+ activation failed because the activation could not be completed in the specified amount of time.
    DAS method called: ConfigurationGetOnePointFreeSpace
    Called from file: d:\bt\4\private\product\core\engine\managers\perfcountermanager\src\momperfcountermanager.cpp
    Called from line: 984

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Any clues as to what the problem is?

Answers

  • Monday, October 19, 2009 8:02 AMrfdswa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Nick,

    Please feel free to close this off.

    For historical purposes (and in case anyone else has the same issue), our fix was as follows;

    We reinstalled FCS in Single Server topology by logging on and installed the prerequisites and FCS as the same user as the 'action / reporting account'. Whereas before we were logging in as a domain admin installed the prerequisites and ran the FCS install configuring the accounts as needed (e.g. domain admin installed, and then inputted the action / reporting  account). The biggest change that we can tell is that since SQL 2005 was installed with the same credentials as the action account permissions on all DB's were changed to dbo (even though in our previous attempts we followed the instructions to the letter with regards to account permissions).

    To date no DAS errors - problem solved..!!!

    thanks for all the feedback.

    Matt
    • Marked As Answer byrfdswa Monday, October 19, 2009 8:02 AM
    •  

All Replies

  • Thursday, October 15, 2009 3:30 AMNick Gu - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi  rfdswa,

     

    Thank you for your post again.

     

    I have read the former  post(DAS Error every 16 minutes ) .  If this issue still retains, you may “unmark” the answer and we will continue to support this issue.

     

    By viewing the event log, we saw error events(25100,20607) registered on the affected MOM Server JTSRV-FCS-01. It indicates that the DAS component hosted on JTSRV-FCS-01 isn’t running properly.

     

    To resolve this issue, please take the following actions on JTSRV-FCS-01:

    1.Go to Start / Run. Type dcomcnfg.
    2. Expand Component Services/ Computers / My Computer /COM+ Applications and open properties for Microsoft Operations Manager Data Access Server.
    3. Click the Pooling & Recycling tab.
    4. Change Pool Size from 1 to 10 and set Lifetime Limit from 0 to 9 minutes.
    5. Right-click “Microsoft Operations Manager Data Access Server” and click "Shut down".
    6. After a while, right-click “Microsoft Operations Manager Data Access Server” and click "Start".
    7. Restart MOM service.

     

    If anything unclear, please feel free to contact us.

     

    Regards,

     

  • Thursday, October 15, 2009 7:00 AMrfdswa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks Nick,

    Really appreciate the reply - we're currently reinstalling as we thought it may have been something in our configuration, however we have already done this twice before with the same outcome (e.g. same errors in the event log).  We'll get this one set up and if the same errors occur I will com back to you in the next 24 hours.

    again thanks (I've got heaps less hair now.. ;-)

    Matt
  • Monday, October 19, 2009 6:10 AMNick Gu - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Matt,

     

    I’d like to confirm whether there is any update about this issue. If anything unclear, please feel free to contact us.

     

    Regards,


    Nick Gu - MSFT
  • Monday, October 19, 2009 8:02 AMrfdswa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Nick,

    Please feel free to close this off.

    For historical purposes (and in case anyone else has the same issue), our fix was as follows;

    We reinstalled FCS in Single Server topology by logging on and installed the prerequisites and FCS as the same user as the 'action / reporting account'. Whereas before we were logging in as a domain admin installed the prerequisites and ran the FCS install configuring the accounts as needed (e.g. domain admin installed, and then inputted the action / reporting  account). The biggest change that we can tell is that since SQL 2005 was installed with the same credentials as the action account permissions on all DB's were changed to dbo (even though in our previous attempts we followed the instructions to the letter with regards to account permissions).

    To date no DAS errors - problem solved..!!!

    thanks for all the feedback.

    Matt
    • Marked As Answer byrfdswa Monday, October 19, 2009 8:02 AM
    •