Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The BITS job list is not in a recognized format. It may have been created by a different version of BITS. The job list has been cleared.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is BITS?
As per Microsoft: "BITS maintains a list of active jobs in a file. When BITS starts, it always loads this list of jobs first. This message is logged to inform you that BITS does not recognize the file format of the list. This happens when the file is corrupt, or the version of BITS that originally wrote the file is different from the version of BITS currently running. The latter happens if this is the first time that this version of BITS is running after a newer version was removed. If the file is corrupt and there were pending BITS jobs, the references to all partially downloaded files are now lost". See MSW2KDB for more details.
Upgrading BITS to the latest version might help resolve this problem. See ME842773 to upgrade to version 2.0. See the link to "BITS - New Features" for information on what brings new version 2.0.
BITS version 1.5 uses a different job list format. The next time a BITS job is submitted the job list will be purged and the error message will disappear. If you want to clear the error message right away you can manually clear the BITS job list by running the following commands:
- net stop bits
- del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*"
- net start bits.
According to a newsgroup post, this message occured after the installation of the latest version of the Microsoft Background Intelligent Transfer Service.
From a newsgroup post: "This should not happen when you upgrade from older versions of BITS to BITS 1.5. This kind of error message would be expected on a system where BITS was downgraded to an older version and the older version was loaded. Enable the BITS logging following these instructions:
reg add %BitsKey% /v LogFileFlags /t REG_DWORD /d 0xfbcf /f
reg add %BitsKey% /v LogFileSize /t REG_DWORD /d 20 /f
After this restart BITS.
Restart of BITS can be accomplished by the following commands
net stop bits
net start bits
Examine these logs:
* %windir%\system32\bits.log and %windir%\system32\bits.bak (if it exists)
* Client OS information (Win2k3 or WinXP or Win2000) and Service pack (if
* output of "dir %windir%\system32\qmgr.dll" command"
|Private comment: Subscribers only. See example of private comment|
|Links: ME331716, ME842773, BITS - New Features, BITS FAQ, BITS Whitepaper, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated