After finally getting some clients installed, I have some of these alerts on almost every computer. Each is a little different depending on the script it wants to run. I can see inventory for some computers and not others. I can see some drive spaces for some computer and not others. Here are some of the alerts: Event Type:WarningEvent Source:Health Service ModulesEvent Category:NoneEvent ID:21405Date:5/21/2007Time:1:43:57 PMUser:N/AComputer:CMTCBODescription:The process started at 1:43:57 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0Command executed:"C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1325\WindowsComputerIPSubnetDiscovery2.vbs" 0 {07591DE1-AA11-BF6A-0EC1-2BDD0FB135A5} {0DF708AC-AC3D-D15A-FAE2-BA2BAED0C55C} 0.0.0.0 0.0.0.0 cmtcbo.cometind.comWorking Directory:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1325\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.WindowsServer.IPSubnetMembership.Discovery Instance name: Virtual Network Instance ID: {0DF708AC-AC3D-D15A-FAE2-BA2BAED0C55C} Management group: CMTSMS_MG For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:WarningEvent Source:Health Service ModulesEvent Category:NoneEvent ID:21406Date:5/21/2007Time:1:37:36 PMUser:N/AComputer:CMTADCDescription:The process started at 1:37:35 PM 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 1\481\ADLocalDiscoveryDC.vbs(1079, 5) Microsoft VBScript runtime error: Object required: '' Command executed:"C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\481\ADLocalDiscoveryDC.vbs" 0 {DA9FDA73-9E98-A61B-466B-19768F40907A} {C4DCC5B1-F6FC-AFF1-78C4-7C59188465A9} cmtadc.cometind.com CMTADCWorking Directory:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\481\ One or more workflows were affected by this. Workflow name: Microsoft.Windows.Server.2000.AD.DomainControllerRole.DCDiscovery Instance name: cmtadc.cometind.com Instance ID: {C4DCC5B1-F6FC-AFF1-78C4-7C59188465A9} Management group: CMTSMS_MG For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:WarningEvent Source:Health Service ModulesEvent Category:NoneEvent ID:21405Date:5/21/2007Time:1:43:25 PMUser:N/AComputer:CMTADCDescription:The process started at 1:43:25 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 4294967295Command executed:"C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\3368\WindowsComputerIPSubnetDiscovery2.vbs" 0 {07591DE1-AA11-BF6A-0EC1-2BDD0FB135A5} {7153369C-A7BA-9F93-D962-0A8FB29617E9} cmtadc.cometind.comWorking Directory:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\3368\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.WindowsServer.IPSubnetMembership.Discovery Instance name: Local Area Connection Instance ID: {7153369C-A7BA-9F93-D962-0A8FB29617E9} Management group: CMTSMS_MG For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Would you login to one of the affected machines and try to run one of these scripts manually to see if it returns an error? Try this one for example and let us know if it runs successfully or generates an error.C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1325\WindowsComputerIPSubnetDiscovery2.vbsAre there resource issues on these machines prior to SCE agent installation? High CPU or memory utilization can impact script execution. Also check cpu / memory util of the MonitoringHost.exe process in Task Mgr on affected machines and report if that appears to be unusually high.

I've run the script, but I see no return information on it. I just ran from command line and it just comes back to the c: prompt. As for utilization, this is on a very underutilized server as we haven't moved many people on it yet. The task mgr process for monitoringhost.exe is either 0 or 1 percent. Everything else looks good.

I have been having this issue with ops mgr and discovered that the path doesn't exist. Looking into the directory structure where ops mgr says this script exists "Monitoring Host Temporary Files 1" doesn't exist but "Monitoring Host Temporary Files 2" does. In that directory several of theerrors list numerical dirs that dont exist like "2456" but I have directory "2454" as well as a bunch of others. Not sure why this is because I haven't editited the management pack or rules (yet). Doing a search I have found the script and manually created the path with that script to see if I get any errors when ops mgr CAN get to the script. I'll post again when I get results. Just to clarify we are just evaluating ops mgr and are running the eval copy in a lab. I'm only getting these errors in the AD management packs. All clients are W2k3 with a SQL 2005 backend for the ops server. We have to manually install the agents due to strict network ACLS where only the agent port and auditing port are open between agent and ops mgr server ( following the supportted configuration whitepaper).

