Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

porkchopexpress (IS/IT--Management)
14 Dec 05 9:19
I have a problem with the same few PC's each month that register they have failed to update i get these two errors in the event log.

Event ID 10010
The server {4991D34D-80A1-4291-83B6-255585575} did not register with DCOM within the required timeout.

Event ID 7024
The Background Intelligent Transfer Service service terminated with service-specific error 2147942403.

When i look on the PC's i can see that they have a folder called Documents and settings\All Users.WINNT\ and the WINNT folder is empty (i guess due to corruption). Reading an article that i found is see there is supposed to be a folder called Network in the Documents and settings\All Users\Application Data\Microsoft\ folder

Is it possible that the BITS service is looking in the wrong location and failing?

I have also emptied the C:\WINNT\SoftwareDistribution folder.

This is happening on 2k SP4 and XP SP2 boxes

Can anyone suggest a way to sort this?

Thanks.
trock1004 (IS/IT--Management)
14 Dec 05 13:42
This sounds like a WMI problem.  Open Computer Management, right click on WMI Control and select properties.  Most likely you'll get something back that says it couldn't communicate with it due to the path it's looking at.

On the XP machines, search the registry for any entries pointing to the path "c:\WINNT\the rest of the path" and replace WINNT with Windows.  Then reboot your machine. XP shouldn't have anything on it relating to a WINNT directory.

Tony

linney (TechnicalUser)
14 Dec 05 14:34
porkchopexpress (IS/IT--Management)
15 Dec 05 5:49
Creating a 'Network' folder in the mystery All Users.WINNT folder seems to sort it on the 2k PC's it's looking like a different error on the XP boxes. They no longer seem to use the C:\Documents and Settings\All Users\Application Data\Microsoft\Network path, which is very odd.

Thanks.
porkchopexpress (IS/IT--Management)
15 Dec 05 6:24
The only problem is that the Network folder disapears when the machine is rebooted so next month i will see the same issue.
trock1004 (IS/IT--Management)
15 Dec 05 9:43
Hey, Porkchop, did you read my post?  Have you checked this?  I had the same type of thing happening in my network with a few of my XP machines.  After days of troubleshooting, I found this to be the culperit. Somehow the registry had been changed by an update.  There are other things such as re-registering the WMI component that may need to be done too but the path must be correct in the registry or that won't work either.

Tony

porkchopexpress (IS/IT--Management)
15 Dec 05 9:56
No i'd missed it soz i'll take a look at the XP PC's when i get chance.

Thanks.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close