Error 1611:3 after working through install steps

BatchPatch Forums Home Forums BatchPatch Support Forum Error 1611:3 after working through install steps

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #13069
    jkwi
    Participant

    I decided to get Batch Patch installed while we wait for the purchase to be processed. I worked through the setup guides but I’m still running into error 1611:3 when checking for updates. Initially our AV was blocking PSEXEC, however I made an exception for that and I’m able to run PSEXEC remotely via command line so I know that is working. I have the correct ports open in the firewall (We had printer/file sharing and remote admin already enabled). I see the batch patch directory being created and populated with the batchpatch.exe when running. PSEXEC service is running on the remote PC when I execute the check for updates, however I still a 1611:3 error. Any other ideas on what I can check? Thanks!

    #13070
    doug
    Moderator

    You purchased a license without ever testing out the free evaluation version?

    Hmmm… it’s tough to figure out what this could be. We’ve only ever had one report of 1611:3 before. Have a look at this link for details, and then let me know what you discover: https://batchpatch.com/forums/x/topic/error-1611-3-failure/

    #13071
    jkwi
    Participant

    Hi Doug,

    I had it working when we did a demo a couple years back but my boss would not purchase at the time.

    Thanks for the article and I did figure out the issue. There was a stopped batch patch service that must have stuck there when I was tweaking AV. Once I ran the command to delete that service, I initiated the check for updates again on my workstation and it worked.

    Thanks for the help

    #13072
    doug
    Moderator

    Ok great. Glad it’s working now. Thanks for letting me know. This is very helpful for us to know that you were able to resolve it with the instructions in that link.

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