Error 198 from Batch Patch Server

BatchPatch Forums Home Forums BatchPatch Support Forum Error 198 from Batch Patch Server

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #11934
    jsira7
    Participant

    Hi Doug,

    I have 2 Batch Patch servers (Server A, Server B) running in my environment. One for our IT Ops crew and the other for the System Engineers. When I try to initiate Download and Install Windows Updates on any target PC on Server A I am met with Error-198: Failed to add scan package service. HRESULT: -2147024674. I have confirmed from this server (Server A) that I am able to reach Windows Updates and am able to manually download the wsusscn2.cab file. Server B has no issues. I can Download and Install Windows Updates no problem. Would you have any idea why Server A is having this problem? I created a video that you can view to see what it’s doing. Link below:

    https://youtu.be/kVKKbwucg-0

    #11935
    doug
    Moderator

    0x8007000D The data is invalid. ERROR_INVALID_DATA

    This implies that there is probably an issue (presumably some type of file corruption) with the WsusScn2.cab file that ServerA is using. Either there was corruption when downloading it from Microsoft to ServerA, or the corruption is being introduced when ServerA copies it to the target computers. If you manually inspect the WsusScn2.cab file (both on ServerA as well as on a couple of targets) you can right click on the file and view ‘Properties > Digital Signatures’ as a way to verify that the file has not been corrupted/modified. If the Digital Signatures tab is present with signatures listed, then the file is good. If it is not present or if it is present but with no signatures listed, then the file is not good. If it’s not good then you can delete the WsusScn2.cab file and let BatchPatch re-download it. If it’s good on ServerA but not good on the targets, then the corruption is being introduced during the file copy from ServerA to the targets. This would be unusual, but it would imply that you have issues with your network.

    #11936
    jsira7
    Participant

    I checked the wsusscn2.cab on Server A and it was old. The location I checked was C:\Program Files\BatchPatch. I went ahead and deleted it but when I tried to deploy updates to another systems it has been trying to execute the download for the last 10 minutes. The two other machines I’m trying to deploy updates just state Queued. While I am not getting the error message yet, something seems to be preventing Batch Patch from downloading the cab file.

    Test1 Executing WsusScn2.cab downloader… – 10:52:37 System.Drawing.Bitmap ::Begin download – 2019-09-18 08:00:22 Test1 09/18/2019 08:00:48
    Wed-10:52:37> Windows Update: Executing WsusScn2.cab downloader…
    Test2 Queued WsusScn2.cab downloader… – 10:53:17 System.Drawing.Bitmap ::Begin download – 2019-09-18 10:49:18 Test2 09/18/2019 10:50:05
    Wed-10:53:17> Windows Update: Queued WsusScn2.cab downloader…

    • This reply was modified 5 years, 3 months ago by jsira7.
    #11938
    doug
    Moderator

    The age of the file wouldn’t be the issue, which is why I suggested looking at the digital signature in order to confirm if the file had been corrupted since the error message that you are getting indicates that the file is corrupted (a corrupted/modified file would not contain a valid signature). If your BP computer can’t download the WsusScn2.cab file then there is either a transient issue with Microsoft’s server or there is some kind of issue with your BP computer… not sure if you have a proxy or a web filter/firewall that prevents it from getting the file. In either of those cases you can certainly put the file there yourself, and then BP will use it.

    #11939
    jsira7
    Participant

    I am able to download from Server A manually, it’s just when Batch Patch tried to retrieve it is when I am getting the errors. I did as you suggested and manually copied the cab file to:

    C:\Users\msulimo\AppData\Local\Cocobolo_Software,_LLC\BatchPatch\cache

    That seemed to have resolved the issue for now.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.