TONS of Batch response module events problems & errors & MP update problem..

Previous | Next

Latest post 01-29-2009 5:29 AM by Kaisho. 20 replies.

10-18-2007 3:35 AM

Pixel
Joined on 10-18-2007
Posts 21

TONS of Batch response module events problems & errors & MP update problem..

Hey,

I'm using scom 2007 in a very large enterprise and we keep on getting errors
from .js .vbs script files into the monitoring view.

I'm getting alot of different errors and most of them occour on way more
then one server, ive havent pasted most of the errors as of the 50,000chars
limit in the thread.

i've searched the web, i know some of these errors are bugs and the script
needs to be disabled or something to fix the problem. i need to fix these
issues asap, waiting for sp1 is too much time. anyone have any idea how
should i debug or fix most of this errors? im not just looking for solutions,
any idea i would take happily!

p.s: i also have a few script files that i wrote that scom tells me the
health service closed, giving this as an example as i know the scripts are
alright, i even launched them manually and they work without outputting any
errors.

i was told to download the latest mom2005 backward compability MP which i did, but still same situation.

now i have another issue cause of installing that mp.. this backward compability MP was installed on all
agents except a few agents in a different domain.
i went to the pending update agents view and approved the update using the
domain admin of the other domain, i cannot update them through the
console as they are secured servers with alot of security options and it just
wouldnt go through.
how can i check which updates these agents are missing? ive trying going to
the logs in the RMS' logs directory to check what updates were installed
successfully on other servers and then add the missing agents on the servers
that didnt get them, but i couldnt find logs corrseponding to those servers,
just some others.

i think the only thing missing on them is the update ive just done to the
backward compability MP, but i still want to check to be sure and still want
to know how to do this for the future

Description:

The process started at 3:03:52 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
"DiscoverSQL2005RSDiscovery.vbs" {4CC14CC2-E918-1733-726A-32631502C25B}
{95EF04AB-2DDA-AA11-7087-FACF341AEE50} STLBOWEB.masked.domain.com
STLBOWEB.masked.domain.com

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

Workflow name: Microsoft.SQLServer.2005.ReportingServicesDiscoveryRule.Server

Instance ID: {95EF04AB-2DDA-AA11-7087-FACF341AEE50}

Description:

The process started at 3:03:52 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
"DiscoverSQL2005DBEngineDiscovery.vbs" {E71360F6-C12E-8326-4539-FBC9D78862F5}
{95EF04AB-2DDA-AA11-7087-FACF341AEE50} STLBOWEB.masked.domain.com
STLBOWEB.masked.domain.com "Exclude:"

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

Workflow name: Microsoft.SQLServer.2005.DBEngineDiscoveryRule.Server

Instance ID: {95EF04AB-2DDA-AA11-7087-FACF341AEE50}

Description:

The process started at 11:55:07 AM was terminated because the HealthService
requested the workflow to stop, some data may have been lost.

Command executed: "C:\WINDOWS\system32\cscript.exe" //NoLogo "C:\Program
Files\System Center Operations Manager 2007\Health Service State\Monitoring
Host Temporary Files 1\769\LogEndToEndEvent.js"

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

Workflow name: Microsoft.SystemCenter.AgentManagement.LogEndToEndEvent

Instance ID: {4E577D68-1D87-2FFF-68CA-CDA0FEFC2625}

Description:

The process started at 11:52:25 AM failed to create System.PropertyBagData,
no errors detected in the output. The process exited with 1

Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program
Files\System Center Operations Manager 2007\Health Service State\Monitoring
Host Temporary Files 365\1914\LogicalDiskHealthCheck.vbs"
ALTIRIS2SRV.masked.domain.com D:

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

Workflow name: Microsoft.Windows.Server.2003.LogicalDisk.AvailabilityHealth

Instance ID: {91D6CF77-6D95-E44D-F93F-4C716D18076C}

Description:

Forced to terminate the following process started at 3:19:41 PM because it
ran past the configured timeout 60 seconds.

Command executed: "C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System
Center Operations Manager 2007\Health Service State\Monitoring Host Temporary
Files 56\1566\Hewlett-PackardProLiantServerDiscoveryScript.vbs" 0
{600ED414-A5F8-F901-6826-201CECEBDC76} {954F50D4-5451-7A8B-45CD-ADD392282230}
insimagt1srv.masked.domain.com insimagt1srv.masked.domain.com SNMP

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

Workflow name: HewlettPackard.Servers.ProLiant.HPProLiantServerDiscoveryRule

Instance ID: {954F50D4-5451-7A8B-45CD-ADD392282230}

Description:

