- This topic has 1 reply, 2 voices, and was last updated 5 years, 10 months ago by .
-
Posts
-
The 5 in ‘1620: 5’ would generally mean access denied, which is a permission problem, but this is not how BatchPatch would typically report an actual permissions problem. That said it’s hard to know for sure what is going on in this case. I see you have the target going OFFLINE then ONLINE at one point in the middle of an operation. This could mean that the reason for the 1620:5 failure was actually due to a network issue or the target computer going offline or some kind of other weird issue like if you have anti-virus software running on the target that is killing the connection or the batchpatchremoteagent.exe or the remote psexesvc.exe service. If it occurs repeatedly as opposed to just being a transient issue I’d suggest using the troubleshooting instructions at this page to see if you can determine exactly where things are going wrong.
batchpatch-troubleshooting-guide
Also if you have antivirus software running on the target then it would be worth trying a different remote service name as described here, just to see if that might make a difference:
what-to-do-when-psexec-is-blocked-by-your-anti-virus-software”>batchpatch-troubleshooting-guide
- You must be logged in to reply to this topic.