roland_fortis

21 Oct 2011 5:58 PM

Performance Utilization report

1) PerfDS error when executing the report

The report Performance Utilization does not correspond with the stored procedure it calls

I opened the report with Visual Studio and in the definition of the report the dataset PerfDS calls the stored procedure

dbo.[Microsoft_SystemCenter_Report_Performace_By_Utilization]; in the parameters defined for this the call to the stored procedure has as first parameter @DataAggregation: the stored procedure from the MP does not have this parameter. I adapted the report to remove the parameter in the PerfDS dataset, deployed it and then it works.

2) At my company I have a datawarehouse which is used by two managementgroups; it would like to take the parameter @ManagementGroupId in consideration for the dataset Groups in the report

3) The Groups DataSet gives all defined groups; it should only give groups where the members are of type Computer, e.g. in the list of group Active Directory, AD Domain Controller Group (Windows 2003 Server), ... are present; when selecting these the report does not return data because I presume the members of the group are not of type Windows Computer

It is a nice report but it could be beter at certainly the management pack should make sure the reports call the stored procedures with the correct parameters

Roland

Kevin Holman

21 Oct 2011 6:11 PM

@roland_fortis -

1. Removing the dataset from the report is not the right approach. The report will potentially redeploy and break it again unless you copied it to a new location. The correct approach is to modify the stored proc in SQL to add in the missing item: "@DataAggregation INT," I am not sure why this didnt deploy correctly in your specific environment, but I assure you it is environmental. At least one other customer has reported this same behavior, but it is very rare. Interesting.

2. You will need to re-write the report for that, or open a DCR.

3. You are correct - this report could be optimized from that perspective.

Felyjos

21 Oct 2011 6:39 PM

Hello Kevin,

How to get an individual report to work on more than 10 occurences only for this report... (10 is fine for most graphs)...?

Are they existing report already?

Thanks,

Dom

stellar19

21 Oct 2011 10:36 PM

Just wondering if anyone else has seen an abnormal amount of Security login failures EventID 4625 for the SDK account post installing this MP? My domain admin notified me its hammering our DCs with upwards of 50000 failures a day.

An account failed to log on.

Subject:

Security ID: DOMAIN\DSISRVC_Q_SCOMSDK

Account Name: DSISRVC_Q_SCOMSDK

Account Domain: MTOLYMPUS

Logon ID: 0x2e129

Logon Type: 3

Account For Which Logon Failed:

Security ID: NULL SID

Account Name:

Account Domain:

Failure Information:

Failure Reason: An Error occured during Logon.

Status: 0xc00002fd

Sub Status: 0x0

Process Information:

Caller Process ID: 0xd3c

Caller Process Name: C:\Program Files\System Center Operations Manager 2007\Microsoft.Mom.Sdk.ServiceHost.exe

Donald Dsouza

25 Oct 2011 8:42 PM

Hi Kevin

In the new version of the mp the Logical Disk Free Space monitor alert not showing the % or value free space left. Is there any bug is opened to fix this issue?

Kevin Holman

25 Oct 2011 8:48 PM

@Donald - I discussed this in a previous comment:

You are correct - the free disk space alert description was changed. There are no immediate plans to change this that I know about. HOWEVER - if this impacts any customer's business process, the BEST way to have any MP changed, is to call PSS, open a case, and ask them to file a DCR or RFH on your . That's it. DCR = design change request and RFH = request for hotfix. This has the most impact, because it is YOUR business case that effects change. So, if you want to see this workflow design change, or ANY change to a MP, and can communicate the business impact, the next step is yours. :-)

Value over 100 %

25 Oct 2011 9:23 PM

Hello Kevin,

I noticed on Network Adapter: Average Percent Bandwith Used I have value 109%, 105%, 102% what does this mean!!! How could it be over 100%!!!!

Thanks,

Dom

Kevin Holman

25 Oct 2011 9:52 PM

@Value over 100 % -

This can happen from discrepancies in perfmon at the time the data is collected, or a flaw in the math used in the script which collects the data.

The bandwidth is collected from WMI in the script by looking at:

nCurrentBandwidth = GetWMIProperty(oInterface, "CurrentBandwidth", wbemCimtypeUint64, ErrAction_None)

nBytesSentPersec = GetWMIProperty(oInterface, "BytesSentPersec", wbemCimtypeUint64, ErrAction_None)

nBytesReceivedPersec = GetWMIProperty(oInterface, "BytesReceivedPersec", wbemCimtypeUint64, ErrAction_None)

nBytesTotalPersec = GetWMIProperty(oInterface, "BytesTotalPersec", wbemCimtypeUint64, ErrAction_None)