Looking at it closer, I see what you mean. In the error, the path is completely different then what is on the drive at the time. I'm guessing SCE makes these temp directories on the spot, and then deletes them afterwards. I don't know if one of the support guys can confirm this and help us understand why these scripts are failing. Any help, or results you have would be appreciated. I'm going to try to just find some of the ones that aren't working and run them as now I know the path is not correct. Thanks!

Pete, After finding the paths are different from the error at the time, I tried running a script that failed on one of the server. The script was teh "DiscoverWindowsComputerProperties.js" script. I got a message box that reads: Windows Script Host Script c:\program files\system center operations manager 2007\health service state\monitoring host temporary files 4\734\DiscoverWindowsComputerProperties.js Line: 37 Char: 1 Error: Subscript out of range Code: 800A0009 Source: Microsoft JScript runtime error Can you tell me what is wrong with that, and also, does SCE just put on the script to a computer then erase it once it runs?? is that why the path is always different then the error since I'm guessing it's already tried it and erased it?

After I changed the path everything is running fine but the last thing I want to do is change the paths to these scripts on the ten servers we have in the lab. I may change the MP instead but I would like to see an explaination of why the paths are all screwed up. Is the Agent not getting configurations from the server? Is there a patch needed, am I an id10t? I'll will post more when I find and I'll keep my eye on this is incase you have come across something.

I had the dis-joint domain problem and waited for that to be hotfixed. When I was able to finally install SCE, now I am having the same problem you are with the script failures on every client. I think I will uninstall and wait for SP1. For a trial edition, this is way too much work.

I'm seeing the exact same error with my SCE install and the scripts not running correctly. The paths are off because the temp folders are no longer present exactly as they should be. Also, I cannot see the software inventory of my managed PCs. SCE is showing which Windows Updates are installed/missing, but no other software is being reported. I guess this is due to the scripts not executing properly. Thanks. Ken

Yes, scripts run in temporary directories that are regularly deleted and recreated. This is normal behavior. To find the script mentioned in the alert message, you can search under the current temporary directory. Dustin

Dustin, I think we have figured out where to find the scripts, its just now a question as to why they fail. I definitely have multiple scripts on either clients or servers that fail, and have never run. What can be done to clear these alerts and try the script again, or how do we track down and fix the script error?

I have a same problem with script or executable failed. While i searsch for the script, it is not located in the same location, but in another temporary folder. If i run the script from this directory it exits without any error message.

Have anyone found a solution to the problem? Or is it a manual fix for all managed computers?

I'm looking for info on this as well. I deployed SCE today and I have this issue for 90% of my workstations/servers. Has MS responded to the issue yet?

I'm encountering the same problem and I hope there will be a solution soon. Thx in advance, Marco

I'm also having the exact same problem on all of my monitored clients. Any response from the moderators on this issue?

I am also experiencing this. However it is in the System Center Operations Manager environment. Thanks, Nick

There are three known issues with scripts failing and alerts being generated for the resultant failure. If you are seeing this error message in an alert, you'll need a QFE that will be available shortly (KB 936339 Command executed:"C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\3368\WindowsComputerIPSubnetDiscovery2.vbs" 0 {07591DE1-AA11-BF6A-0EC1-2BDD0FB135A5} {7153369C-A7BA-9F93-D962-0A8FB29617E9} cmtadc.cometind.comWorking Directory:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\3368\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.WindowsServer.IPSubnetMembership.Discovery Until then, you can disable the Microsoft.SystemCenter.WindowsServer.IPSubnetMembership.Discovery and Microsoft.SystemCenter.WindowsClient.IPSubnetMembership.Discovery object discoveries in the Essential's console Authoring space If you are seeing this error message, we are working on fixing this MP for Essentials SP1. Command executed:"C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\481\ADLocalDiscoveryDC.vbs" 0 {DA9FDA73-9E98-A61B-466B-19768F40907A} {C4DCC5B1-F6FC-AFF1-78C4-7C59188465A9} cmtadc.cometind.com CMTADCWorking Directory:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\481\ One or more workflows were affected by this. Workflow name: Microsoft.Windows.Server.2000.AD.DomainControllerRole.DCDiscovery Until then, you can disable the AD DC Local Discovery (DC Role). If you are seeing this error message, we are working on fixing this MP for Essentials SP1. Description: Forced to terminate the following process started at5:47:08 PM because it ran past the configured timeout 20 seconds.Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "RedirectWSUS.vbs" 0 {26D3CA4A-0EBA-57EB-2A74-589DAAFA8334}{D4D36ADB-F49F-F105-AB11-19688D2B7342} Duplicator.landrum.com Working Directory: C:\Program Files\System Center Operations Manager 2007\HealthService State\Monitoring Host Temporary Files 3\499\ One or more workflows were affected by this.Workflow name: Microsoft.SystemCenter.Essentials.WSUSRedirectDiscovery discovery. Until then, you can disable the Discover XP SP2 clients discovery. Dustin

