SCCM R2 Client Status Reporting Woes

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SCCM R2 Client Status Reporting Woes

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> SCCM R2 Client Status Reporting Woes

Page: [1]

Message

<< Older Topic Newer Topic >>

SCCM R2 Client Status Reporting Woes - 9/16/2008 11:53:25 AM

aellis

Posts: 53
Score: 0
Joined: 12/29/2003
Status: offline

I'm trying to find out if anyone has dealt with the following errors while running Pulse and Ping tasks in Client Status Reporting.

<9/16/2008 4:06:40 AM> Load Settings for Daily Task
<9/16/2008 4:06:40 AM> Done Loading Daily Task Settings
<9/16/2008 4:06:40 AM> Start to run daily task
<9/16/2008 4:06:40 AM> Invalid SQL error - Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.
Warning: Null value is eliminated by an aggregate or other SET operation.
<9/16/2008 4:06:40 AM> Failed to sync client summary in database

Now other task complete just fine:
<9/16/2008 4:06:40 AM> Failed to sync client summary in database
<9/16/2008 4:06:40 AM> Successfully updated current health in database
<9/16/2008 4:06:40 AM> Successfully updated history current state in database
<9/16/2008 4:06:40 AM> Successfully cleant aged records in database
<9/16/2008 4:06:40 AM> Successfully updated inactive clients in database

This error is preventing me from reporting on any Client Health Status. Here is the config of SCCM server hosting the Status Reporting:
Central Site Server (win2k3 SP2 x64)
SQL 2005 x64 Cluster on win2k3 sp2 x64

< Message edited by aellis -- 9/16/2008 11:55:47 AM >

Post #: 1

RE: SCCM R2 Client Status Reporting Woes - 10/1/2008 10:19:38 AM

ccowart

Posts: 7
Score: 0
Joined: 9/30/2007
Status: offline

I have the same problem. I was able to trace it back to the stored procedure CH_SyncClientSummary. On line 25 looks to be my problem, below is the line. I commented out this and everything worked properly. only drawback is that it doesnt tell me the site code for each machine.

SiteCode = ( Select Sites_DATA.SiteCode from Sites_DATA
Where CH_ClientSummary.MachineID = Sites_DATA.MachineID ),

(in reply to aellis)

Post #: 2

RE: SCCM R2 Client Status Reporting Woes - 10/1/2008 11:04:27 AM

jnelson993

Posts: 900
Score: 127
Joined: 2/18/2005
From: Minneapolis, MN
Status: offline

Egads, man. I wouldn't just comment out random lines of stored procedures that CM uses for it's inner workings...you don't know what other things it might affect and Microsoft would definitely not support it.

If you're really having a problem there, just change it from
( SELECT Sites_Data...
to
( SELECT TOP 1 Sites_Data

But really, you should be contacting MS to figure out why you're getting multiple records there. Either THEY messed up and should have put TOP 1 or you have some data issue that needs to be addressed.

_____________________________

Number2 (John Nelson)
MyITForum - Blog
MyITForum - Forum Posts

(in reply to ccowart)

Post #: 3

RE: SCCM R2 Client Status Reporting Woes - 10/1/2008 11:21:13 AM

ccowart

Posts: 7
Score: 0
Joined: 9/30/2007
Status: offline

I only did that in our test lab just trying to narrow down where the issue was. im going to give MS a call when i get a chance and see if its their issue or a issue with my data.

(in reply to aellis)

Post #: 4