Strange Error with running processes

[jaredguerra]

Hello I am currently having errors with one of my team member’s batchpatch. We utilize 4 instances of batchpatch and 3 of the 4 work normally. My issue is the fourth instance seems to just “initiate windows update…” or says on “initiate deployment” but never moves on from that. It is configured the exact same way as the other instances so I am really stumped on how to fix this. I am pointing to the correct psexec.exe location but still cant seem to do any update or deployment pushes. I can pull information from the machine like host name but not available updates. The software is also up to date as well. Any ideas?

[doug]

Can you give me the verbatim text that it gets stuck on?

The app never says these two things exactly:

“initiate windows update…”

“initiate deployment”

In order to troubleshoot this to determine exactly where things are getting stuck, I need to start with learning the exact text that you’re seeing hang indefinitely. There are too many places with *similar* text, so I can’t pinpoint your issue without knowing the exact text.

Thanks.

[jaredguerra]

Oof, I really should have included the actual messages. When running windows update it gets stuck on “Windows Update: Attempting to initiate Wndows Update” and when trying to send a deployment it stays on “Deployment: Executing \[target] -s -w “[target file transfer location]””[deployment path]””

[doug]

Thanks. It sounds like psexec is blocked on the computer. This can happen as a result of Windows settings that prevent running an executable file that was obtained from somewhere else until after permission has been explicitly granted. One way this manifests is with a popup of a dialog that says “File Insecurity Warning” and prompts you to either check or uncheck a box to make sure that it never prompts again. The issue with this is that if you are running BatchPatch as a user that is not the logged-on user, then this popup might not be visible. It’s also possible that this popup doesn’t appear at all. Another way that this can usually be resolved is to right-click on the psexec.exe and select ‘Properties.’ Then on the ‘General’ tab at the bottom there is a section titled ‘Security’ that says “This file came from another computer and might be blocked to help protect this computer. Then there is a checkbox next to that to “Unblock.” Select the checkbox and click ok.

Please confirm you got everything working.

-Doug

[jaredguerra]

Doug to the rescue! Thank you

[Author]

Posts