Change timeout of script

Mon, 09 Jun 2008 09:09:27 Z

Hi,

I'm looking for a way to change the timeout value of a script In SCE 2007 SP1.
The specific script is one of quite a few failing with a timeout error.
So far I've been able to locate the monitor using the script, but the timeout value is greyed out. The location is:
Authoring: Management Pack Objects/Monitors/Agent/Entity Health/Availability/Managed Computer update server configuration monitor/script
Is there a way to change the timeout value for the below script:
CheckWUAgentConfig.vbs

Best regards,

Michael Pultz-Hansen

Change timeout of script

Tue, 10 Jun 2008 07:39:29 Z

Hi Michael,

This monitor which contains the scrips belongs to System Center Essentials 2007 Management Pack which is sealed, that's the reason why you cannot modify the time out value.

Did this error occur on one specific client or on several clients?

--------------------
Regards,
Eric Zhang

Change timeout of script

Tue, 10 Jun 2008 07:57:43 Z

Hi Eric,

I see this timeout error (and several other) on several clients. The specific error I experience is:

Forced to terminate the following process started at 07:49:57 because it ran past the configured timeout 30 seconds. Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "CheckWUAgentConfig.vbs" CG-SYS_MG Working Directory: C:\Programmer\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 11\975\ One or more workflows were affected by this.

Can I change the timeout value in the MP xml file:

Microsoft.SystemCenter.Essentials.2007.{6B0A0E1F-9339-E84F-4A8C-56FC7B4C9AE4}.{F2BF1A19-89DD-1806-BF9F-8C648A796B27}.xml

Best regards,

Michael

Change timeout of script

Wed, 11 Jun 2008 13:01:47 Z

Hi Michael,

As this MP is sealed, so you cannot modify it, did you find any error on the event viewer on the problematic client?

--------------------
Regards,
Eric Zhang

Change timeout of script

Wed, 11 Jun 2008 13:18:24 Z

Hi Eric!

I just checked a couple of the problematic clients and they have 4 warnings. The OS is Windows XP SP3 (Danish), so I've tried to translate the error messages.

Source: WinMgmt Error: 35

WMI ADAP could not read performancelibrary ASP.NET, because it returned invalid data: 0x0

Source: WinMgmt Error: 40

WMI ADAP could not create object Win32_PerfRawData_ASPNET_ASPNETApplications for the performancefile ASP.NET, because error 0x80041001 was returned.

Source: WinMgmt Error: 35

WMI ADAP could not read performancelibrary ASP.NET, because it returned invalid data: 0x0

Source: WinMgmt Error: 40

WMI ADAP could not create object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 for the performancefile ASP.NET_2.0.50727, because error 0x80041001 was returned.

I guess the scipt uses ASP.NET 2.0 ??

Best regards,

Michael

Change timeout of script

Wed, 11 Jun 2008 13:34:31 Z

Hi Micheal,

In SCE console, under Agent managed, look at your version column. If they are not all at version 6.0.6278.0 then update them.

Also, if the version is 6.0.6278.0, please delete the problematic cilent and push the agent to it again, then check whether the problem will still exists.

--------------------
Regards,
Eric Zhang

Change timeout of script

Wed, 11 Jun 2008 14:06:41 Z

Hi Eric,

All my agents are version 6.0.6278.0.

I made and uninstall of one of the agents and then pushed the agent again.

So far I haven't seen the timeout error, but I still see the 4 errors in the eventlog...

I'll se if the timeout error returns tomorrow, as I'm on my way home, I'll update you tomorrow.

Best regards,

Michael

Change timeout of script

Thu, 12 Jun 2008 09:27:03 Z

Hi Eric,

after uninstall and install of a few of the problematic clients, it seems as if the timeout error has disappeared. I'll keep monitoring the clients in the next few days and let you know if the problem is in fact gone.

Best regards,

Michael

Change timeout of script

Fri, 13 Jun 2008 12:28:48 Z

