BITS is self correcting and more. These are informational even and only looked at when there are other errors we are looking to fix.
Since you have no other failures noted I'm going with "clear the event log can carry on."
--> I'm getting a lot of requests like this because of that recent SCAM noted at http://forums.cnet.com/7723-6132_102-563986/scam-alert-are-you-getting-phone-calls-by-people-claiming-to-be-tech-support/?tag=contentBody;threadListing
These scammers have folk look at the event log and even if you don't fall for the scam you might try to fix the events you find there.
Our two networked Windows 7 computers ( 1 64-bit, 1 32-bit) have both started (since 6/12) posting many events of this type:
A new BITS job could not be created. The current job count for the user xxxx/xxx (60) is equal to or greater than the job limit (60) specified through group policy. To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increate the per-user and per-computer Group Policy job limits.
Yes, the spelling error "increate" is there. This is a minor annoyance now but I am concerned that it will interfere with future updates. (That spelling error also concerns me.)
How do I "complete or cancel the BITS jobs that haven't made progress by looking at the error"? That doesn't mean anything to me.
Thanks for any help; I'm a little concerned.