Error -102

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #8601
    qwejibo
    Participant

    Hello,

    I’ve been using BatchPatch pretty much monthly for all of my servers for a couple of years now. I went to update my servers and now I get error -102 for all of them. We are using a WSUS server. It is synched up and seems to be happy. My servers are set via group policy to use this WSUS server. They will update manually. Since I updated batchpatch last week to version 2013.21.20.10 I get this -102 error. I’ve rebooted the WSUS server and a couple of the client servers and I still get error -102.

    #9522
    doug
    Moderator

    Could you provide me with the HRESULT code? You’ll find this in the error.log file in the remote working directory on a server that has thrown the -102 error.

    Thanks,

    Doug

    #9523
    qwejibo
    Participant

    EABW0811 05/02/2013 13:18:12> -102: Failed to execute the search. HRESULT: -2147020579

    EABW0811 05/02/2013 13:31:39> -102: Failed to execute the search. HRESULT: -2147020579

    EABW0811 05/03/2013 08:15:55> -102: Failed to execute the search. HRESULT: -2147020579

    EABW0811 05/06/2013 12:42:39> -102: Failed to execute the search. HRESULT: -2147020579

    EABW083 05/02/2013 13:18:23> -102: Failed to execute the search. HRESULT: -2147020579

    EABW083 05/02/2013 13:31:37> -102: Failed to execute the search. HRESULT: -2147020579

    #9524
    doug
    Moderator

    Has anything at all on your wsus server changed? Does the windowsupdate.log file have anything that’s might indicate a cause? If you manually install updates on one of the problem systems and reboot, do you still see the same behavior in BP? I’m not quite sure what to make of this problem. You should be able to figure out if the issue is on the clients or on the Wsus by temporarily pointing a client to a different wsus or to Microsft update, and then see what happens with BP. Also, if you do “install downloaded updates” even if there are no updates downloaded, does this throw an error? I predict it won’t because the client will not do a search on the wsus in that case and will only scan the actual client to see if it has any updates downloaded. This points to a problem or config issue of some kind on the wsus.

    #9529
    qwejibo
    Participant

    Sorry for not getting back to you sooner.

    Something became corrupt in the IIS configuration on our WSUS server. We couldn’t get it fixed so we rebuilt the machine. Things are working fine now. One thing to note, after doing a vanilla WSUS SP2 install we had to install KB2734608 to get it working.

    #9530
    doug
    Moderator

    Thanks for sharing! Glad you got it working.

    -Doug

    #11948
    doug
    Moderator

    For all other -102 HRESULT values, please see batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx

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