Event ID:1309.......seems to be happening to alot of people
Hello again,
Believe me when I say that I have exhausted all of my resources troubleshooting this error. I have read all the posts about and even tried some of the accepted solutions. Alas, I cannot clear these errors. I have however narrowed it down to 3 machines on my network trying to access the server that runs WSUS (not currently being used), and our help desk website. Let me give you a little history. these three machine are brand new to the domain but not new computers. They belong to a department that were previously on a separate domain using separate resources. I have checked the GPO, User accounts and folder permissions as sugested in many differant threads but still cannot seem to stop these error. Anyone have any ides?
Believe me when I say that I have exhausted all of my resources troubleshooting this error. I have read all the posts about and even tried some of the accepted solutions. Alas, I cannot clear these errors. I have however narrowed it down to 3 machines on my network trying to access the server that runs WSUS (not currently being used), and our help desk website. Let me give you a little history. these three machine are brand new to the domain but not new computers. They belong to a department that were previously on a separate domain using separate resources. I have checked the GPO, User accounts and folder permissions as sugested in many differant threads but still cannot seem to stop these error. Anyone have any ides?
Event ID: 1309
Logfile: Application
Computer: quest
User: NETWORK SERVICE
Source: ASP.NET 2.0.50727.0
Category: Object Access
Event Type: Warning
Message:
Event code: 3001
Event message: The request has been aborted.
Event time: 9/17/2008 2:08:50 PM
Event time (UTC): 9/17/2008 7:08:50 PM Event ID: 9c0d5d54a9744d06a06d908f67c30ed4
Event sequence: 54
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/784025969/ROOT/ClientWebService-5-128661474352547342
Trust level: Full
Application Virtual Path: /ClientWebService
Application Path: C:\Program Files\Update Services\WebServices\ClientWebService\
Machine name: QUEST
Process information:
Process ID: 5516
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpException
Exception message: Request timed out.
Request information:
Request URL: http://quest:8530/ClientWebService/client.asmx
Request path: /ClientWebService/client.asmx
User host address: 192.168.105.46
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 13
Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: Custom event details:
It looks to me like they are trying to go to a WSUS server that doesn't exist.
Is QUEST your server or these machine's old server?
Two Scenarios:
1) If it is their old server, you need to update group policy. GPO objects are saved on the root of each computer. They will have a GUID for each policy. Updatdating policy on the client, by going to the command prompt and typing GPUdate /force should contact your DC and updtate your PCs to the current policy.
2) If QUEST is a part of your domain as the WSUS server, then you still have an active policy that is probably a part of the default domain policy. This policy points the way to your server for updates, but the server is unavailable.
Either way, these machines are looking for a WSUS server that is unavailable.
Is QUEST your server or these machine's old server?
Two Scenarios:
1) If it is their old server, you need to update group policy. GPO objects are saved on the root of each computer. They will have a GUID for each policy. Updatdating policy on the client, by going to the command prompt and typing GPUdate /force should contact your DC and updtate your PCs to the current policy.
2) If QUEST is a part of your domain as the WSUS server, then you still have an active policy that is probably a part of the default domain policy. This policy points the way to your server for updates, but the server is unavailable.
Either way, these machines are looking for a WSUS server that is unavailable.
ASKER
QUEST is the WSUS server, and out of 300+ machines on the the network these three machine are the only ones throwing this error. The GPO is set properly and did not have this issue until we joined these new machines to the domain.
Is WSUS active on that server?
ASKER
It is active but not sending any updates yet. We are not ready to deploy yet. Like a said above, no other machine on the network are having a problem with the current setup. Just these three new additions. My thought lean toward a Group policy or permissions issue.
Well the list of permissions needed are on this page:
http://technet.microsoft.com/en-us/library/cc708545.aspx
These clients may not have checked in yet because they haven't recieved Win2000 updates for them, yet. When you deploy, you might get the Win2000 updates for them and see if they end up on the right track.
http://technet.microsoft.com/en-us/library/cc708545.aspx
These clients may not have checked in yet because they haven't recieved Win2000 updates for them, yet. When you deploy, you might get the Win2000 updates for them and see if they end up on the right track.
ASKER
Checked the permissions, and they match what is explained in the link posted above. Still unsure why only a couple of machines out of 300+ are having a problem.
Well, I have been working on other posts where only a couple machines are having problems. Let me do my homework and get back with you. I need to review some of my notes.
>1hr
>1hr
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, I'll give these a shot and see what happens
Any luck, boss?
ASKER
Honestly, I have been so busy working on this...
https://www.experts-exchange.com/questions/23703126/Starting-point-for-fiber-Conversion.html
I have not given it it's due attention. Thanks for the inquiry. I will revisit is when priority allows.
https://www.experts-exchange.com/questions/23703126/Starting-point-for-fiber-Conversion.html
I have not given it it's due attention. Thanks for the inquiry. I will revisit is when priority allows.
ASKER
Thanks
ASKER
Open in new window