D
dylan
I'm having a problem with just about all of my users where the BITS
service won't start up, and they therefore cannot download updates.
When I try to start up BITS manually, I get the following error in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/19/2007
Time: 10:07:36 AM
User: N/A
Computer: AM-SAWES
Description:
The Background Intelligent Transfer Service service terminated with
service-specific error 2147500053 (0x80004015).
I found some posts suggesting to reregister dlls, but that didn't fix
the problem. I did however discover that the RPC service is set to
Log On as the Network Service account. According to this microsoft
article, http://www.microsoft.com/resources/.../en-us/sys_srv_default_settings.mspx?mfr=true
RPC is supposed to be set to log on as LocalSystem. If I change RPC
back to log on as LocalSystem, BITS starts up without a problem. Does
anyone have any idea how that would have been changed? I looked
through our group policies and it's not in there anywhere. I found
that in Windows 2003 Server, SP2 changes that setting, did an XP
update change it at some point as well?
Thanks
Dylan
service won't start up, and they therefore cannot download updates.
When I try to start up BITS manually, I get the following error in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/19/2007
Time: 10:07:36 AM
User: N/A
Computer: AM-SAWES
Description:
The Background Intelligent Transfer Service service terminated with
service-specific error 2147500053 (0x80004015).
I found some posts suggesting to reregister dlls, but that didn't fix
the problem. I did however discover that the RPC service is set to
Log On as the Network Service account. According to this microsoft
article, http://www.microsoft.com/resources/.../en-us/sys_srv_default_settings.mspx?mfr=true
RPC is supposed to be set to log on as LocalSystem. If I change RPC
back to log on as LocalSystem, BITS starts up without a problem. Does
anyone have any idea how that would have been changed? I looked
through our group policies and it's not in there anywhere. I found
that in Windows 2003 Server, SP2 changes that setting, did an XP
update change it at some point as well?
Thanks
Dylan