Hi. JUST installed SCE RTM Eval, and I am not sure where I would disable the "Discover XP SP2 clients discovery" rule you mention. Can you help? Meanwhile, I will keep looking. Thanks! Garth

Open up authoring, expand management pack objects, click object discoveries and in the lookup box type XP SP2 clients. Right-click on Discover XP SP2 clients and click properties. Click the overrides tab and then click the disable button and choose the category in which the object you want to disable are located.

Thanks TroutMan. Did that. Added the overrides. Closed the alerts. Garth

Guys! How about this alerts? I have it on all management agents :-( Alert: Script or Executable Failed to run Source: VIDEO-SERVER.unicredit.lan Path: VIDEO-SERVER.unicredit.lan Last modified by: System Last modified time: 12.09.2007 11:58:39 Alert description: The process started at 11:58:20 failed to create System.PropertyBagData. Errors found in output: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1326\CPUUtilization.vbs(72, 9) Microsoft VBScript runtime error: Type mismatch: 'CDbl' Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "CPUUtilization.vbs" 95 15 VIDEO-SERVER.unicredit.lan 3.2016019225120544 Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1326\ One or more workflows were affected by this. Workflow name: Microsoft.Windows.Server.2003.OperatingSystem.TotalCPUUtilization Instance name: Microsoft(R) Windows(R) Server 2003, Standard Edition Instance ID: {2465C1CD-E476-6C37-2440-A081179EB0B1} Management group: UCB & Alert: Script or Executable Failed to run Source: VIDEO-SERVER.unicredit.lan Path: VIDEO-SERVER.unicredit.lan Last modified by: System Last modified time: 12.09.2007 11:58:39 Alert description: The process started at 11:58:20 failed to create System.PropertyBagData. Errors found in output: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1319\MemoryUtilization.vbs(47, 6) Microsoft VBScript runtime error: Type mismatch: 'CDbl' Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "MemoryUtilization.vbs" 2.5 VIDEO-SERVER.unicredit.lan 539. Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1319\ One or more workflows were affected by this. Workflow name: Microsoft.Windows.Server.2003.OperatingSystem.MemoryAvailableMBytes Instance name: Microsoft(R) Windows(R) Server 2003, Standard Edition Instance ID: {2465C1CD-E476-6C37-2440-A081179EB0B1} Management group: UCB

Thisis caused by the locale of the account under which SCE run these scripts. SCE thinks that the decimal separator should be something but the locale uses different decimal separator. The result is a failure in conversion (for example string 0.123456 to real/decimal number with decimal separator set to , by locale). It seems that everyone is affected by this issue, could Microsoft react somehow?

Hi, Thanks for your update. This is a known bug and we have been handling it. Personally, I think it will be corrected in SCE SP1. Thanks.

I am another Victom of this monster! I have Multiple Script failing on servers, we dont monitor clients. I hope somebody will come up with this solution.

I am having the same issue as well.. From other forums that I have looked at, some state that SP1 will fix all these issues - but to my dismay, SP1 isn't released yet, it is still in Release Canaidate mode Is this thread related? They seem to be and the resolution seems to be installing SP1 RC1 http://forums.microsoft.com/technet/showpost.aspx?pageindex=2&siteid=17&postid=2520512&sb=0&d=1&at=7&ft=11&tf=0&pageid=3 I registered with connect.microsoft.com and tried to download the service pack, but I can't seem to find it. Here is where I tried to download it from: http://www.microsoft.com/systemcenter/opsmgr/default.mspx And here: https://connect.microsoft.com/systemcenter?wa=wsignin1.0 Thanks,

If you have installed System Center Essentials and you are getting Cscript.exe errors, you may want to check the directory names that the script is pointing to. It appears that, a least in my case, the script is looking for a file in Program Files\System Center Operations Manager 2007 (which does not exist)instead of Program Files\System Center Essentials 2007. I thought about just renaming the folder, unfortuately, microsoft is using the Systems Center Essentials 2007 for other things, so Microsoft needs to fix the script and send out a patch. Tim Harris

i had the same errors too, butmy script errors came from AV mcafee virusscan (enabled scriptscan)

Alexey T wrote: Guys! How about this alerts? I have it on all management agents :-( Alert: Script or Executable Failed to run Alert description: The process started at 11:58:20 failed to create System.PropertyBagData. Errors found in output: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1326\CPUUtilization.vbs(72, 9) Microsoft VBScript runtime error: Type mismatch: 'CDbl' This problem stillexistinSP1. When it will be solved?PS. http://www.eggheadcafe.com/software/aspnet/30050790/script-fails-to-run-becau.aspx

I have these script errors also on a lot of my clients, I have applied SP1 but this didn't fix it. I have uninstalled and re-installed the agents but nu solution. What is the status of this problem?

I have the same error, as I believe everyone who uses it does. I am downloading SP1 and will keep you updated.

I am having SP1 installed and got Event ID 21406 error on one of the agent managed servers as: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2324\PrintServerDiscovery.vbs(391, 1) Microsoft VBScript runtime error: ActiveX component can't create object: 'MOM.ScriptAPI' Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "PrintServerDiscovery.vbs" {52A54AB3-2D5A-AACC-6D82-04AAA42EB595} {1FFFBB0E-4B57-7A6D-533B-5F38B7A4E2EB} sgvmmwt.core.umdnj.edu Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2324\ PrintServerDiscovery.vbs was found on the problematic server with the right path, manually run the script, the following error appeared: Line: 27 Char: 2 Error: The Handler is invalid Code: 80070006 Source: (null)

Hi, As the new report issue you mentioned is different from the one discussed in this current thread, we'd recommend that you start up a new thread for it. We generally focus on one topic in one thread because in this way it will be better for other community members to participate in the discussion, and to search/find specific answers more efficiently in the future. Thanks for your understanding.

I have installed SP1 after a fresh install of SCE on a new install of Server 2003 as well. We still have script errors all over the board, all of which have been posted earlier in this thread. Any word on when we can expect a fix for this?

Anotherone for the post SP1 install issues club (must be getting a solid membership by now)... I'm getting multiple script run failures - the majority are producing the timeout error similar to Forced to terminate the following process started at5:47:08 PM because it ran past the configured timeout 20 seconds. but a couple are also The process started at 2:50:13 PM failed to create System.PropertyBagData. Repeat offender scripts producing the errors are CPUUtilzation.vbs CheckWUAgentConfig.vbs DiscoverHealthServiceCommunicationRelationships.js DiscoverAgentRelationshipSettings.js LogEndToEndEvent.js DiscoverWindowsComputerProperties.js IsHostingMSCS.vbs Any clues anyone? Any updated timeframe on fixes from MS? This software holds such great promise, so I really would like to see it working propoerly. Cheers Dan

I'm having exactly the same problem as Dan09 after a SP1 upgrade.

I'm having the same problems :-( I guess we will now have to wait for SP2 to fix SP1

Yep, I'm running with SP1. I get about 50-100 of these per hour.

I'm getting the same errors as dan08 after installing SP1. Are there any work-arounds on these, until we get a permanent fix for it?

Anybody had any joy as yet? I also have the same scripts failiing as Dan above. SP1 installed.

Hello again, I'm still no nearer resolving these alerts, and am pretty much getting to the point of automatically closing them whenever they pop up. If anyone at MS has any clues, tips or fixes, please don't hold us all in suspense until SP2! (I'm happy to disable these particular alerts if someone can advise me how to identify them in the Authoring view) Cheers

exactly the same problem here, running SCE SP1 several clients both XP and VISTA failing on numerous scripts. discoveroffice2003.vbs, ipconfig.vbs etc etc... any resolution from MS yet ?

dan08 wrote: Hello again, I'm still no nearer resolving these alerts, and am pretty much getting to the point of automatically closing them whenever they pop up. That's what we've been doing as well. But lately we've found that these script initiated by cscript.exe seem to eat up 90-100% of the CPU as well as a lot of memory while they try to run for approx 10 minutes, which leaves the computer unusable while it lasts. How can we disable these scripts and what would be the effect? Regards, Stian

dan08 wrote: Hello again, I'm still no nearer resolving these alerts, and am pretty much getting to the point of automatically closing them whenever they pop up. If anyone at MS has any clues, tips or fixes, please don't hold us all in suspense until SP2! (I'm happy to disable these particular alerts if someone can advise me how to identify them in the Authoring view) Cheers Seriously MS... I've got hundreds of these alerts each week from practically every server across our enterprise. This issue appears to have been ongoing for over a year. Please communicate: Resolution status and ETA Clear and specific steps to disabling these scripts until a resolution is developedThanks.

Hi,I have the same problem. Not with Essentials, but with Operations Manager; the background must be the same, I think.I get a lot of Script or executable failed to run errors. The sources are from different management packs; scripts belonging to discovery and performance checking rules and monitors too. They give a timeout error.I have the most problems with Windows 2003 DNS management pack, which is unable to run its nslookuptest.js and conditionalnslookuptest.js files.I tried to run the according nslookup command from the command prompt, and it runs fine.I tried to run the script manually, and it runs fine.I reinstalled the agents.I removed the problematic management packs and reimported them.I tried to raise the timeout values with overrides for these scripts, thinking they need more time.I checked the antivirus software. Some of my servers run McAfee, some of them has Symantec. Both produce the same timeout error. I checked McAfee's ScriptScan component, it isn't enabled. I tried to disable the antivirus software, but I can't see any positive change.So finally I run out of ideas.

Let me answer a couple of questions here: Essentials does use temp directories for scripts being run on the agent, so search by script name rather than browsing to the directory, as the script location many not be the same on every run. For the Operations Manager question, if you have McAfee running, I would immediately suspect ScriptScan, a feature in McAfee famous (or infamous) for killing runtime scripts. Disabling ScriptScan is a pretty common fix in my experience. I've had users in the last 12 - 18 months report improvement in OpsMgr runtime scripts after disabling ScriptScan.

"Subscript out of range" is the error indicated by that error code. I would expect that on a Discovery script, as they have parameters that will likely not be apparent to an end user. And to have that somewhat global Discovery failing leads me to believe there could be health issues with the OS or perhaps 3rd party interference, like antivirus software. McAfee is pretty commonly mentioned in discussions related to OpsMgr runtime script failures.

Just to let you know, I had to remove DNS MP, it has a bug.

I have also a lot of script errors. Discovery communications etc. But how can i see where the scripts fail? In the alert discription there are a lot of numbers and also the mangement group name but how can i disable the scripts if i don't now which one?

Any fix yet? Thanks.Nuck

Same problem here on SCE SP1 latest available Management Packs.C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 8\1134\DiscoverAgentRelationshipSettings.jsRun manually gives the following:Script:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 8\1134\DiscoverAgentRelationshipSettings.jsLine: 12Char: 1Error: Subscript Out Of RangeCode: 800A0009Source: Microsoft JScript runtime errorthanks

Just noticed though as part of the errorMicrosoft.SystemCenter.DiscoverADManagedComputer.The subscript error I've detailed previously relates to a server that is NOT part of our W2K3 AD, the MG ServerIS part of our AD and they use certificates for mutual authentication so this could be part of the cause, not sure.

Can't explain the problem with these 2 though:C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 10\500\DiscoverWindowsComputerProperties.jsLine: 24Char: 1Error: Subscript out of rangeCode: 800A0009Souce: Microsoft JScript runtime errorC:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 10\1986\DiscoverHealthServiceCommunicationRelationships.jsLine: 12Char: 1Error: Subscript out of rangeCode: 800A0009Souce: Microsoft JScript runtime errorthanks

Has anyone got any futher with this aggrivating error? I'm running SCOM 2007 SP1 and are intermittently innundated with the "Script or Executable Failed to run" alerts - but there doesnt appear to be anywhere to overide the 120 second timeout or a working script anywhere!

Bump. Big BUMP

I second that!

Bump. Has been almost 2 months. Anyone?

Another Bump. Dustin are you there? Not getting anything from anyone.

Hi, This patch hlep me to fix this issue. Enjoy......... http://www.microsoft.com/downloads/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&DisplayLang=en Omkar umarani SCOM STUDENOmkar umarani SCOM STUDENT

Hi, This patch hlep me to fix this issue. Enjoy......... http://www.microsoft.com/downloads/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&DisplayLang=en Omkar umarani SCOM STUDENOmkar umarani SCOM STUDENT