Client not reporting back????

[James Brown]

HI,

I am getting the following error on my Windows 2000 cleints

2006-01-09 12:41:50 1248 1a0 Report WARNING: Reporter failed to upload
events with hr = 8024000c.
2006-01-09 12:41:50 1248 1a0 Report WARNING: Reporter failed to upload
events with hr = 8024000c.
2006-01-09 12:41:50 1248 1a0 Report WARNING: Reporter failed to upload
events with hr = 8024000c.
2006-01-09 12:41:50 1248 1a0 Report WARNING: Reporter failed to upload
events with hr = 8024000c.
2006-01-09 12:41:50 1248 1a0 Report WARNING: Reporter failed to upload
events with hr = 8024000c.
2006-01-09 12:41:50 1248 1a0 Report REPORT EVENT:
{190CBA5F-4E7E-4FD6-9C7B-DA3F047D7E6F} 2006-01-09 12:40:29-0000 1 202 102
{00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Reboot completed.
2006-01-09 12:43:17 1248 1a0 PT Initializing simple targeting cookie,
clientId = 4dd0b041-356e-47c7-9d96-dd7d6f3b238c, target group = Test -
Notify and Install only, DNS name = PC??????.DOMAIN.COM
2006-01-09 12:43:17 1248 1a0 PT Server URL =
http://server/SimpleAuthWebService/SimpleAuth.asmx
2006-01-09 12:43:17 1248 1a0 Report Uploading 1 events using cached cookie,
reporting URL = http://server/ReportingWebService/ReportingWebService.asmx
2006-01-09 12:43:17 1248 1a0 Report WARNING: Failed to upload events to the
server with hr = 80244008.

Dones anyone know how to fix this,

I can update the client but its not reporting back???

Thanks

James

[Melinda]

I am also having issues with a few clients not reporting back. I don't get
the same errors you have below, but I do get a 0x8024001b. Do you get this
error? I have yet to be able to fix my issue (checked registry settings,
redeployed the client)

[Lawrence Garvin (MVP)]

>2006-01-09 12:43:17 1248 1a0 PT Initializing simple targeting cookie,
>clientId = 4dd0b041-356e-47c7-9d96-dd7d6f3b238c,
>target group = Test - Notify and Install only,
>DNS name = PC??????.DOMAIN.COM

I would suggest simplifying the Target Group name. Specifically, remove the
spaces. The target group name configured in policy, and the target group
name configured on the server must be =identical=.

Also, I'm assuming you've "masked" the DNS name of the client PC. However,
if you want the -best- help available, editing diagnostic logs, for whatever
reason you seem necessary, will not advance that cause. For all I know, and
couldn't possibly tell you, you could have a defective DNS name for this
client which is causing the problem.

> 2006-01-09 12:43:17 1248 1a0 Report WARNING: Failed to upload events to
> the
> server with hr = 80244008.

0x80244008 - SUS E PT SOAPCLIENT PARSEFAULT

Something in the information you're sending to the SOAP server on the WSUS
system doesn't like what you've configured. Most likely it's the Target
Group name, but DNS names are known to be common culprits in these errors as
well.

"James Brown" <nowhe...@nogoodplace.com> wrote in message
news:uFta57RF...@TK2MSFTNGP10.phx.gbl...

[Lawrence Garvin (MVP)]

Melinda, it would be better for you to start your own thread about your
specific circumstances and error messages. I suspect what you're
experiencing is nowhere at all related to James' situation, and it would do
neither of you any service to clutter up the discussion about his situation
with unrelated notes about yours.

0x8024001b - WU E SELFUPDATE IN PROGRESS

The 0x8024001b error means..... Be Patient. The Client is trying to do what
its supposed to be doing. If this error appears for more than an hour, I
would suggest doing the following:

1. Stop the Automatic Updates service.
2. Remove the registry key and all values at
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
3. Restart the Automatic Updates service.
4. Inspect the WindowsUpdate.log after 30 minutes.

"Melinda" <Mel...@discussions.microsoft.com> wrote in message
news:BFF45027-1E2E-4140...@microsoft.com...

[James Brown]

I have now resolved my issue, I did the following:

Checked in SQL Server Enterprise Manager :-

Management >> Current Activity >> Locks / Process ID

Spid Blocking update of database tables

Checked server log 'SoftwareDistribution.log' and this showed deadlock
errors

Info w3wp.5730 GenericDataAccess.ExecuteSP Deadlock exception
caught while executing spGetUpdateServerStatus in GenericDAL. Retrying...

Errors:

Also noted the error below :-

System.Data.SqlClient.SqlException: Violation of UNIQUE KEY constraint
'nc3EventInstanceConstraint'. Cannot insert duplicate key in object
'tbEventInstance'.

Checked table 'tbComputerTarget' - Some computers had duplicate entries

In SQL Query Analyzer :-

use SUSDB

select FullDomainName, LastReportedStatusTime

from tbComputerTarget

order by 1, 2

Also noticed that many entries (LastReportedStatusTime) were from 3 months
ago!

Discovered the following table 'tbConfigurationC' that defines the maximum
amount of entries allowed for 'MaxEventInstances' in the 'tbEventInstance'
table - This appears to be written to when each client communicates back to
the server.

Checked how many entries were currently in the table. Over 1 million!!!

select count(*) from tbEventInstance

Decided to implement the following steps :-

1.. Remove duplicate entries in the 'tbComputerTarget' table
There were only a handful of these so from sorted table removed by machine
name and where the date was not the current day :-

DELETE from tbComputerTarget

where FullDomainName = 'computername.domain.co.uk'

AND DATEDIFF (Day, LastReportedStatusTime, getdate())<> 0

2.. Clear down the table 'tbEventInstance' as MaxEventInstances value
reached.
Although this is supposed to be handled automatically it appears to cause
multiple deadlocks on the database. Managed to do this simply by deleting
all the entries in the table over 30 days old. Time stamp was referenced
from the field 'TimeAtServer'.

DELETE from tbEventInstance

Where DATEDIFF (Day, TimeAtServer, getdate()) > 30

This reduced the entries from over 1 million to 320,000. Following this the
deadlocks dispappeared and new entries successfully wrote back to the table.

Hope this helps

James

"Lawrence Garvin (MVP)" <onsi...@news.postalias> wrote in message
news:eQ$8jraFG...@TK2MSFTNGP15.phx.gbl...

[xx]

This can happen if the event table (tbEventInstance) in your WMSDE
database has exceed 1M events. Caused by lots of clients or increased
detection frequency set on the clients. The default purge time is 2K
events/12hours. You can try changing the following configuration.

Default:
AutoPurgeDetectionPeriod = 12
AutoPurgeClientEventAgeThreshold = 15
AutoPurgeServerEventAgeThreshold = 90

New:
AutoPurgeDetectionPeriod = 1
AutoPurgeClientEventAgeThreshold = 7
AutoPurgeServerEventAgeThreshold = 30

[Lawrence Garvin (MVP)]

Interesting... I've not seen anything that directly relates a SOAPCLIENT
PARSEFAULT error to an oversized tbEventInstance table in the database.

Do you have a =reliable= source for this information?

"xx" <x...@xx.com> wrote in message
news:%23tcR5fM...@TK2MSFTNGP14.phx.gbl...