The counter output is methematically generated by using the below formula:

Counters.Add CN_PercentBandwidthUsedRead, CalculatePercent(nBytesReceivedPersec,nCurrentBandwidth/8)

Counters.Add CN_PercentBandwidthUsedWrite, CalculatePercent(nBytesSentPersec, nCurrentBandwidth/8)

Counters.Add CN_PercentBandwidthUsedTotal, CalculatePercent(nBytesTotalPersec,nCurrentBandwidth/8)

It is very possible there is some logic flaw in using this calculation. I used a slightly different method in my calculation - but also heard some customers report it was above 100% in some cases. I'd imagine that the formula needs some tweaking to be 100% perfect, given that this is a script and is performing a mathematical caluclation at runtime.

Were your NIC's hammered at that time?

I have also seen issues in virtualized environments and on server 2003 where "Current Bandwidth" is reported incorrectly, and this will skew the results.

Felyjos

25 Oct 2011 11:30 PM

It is the Exchange environment which is occupying the first 6 position then one configuration manager server.

I picked one exchnage mailbox server and running perfmon now...

Bytes Received/sec ==> floating 40/60 ...

Bytes Sent/sec ==> Flat at 100

Bytes Total/sec ==> Flat at 100

Current Bandwidth ==> Flat at 100

so I think it might still be real unfortunately.

All are physical servers DL360 or PoewerEdge 1950

I am checking with the Network team ... as it seems to be the same subnet as well (:

Thanks,

Dom

Maekee

26 Oct 2011 12:14 PM

After updating to this MP Version i started getting ALOT for these:

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "C:" with id:"{ACFAEF0C-2EE1-A392-1542-C7086D239AF6}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "J:" with id:"{D66C40BE-8BD4-7672-6280-B8B609859D7F}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "G:" with id:"{CFC2CCA9-B2ED-869A-B71F-EB77882AB37A}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "H:" with id:"{66316FE7-98BA-54A3-6D5B-CBFDA580BD45}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "E:" with id:"{FD8F9377-2F45-636C-9FE3-DFDE975F75B0}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "Q:" with id:"{E81FDAF2-F21B-1A7C-86CD-E5EDDF5E1E73}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "I:" with id:"{016411C8-3747-B397-BDA4-A5B90A68548C}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "F:" with id:"{60FE7A35-B9A9-613C-D7D5-79654A408166}" cannot be initialized and will not be loaded. Management group "MG001"

Rule/Monitor "Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace" running for instance "D:" with id:"{F44935A8-B4F9-1107-111E-496A2107F67D}" cannot be initialized and will not be loaded. Management group "MG001"

Will these stop arriving soon? So far i have about 5887 of these events last 24 hours

Help

Logical Disk Free Space

26 Oct 2011 12:59 PM

I have the same problem of Maekee with the version 6.0.6957.0 . I fix the problem editing the overrides Management packs manually, deleting the logical disk overrides, and recreating from the console, my question is ¿What happen if I import this version(6.0.6958.0) now?

Thanks Kevin!!

TomaS

27 Oct 2011 12:07 PM

Did anyone see an error like this? I could not import reporting MP on Server 2008 sp2 with OpsMgr SP1+971541+2028594 with upgraded databases and reporting services from 2005 to 2008 ? Any idea? Thanks!

Invalid Management Pack

Invalid Management Pack : C:\Program Files (x86)\System Center Management Packs\Windows Server Base OS System Center Operations Manager 2007 MP\Microsoft.Windows.Server.Reports.mp .: XSD verification failed for management pack. [Line: 1594, Position: 12]

The element 'Definition' has invalid child element 'Report' in namespace 'schemas.microsoft.com/.../reportdefinition&. List of possible elements expected: any element in namespace 'schemas.microsoft.com/.../reportdefinition&.

Per or Per Team?

31 Oct 2011 9:49 PM

Hello,

After checking with the Network Team the servers seem to be running high but not critical as it shows...

Is the Bandwidth performance done per NIC or per Team?

Thanks,

Dom

Jim DeVries

3 Nov 2011 9:29 PM

I'm not sure if this is a bug or a feature, but in the last release the new Performance by Utilization report was showing the logical disk instances with the highest percent of idle time, even though the report was supposed to show the servers most heavily utilized. I had to edit the stored procedure to return the busiest instances. Was that addressed at all?

Thanks,

-Jim

Kevin Holman

3 Nov 2011 11:44 PM

Jim - this was fixed in 6.0.6958.0. It was reversed in 6.0.6957.0. Are you sure you are on the latest version? We re-released it very quickly and included several fixes.