After installing the April critical updates on Windows 2000 Server I am
receiving System Log error events from BITS. The critical update included an
update to BITS 2.0 (KB842773). The system log now shows event 16391 for user
N/A which occur daily, once per day. The error states that the BITS job list
is not in a recognized format and the job list has been cleared. Since the
error repeats daily, something must be recreating the a new job list in a
format that was OK with the old version and not OK with this update. I have
no idea of what is creating the job list. I've checked the scheduled tasks
to see if any are scheduled at the time that the event occurs, and have not
found any correlation. There seems to be some correleation with entries in
the Windows Update log, but they are not exact matches. Below are two
entries from each:
Event Log:
Type Date Time Source Category Event User
Error 4/20 8:29:05PM BITS None 16391 N/A
Error 4/21 3:17:09PM BITS None 16391 N/A
Windows Update.log
4/20 20:34:26 01:34:26 Success IUCTL Starting
4/21 15:22:29 20:22:29 Success IUCTL Starting
So, it seems that the BITS error is occurring about 5 minutes and 20 seconds
before the entries in the Windows Update log begin.
Any help would be greatly appreciated.
Sky King - 23 Apr 2005 14:34 GMT
Hi, Frank;
You are right that the new BITS 2.0 uses a different format than did 1.5
and that is the likely cause for your 16391 error. You should be able
to clear the BITS job list and thus clear the error by entering the
following at the cursor in a CMD window:
net stop bits
del "%ALLUSERSPROFILE%\Application
Data\Microsoft\Network\Downloader\*.*"
net start bits.
You should probably also manually download/install this update to BITS,
just in case the prior update did not fully complete or was corrupted
somehow:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3ee866a0-3a09-4fdf-8bdb
-c906850ab9f2&displaylang=en
HTH

Signature
...Sky
Tom "Sky" King
=============
> After installing the April critical updates on Windows 2000 Server I
> am receiving System Log error events from BITS. The critical update
[quoted text clipped - 8 lines]
> found any correlation. There seems to be some correleation with
> entries in the Windows Update log, but they are not exact matches.
.......