BITS fails to launch with "general access denied" error

We're currently having an issue with a Windows Server 2012 R2 box with 57 missing updates.  So far, we've narrowed it down to a failure of BITS to launch, but there's very little information that we can find about what is causing the issue.

Every time I try to launch BITS, I get the error, "Windows could not start the Background Intelligent Transfer Service on Local Computer."  It also refers to a service-specific error code of -2147024891.

Within the System Event Log, I see, "The Background Intelligent Transfer Service terminated with the following service-specific error: General access denied error."

I don't see anything aside from that.

Any thoughts?  Thanks in advance.
Jody DavisSystems EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sam SungCommented:
this is a guide for windows 2003 server, try the same for your server, the paths to the folders are different
Sam SungCommented:
Jody DavisSystems EngineerAuthor Commented:
Thanks Sam - much appreciated.  Still having the same issues, I'm afraid.
Jody DavisSystems EngineerAuthor Commented:
For what it's worth; if anyone runs into this issue and was not able to resolve it, here are all the various bits of information I've found on the subject (including the links Sam was kind enough to suggest):

Unfortunately, none of this resolved the error.  One of my coworkers did resolve the issue yesterday, however, and I've verified that BITS is running again without issues.  I haven't been able to speak with him directly, but through another coworker, I gather that he used the following process to enable logging and from there, resolved the problem.

set BitsKey=HKLM\Software\Microsoft\Windows\CurrentVersion\BITS
reg add %BitsKey% /v LogFileFlags /t REG_DWORD /d 0xfbcf /f
reg add %BitsKey% /v LogFileSize /t REG_DWORD /d 20 /f
the key and dwords to turn on bits logging, what he used to find the problem access issue, permissions wise
i assume its set BitsKey..... and the other 2 lines

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jody DavisSystems EngineerAuthor Commented:
The answer was found by a coworker.  No points are desired for this, but I'd like to close this question, as it no longer needs resolution.  Posted the information above for the benefit of anyone else who might need it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.