locked
Script or Executable Failed to run Warning for RedirectWSUS.vbs RRS feed

  • Question

  • Hi We have configured SCE 2007 and after discovery and installation of SCE client in Health status of 70% of computers we are getting  below warning ...

     

    The process started at 3:10:06 PM failed to create System.Discovery.Data, no errors detected in the output. The

    process exited with 0 Command executed: "C:\Windows\system32\cscript.exe" /nologo "RedirectWSUS.vbs" 0 {26D3CA4A-0EBA-57EB-2A74-589DAAFA8334} {26764331-A936-0BAF-2F72-D446FC35478A}  < FQDN of PC >  Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\474\One or more workflows were affected by this, Workflow name:
    Microsoft.SystemCenter.Essentials.WSUSRedirectDiscovery Instance name: < FQDN of PC > Instance ID: {26764331-A936-0BAF-2F72-D446FC35478A} Management group: SCESRV_MG

     

    Any ideas...

     

    Tuesday, January 8, 2008 9:07 PM

Answers

All replies

  • I have the same problem

     

    The process started at 10:27:36 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0 Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "RedirectWSUS.vbs" 0 {26D3CA4A-0EBA-57EB-2A74-589DAAFA8334} {19E9C381-57F2-61A3-197B-399FB1C32CA3} <FQDN> Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\609\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.Essentials.WSUSRedirectDiscovery Instance name: <FQDN> Instance ID: {19E9C381-57F2-61A3-197B-399FB1C32CA3} Management group: <Group Name>
    Wednesday, January 9, 2008 3:40 PM
  • Hi,
     
    This problem has been reported to the product team.And it will be including the coming Service Pack 1 for SCE.
     
    Now we recommend you to disable "Discover XP SP2 clients" as a workaround.
     
    About "RedirectWSUS.vbs" please refer to the below thread:
     
    REdirectWSUS.vbs and WindowsComputerIPSubnetDiscovery2.vbs problem...
     
    Other similar post:
     
    Multiple Script or Executable failed to Run
     
    coutn me in on this one
     
    Hope it helps.
     

    Best regards,

    Xiu Zhang - MSFT

    Microsoft Online Community Support

    Thursday, January 10, 2008 3:39 AM
  • As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

     

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

     

    Thanks!

     
    Monday, January 14, 2008 1:38 AM
  •  

    We have something similare.

     

    The process started at 4:28:53 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0 Command executed: "C:\Windows\system32\cscript.exe" /nologo "RedirectWSUS.vbs" 0 {26D3CA4A-0EBA-57EB-2A74-589DAAFA8334} {93DB65BE-7321-A4DB-5690-C535C59F9312} computername.domain.local Working Directory: C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 5\472\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.Essentials.WSUSRedirectDiscovery Instance name: computername.domain.local Instance ID: {93DB65BE-7321-A4DB-5690-C535C59F9312} Management group: SERVERNAME_MG 

     

    Any idea why this is happening?  This System Center Essentials 2007 Active Allert is happening on our Windows XP, Windows Vista, and Widnows Server 2003 R2 operating systems. 

     

    Thanks,

     

    Tim

    Thursday, March 6, 2008 8:07 PM
  • Hi Tim,
     
    The coming Service Pack 1 for System Center Essentials 2007 will fix this problem. Also you can follow my previous post to disable there related rule.
     
    Hope it helps.
     
    Regards,
    Xiu Zhang - MSFT
    Friday, March 7, 2008 7:45 AM
  • This is done.

     

    Thanks,

     

    Tim

     

    Friday, March 7, 2008 7:59 PM
  •  

    I continue to have this issue with even after a clean install of SCE SP1.


    David

    Friday, April 25, 2008 6:52 PM
  • Hi,
     
    Warning generated on each machine or just the server?
     
    Best regards,
     
    Xiu Zhang
    Monday, April 28, 2008 9:52 AM
  • I am also experiencing this problem. I have updated SCE to SP1, and the workstations returning the alert are XP SP3.

    Any help would be gratefully recieved.

    Thanks in Advance,

    Jode

    Tuesday, August 18, 2009 3:06 PM