The process started at 12:50:08 PM failed to create System.PropertyBagData,
no errors detected in the output. The process exited with 128

Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program
Files\System Center Operations Manager 2007\Health Service State\Monitoring
Host Temporary Files 706\122176\AD_General_Response.vbs"
cypdc03.masked.domain.com 4 false {E0219537-DE24-D858-9B4F-50FC2055DE52}

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

Workflow name: AD_General_Response.PerformanceCollection

Instance ID: {80309F97-9AC8-F2C1-14CE-44F0F32D4692}

Description:

The process started at 2:22:09 AM was terminated because the HealthService
requested the workflow to stop, some data may have been lost.

Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program
Files\System Center Operations Manager 2007\Health Service State\Monitoring
Host Temporary Files 98\232910\AD_Op_Master_Response.vbs"
meldc2.masked.domain.com false 3 12 {E0219537-DE24-D858-9B4F-50FC2055DE52}

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

Workflow name: many

Instance name: many

Instance ID: many

Description:

Forced to terminate the following process started at 5:18:00 PM because it
ran past the configured timeout 120 seconds.

Command executed: "C:\WINDOWS\System32\cscript.exe" "C:\Program Files\System
Center Operations Manager 2007\Health Service State\Monitoring Host Temporary
Files 9\12661\TopologyDiscovery.js" 0 {B75939D3-F929-EA18-FD6A-DB891229F15B}
{A4AE8F04-3BEC-7E71-423F-13CAD13BA8FC} false

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

Workflow name: Microsoft.Exchange.Topology.Discovery

Instance ID: {A4AE8F04-3BEC-7E71-423F-13CAD13BA8FC}

Filed under: SCOM 2007, events, scripting

10-18-2007 8:10 AM In reply to

adgross
Joined on 06-27-2007
Posts 8

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I have many of the same errors, about 20 per day from 48 managed nodes. This is not just annoying, it is causing the other Admins to start ignoring emails and alerts from OpsMgr. I was hopeful that the latest backward compatibility update would help, but it has not.

10-21-2007 6:47 AM In reply to

Pixel
Joined on 10-18-2007
Posts 21

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