Hi Eric,

the problem has disappeared on some clients, but on others we still get the timeout error and the question is if it isn't going to be a problem in time on those clients which at the moment are OK...?

Have you any suggestion as to what to do next?

Best regards,

Michael

Change timeout of script

Mon, 16 Jun 2008 10:24:08 Z

Hi Michael,

For this timeout issue, I think we can resolve it in this way:

As we cannot modify the timeout setting in this monitor as the MP is sealed, we could disable this monitor and recreate the monitor in a new MP and change the timeout setting to what you want.

1. Open SCE console, navigate to "Authoring" space, choose "Management Pack Objects" - "Monitors"

2. In the details pane, select "Agent" - "Entity Health" - "Availability" - "Managed Computer update server configuration monitor".

3. Right click it and choose "properties". In the script tab, copy the script.

4. Disable this moniotr.

5. Create a new unit monitor, the type is "Timed script two state monitor", you can save it in default management pack.

6. The target is "Agent", the parent monitor is "Availability", then copy the script into it and set the timeout value to a long value.

--------------------
Regards,
Eric Zhang

Change timeout of script

Tue, 17 Jun 2008 10:10:31 Z

Hi Eric,

I've tried to disable the original script and then create a copy of the script. This seemed pretty straightforward...

Now the copy of the script exits with the following error:

The process started at 11:36:53 failed to create System.PropertyBagData, no errors detected in the output. The process exited with 4294967295 Command executed: "C:\Windows\system32\cscript.exe" /nologo "nyConfigWsus.vbs" Working Directory: C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\ One or more workflows were affected by this. Workflow name: UIGeneratedMonitor9ec07547bf1e4b889bab4b4145b631b9 Instance name: PC091CG.compugame.dk Instance ID: {2331A930-ADCC-BE3B-147B-66F1AA2D3A45} Management group: CG-SYS_MG

As I can deduce it tries to run the script nyConfigWsus.vbs in the root of the system instead of in this path: C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\

I've tried to paste this command to a cmd prompt on the affected system:

C:\Windows\system32\cscript.exe" /nologo "C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\nyConfigWsus.vbs" Working Directory: C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\

With that command there's no error.

How do I change the path to nyConfigWsus.vbs from:

c:\nyConfigWsus.vbs

C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\nyConfigWsus.vbs

I expect the "Monitoring Host Temporary Files 9\1353\" is different from client to client and from time to time...

Best regards,

Michael

Change timeout of script

Tue, 24 Jun 2008 06:23:36 Z

Hello!

Does anyone have a suggestion regarding the path problem described above??

Best regards,

Michael

Change timeout of script

Wed, 25 Jun 2008 10:04:17 Z

Hi Michael,

Sorry for the delay, did the error appear again? I tried several tests in my environment, but cannot modify the path.

--------------------
Regards,
Eric Zhang

Change timeout of script

Wed, 25 Jun 2008 10:16:53 Z

Hi Eric,

Yes the error is still present, though I've disabled both the original script and the new in an effort not to clutter the SCE Console whith irellevant errors.

I'm pretty sure it's a path problem - does the error number mean anything to you?

Best regards,

Michael

Change timeout of script

Tue, 30 Jun 2009 08:06:01 Z

The process started at 11:36:53 failed to create System.PropertyBagData, no errors detected in the output. The process exited with 4294967295 Command executed: "C:\Windows\system32\cscript.exe" /nologo "nyConfigWsus.vbs" Working Directory: C:\Program Files\System Center Essentials 2007\Health Service State\Monitoring Host Temporary Files 9\1353\ One or more workflows were affected by this. Workflow name: UIGeneratedMonitor9ec07547bf1e4b889bab4b4145b631b9 Instance name: PC091CG.compugame.dk Instance ID: {2331A930-ADCC-BE3B-147B-66F1AA2D3A45} Management group: CG-SYS_MG

Was this issue ever resolved? I am experiencing the same error code.