locked
Issues with MSMQ 5.0 RRS feed

  • Question

  • Hi

    we have MSMQ 5.0 installed on SCOM 2007 R2. For various reasons none of our MSMQ server is discovered.

    I've set up  a RunAs account  and assigned to designated servers, still no luck.

    If I restart HealthAgent on those server i get an alert:

    Alert: Script or Executable Failed to run

    Source:SVC1.contoso.net

    Path: SVC1.contoso.net

    Last modified by: Contoso\administrator Last modified time: 7/1/2011 12:33:13 PM Alert description: The process started at 08:14:42 failed to create System.Discovery.Data. Errors found in output:

     

    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 8\2108\DiscoverMSMQServer.vbs(218, 3) SWbemObjectSet: There are no more endpoints available from the endpoint mapper.

     

     Command executed:  "C:\Windows\system32\cscript.exe" /nologo "DiscoverMSMQServer.vbs" {7672DC74-3C18-ECF3-2CFA-C856B79B07BB} {A3D62AF9-9CEE-A131-3300-4157B4FD33DE} SVC1.contoso.net "" "true"

    Working Directory:    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 8\2108\

     

    One or more workflows were affected by this.

     Workflow name: Microsoft.MSMQ.2008R2.Server.DiscoverServer

     Instance name: SVC1.contoso.net

     

    Instance ID: {A3D62AF9-9CEE-A131-3300-4157B4FD33DE}

     

    Management group: SCOM_Contoso

     

     

    Alert view link: "http://SCOM-SRV:51908/default.aspx?DisplayMode=Pivot&AlertID=%7b92c5dcde-5ebd-4747-a832-c185e0f9b73d%7d"

    Notification subscription ID generating this message: {84F9FB7B-8D05-46A7-1223-AEA695A5CD5F}

     

    Any help/idea will be highly appreciated.

    Thanks,

     

    Friday, July 1, 2011 1:28 PM

All replies

  • Guessing you are on server 2003 still?

    http://support.microsoft.com/kb/839880

     

    Try this troubleshooting article from our support team.


    Microsoft Corporation
    • Proposed as answer by Vivian Xing Monday, July 4, 2011 7:05 AM
    • Unproposed as answer by FortyWinks Tuesday, July 5, 2011 12:39 PM
    Friday, July 1, 2011 5:34 PM
  • Hi

    Thanks for the answer but the article is focusing on W2k3 and AD&DNS issues.

    The MSMQ servers are Windows 2008 R2.

    Brgds,

     

    Tuesday, July 5, 2011 12:39 PM
  • If the discovery scripts are failing  because WMI is not able to assign any more endpoints, then you will need to get this situation remedied before the MP has a chance of working.
    Microsoft Corporation
    Tuesday, July 5, 2011 7:43 PM
  • Hi

    How could i check/ensure that this is the case?

    thanks,

     

    Wednesday, July 6, 2011 10:15 AM