yeah i know! same thing here man! the annoying thing is that microsoft would tell you to write the question in the right forum, but once you do, they dont answer as they dont have answers :(

besides, i dont understand why do they have like 9000000 websites for this technologies.. a community for this mom a community for that scom, a forum for this a forum for that, its all so not organised, specially when the forums dont look even related to microsoft.. its just hilarious, i hope somebody answers our prays, from microsoft or not. im posting this message for help on every forum i see for mom or scom because there are so many for them, ridicolous.. sigh..

Filed under: SCOM 2007, module events, problems, batch respone, community, errors, backward compability

10-25-2007 4:37 AM In reply to

Pixel
Joined on 10-18-2007
Posts 21

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

This suits microsoft so much..

i get no answers but yet they going around the globe promoting a system that has tons of bugs!

who the f*ck releases a system to the market with so many problems? freakin monopoly its outrageous

everyday i find out how bugged this system is.. new bugs everyday allday

10-25-2007 10:08 AM In reply to

Omarko
Joined on 10-25-2007
Posts 1

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

It is regrettable that your experience with OpsMgr has been so frustrating. Our team is committed to our customers and our goal is to have satisfied customers. The fact we were not able to achieve this for you with the initial release is very disappointing and we will do our best to recover your satisfaction.

I encourage anyone who is frustrated with OpsMgr to open a case with Microsoft Support. As customers report issues through Microsoft Support if they result in identifying an actual bug in most cases we are able to either provide a workaround or deliver a hot fix. Our team has invested a great deal in training our support professionals and they are working with customers everyday and have a great deal of knowledge on how to help customers recover from problems.

Finally, to further help address issues with OpsMgr we are just days from issuing a Release Candidate of Service Pack 1 (will be posted week of Nov 5th on the OpsMgr public beta site on Microsoft Connect). This RC is a true "candidate for release" and has been extensively tested and validated. It is also going to be 100% supported by Microsoft Support. It is also upgradeable to the final version of SP1 which is expected to ship in Q1 next year.

We highly encourage any OpsMgr customer that is experiencing problems to deploy this SP RC.

Thank you, Omar

Omar Kouatly (Microsoft OpsMgr Team PM)

10-25-2007 11:39 AM In reply to

ronin75
Joined on 02-21-2006
Posts 7

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I am also getting the same errors. I have found a few obscure posts that this may be the Virus Scan engine running on your systems that prevent or lock up the script execution. I am in the process of getting CM approval to add an exclusion for C:\Program Files\System Center Operations Manager 2007\Health Service State\

If this helps I will post back

10-25-2007 12:03 PM In reply to

adgross
Joined on 06-27-2007
Posts 8

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I set an exclusion for this folder on 4 of my biggest offenders. I'll let you know the results. I am running McAfee VirusScan 8.0i, 5200 engine.

10-25-2007 12:29 PM In reply to

adgross
Joined on 06-27-2007
Posts 8

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I figured it would take a little longer to prove the virus scan theory wrong, but it didn't. I already have an alert from one of the systems that I set the exception for.

10-25-2007 3:01 PM In reply to

the_newf
Joined on 08-09-2007
Canada
Posts 50

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

One thing in a previous post (paraphrasing here: "I ran the script manually and it worked without any problems") leads me to believe that this problem is not related to SCOM or a management pack specifically but to the configuration, but likely has more to do with security/account rights. There must be a difference in the rights that SCOM is using to execute the scripts.

I have found through my work with this product that the security and account rights must be correct for it to work properly. A necessity of the environment that I work with is that all systems function with the 'least priviledge' that is required for the component/application to run. I didn't have the option to make action accounts etc domain admins to get things to work. I followed the management pack guides to set security as a starting point and worked from there. Initially the troubleshooting was painful, but through process of elimination I managed to get everything working as it was intended. Well, there is one exception, there's a bug in the exchange mailflow script...which will hopefully be fixed in the next release.

I suggest that you investigate the security logs on the SCOM servers and on the agent managed systems and correlate SCOM events to security failures. The security failures will tell you "who" tried to do "what" to "whom". Start there. It might be a simple fix. I have found many authentication/security related glitches and weirdness with SCOM. These include: reporting attempting to authenticate via SQL login rather than windows login, and account names that were simply too long.

10-25-2007 3:41 PM In reply to

ronin75
Joined on 02-21-2006
Posts 7

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

Are you using epolicy to enforce exclusions? I had to set them at the epolicy level so it will net reset back. So far I have had the exclusion in for a few hours and no alerst yet and the one I did get I logged in locally to the server and checked the exclusions and the new exclusion had net set yet. I forced policy enforcement on the box and the new exclusion came down. So far nothing. I hope this is the real deal.

10-26-2007 9:39 AM In reply to

adgross
Joined on 06-27-2007
Posts 8

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I am not using ePolicy, so the exclusion should have taken effect immediately. I did have several more errors last night, so this did not resolve the problem in my environment.

However, I was pointed to a KB article by a Microsoft rep to try...again pointing to VirusScan as the culpret. Since I applied this to a handfull of managed nodes 14 hours ago, I have not had any errors from those servers. I'll let you know if this changes.

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

10-26-2007 11:35 AM In reply to

ronin75
Joined on 02-21-2006
Posts 7

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

well I broke down and called PSS today and it seems that you have to troubleshoot each error individually. I have a few systems that give me an error on the LogicalDiskHealthCheck.vbs script. It seems that the latest base OS MP has a bug in the WMI code of the vbscript where it includes network drives. The subsequent operations tries to do performance monitoring on the drives and it fails on the network mapped drive letter. The line of code specifically looks for win32_logicalDisk where drivetype=3 or 4 or 6. Type 4 is network drive. This is where the bug is. My other bug is a DISCOVERSQL2005RSDiscovery.vbs and a DISCOVERSQL2005ASDiscovery.vbs error which we have yet to troubleshoot. Hope this helps a bit. I think the FreeSapce.vbs script will also fail due to the same wmi query issue.

10-28-2007 6:59 AM In reply to

Pixel
Joined on 10-18-2007
Posts 21

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

first of all, thanks for everybody from the community who is trying to solve these issues together, good work.

the_newf:

the accounts i use to run the scripts are domain admins with local administrative rights as well on the servers. i tried to run the scripts with a various accounts including the SCOM accounts and they work perfectly, so i dont think its that.. specifically because its as i said.. domain admin :)

regarding what you saidL "i have found many authentication/security related glitches and weirdness with SCOM"

Thats exactly what i said.. SCOM ISSUES!

ill try to check the antivirus thing anyways, it might be that.. for reference.. we are using trendmicro here.

12-12-2007 10:17 AM In reply to

ssciarrino
Joined on 12-12-2007
Posts 1

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

I also have those LogicalDiskHealthCheck.vbs,FreeSapce.vbs and DISCOVERSQL2005RSDiscovery.vbs alerts. So did PSS give you a hotfix or just turn off those scripts, or did an override? Did they charge you for the call?

thanks.

12-13-2007 9:23 AM In reply to

adgross
Joined on 06-27-2007
Posts 8

Re: TONS of Batch response module events problems & errors & MP update problem..

Contact

My problems were largely solved by upgrading Dell OpenManage to version 5.3 and applying the SP1 RC to OpsMgr. I still get some messages from servers with earlier versions of OpenManage, but it's only a couple of older test servers that can't be upgraded to 5.3.

Page 1 of 2 (21 items) 1 2 Next > | RSS