1601 errors when using batchpatch for Windows Updates.

BatchPatch Forums Home › Forums › BatchPatch Support Forum › 1601 errors when using batchpatch for Windows Updates.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • January 27, 2017 at 8:40 am #9319
    Jork Eggels
    Participant

    Hi,

    We use BatchPatch for install Windows Updates but some servers respond with the following errors:

    Error 1601: Failed to retrieve WMI info. The interface is unknown. (Exeption from HRESULT:0x800706B5)

    Error 1601: Failed to retrieve WMI info. A security package specific error occurred. (Exeption from HRESULT:0x80070721)

    Can you tell me how to fix this errors?

    Thank You!

    January 27, 2017 at 5:29 pm #11493
    doug
    Moderator

    Error 1601: Failed to retrieve WMI info. The interface is unknown. (Exeption from HRESULT:0x800706B5):

    This indicates that WMI is not working properly on the target computer. This hotfix may resolve the issue. If that hotfix does not fix the issue, then you will need to troubleshoot WMI in more depth on the target computer. This link explains how to do that.

    Error 1601: Failed to retrieve WMI info. A security package specific error occurred. (Exeption from HRESULT:0x80070721):

    I would suggest the following links to help troubleshoot:

    https://blogs.technet.microsoft.com/brad_rutkowski/2011/03/07/solution-for-a-security-package-specific-error-occurred/

    https://blogs.msdn.microsoft.com/asiatech/2012/10/18/troubleshoot-client-calls-to-dcom-server-failed-with-a-security-package-specific-error-occurred-exception-from-hresult-0x80070721/

    https://superuser.com/questions/1005782/wmi-query-fails-with-a-security-package-specific-error-occurred-exception-800

    https://msdn.microsoft.com/en-us/library/aa394603%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

    January 30, 2017 at 3:01 pm #11494
    Jork Eggels
    Participant

    Thanks for your response, i tried to connect to the servers using the ip addresses and then it works. After that i tried it with FQDN again, that worked to! after 30 minutes i did a last check and then it fails again, do you have any idea where this is going wrong? I cant find any logs in the event viewer. The servers who have this problem are windows server 2008 enterprise installed on it.

    I did this for both errors and the result is the same.

    Thanks for your help.

    January 30, 2017 at 4:50 pm #11495
    doug
    Moderator

    Unfortunately I do not have any better suggestions than the ones I provided in the previous posting.

    -Doug

    January 31, 2017 at 12:40 pm #11498
    Jork Eggels
    Participant

    Thanks for your response. We have multiple servers with the same name in different domain so i think it has something to do with NETBIOS, i have added the servers by using IP Addresses and made a description with the name in it, That works fine! Wonderful Tool!

    I saw that you can also use BatchPatch for updating Flash and Adobe, i played around with the deployment following the following tutorial:

    https://batchpatch.com/using-batchpatch-to-deploy-adobe-flash-to-numerous-computers

    instead of getting the Deployment Exit code:0 i get the Deployment Exit Code 255, are you familiar with this exit code? I used the .exe file instead of the .msi file.

    EDIT: when i choose Deployment: normal in the settings i get an Deployment Exit code: 0 (succes, however when i look in the control panel installed applications i dont see flash installed. I monitored the proces, when i execute the deployment i can see on the target server that the installation file is in the batchpatchdeploymenttemp folder. After getting the Deployment exit code 0 succes, it disapeared from the batchpatchdeploymenttemp folder. (normal behaviour i think?) But flash isnt installed..

    EDIT: i can see a difference with my situation and the screenshot, the

    Thanks for helping me! The windows installer options are grade out, sorry for the edits 😉

    January 31, 2017 at 4:34 pm #11500
    doug
    Moderator

    The Windows installer options are grayed out because they are only valid for .msi/.msu. They will not be available for .exe. The tutorial was written for the .msi. It was not written for the .exe that you are using. I don’t know which .exe you are using, so it’s difficult for me to suggest how to use that particular .exe. I would suggest that you use the .msi as described in the tutorial.

    If you want to use that .exe then you should first figure out how to install that .exe from the cmd prompt. Once you have successfully installed it from the cmd prompt without using BatchPatch, then it will be easy to use the same cmd parameters to install from BatchPatch.

    This link may help: understanding-and-discovering-the-silent-parameters-required-to-remotely-deploy-software-with-batchpatch

    -Doug

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