- This topic has 5 replies, 2 voices, and was last updated 10 years, 3 months ago by .
-
Posts
-
Hi, I’m waiting for approval to buy batchpatch. Meanwhile I’m hoping you can help resolve this.
When I try to do something with Windows updates on a target machine (happened on several others too) I get this a lot. Seems to go away if I reboot the machine, but it then happens again fairly quickly. Hoping not to have to reboot everything before I can patch them.
Windows Update Messages
Error 1610. HRESULT -2147024891: Access to the path ‘\wlfssC$Program FilesBatchPatchBatchPatchRemoteAgent.exe’ is denied. – 11:36:51
The progress column says “Searching” but I’m not sure if that’s true.
I also see this:
Get Information Output Log
Could not find file ‘\wlfssC$Program FilesBatchPatchBatchPatchRemoteProcessOutput1730738134.log’.
(That file does not exist on the system. I had tried to do a ‘list all services’.)
The server is running Windows Server 2012.
Cheers, appreciate your help.
These all sound related though strange/unexpected.
First, please make sure you are only running one action at a time per target computer. Running multiple actions at the same time against the same target can, in some cases, produce weird results when one action severs a connection and ends up killing a different action in the process.
Second, do you have any type of anti-virus or intrustion protection/detection software running on the target machine or on the BatchPatch computer?
It seems like something is interrupting either psexec and/or the BatchPatchRemoteAgent that runs on the target. I would start by examining any software that is running on the target that could possibly be doing something along those lines. Try disabling or uninstalling (or testing on a machine that doesn’t have the same app installed) to rule it out.
The ‘Access Denied’ message does indicate a permissions problem, but I could also believe that it’s related to the other errors. Certainly it’s the case that under normal circumstances the domain admin would have local admin permissions on the target, but you should still verify the permissions to be sure.
It sounds like you’re using “run-as” to run the entire BatchPatch.exe as a domain admin user, yes? Could you try running as your regular logged on user and then input the alternate credentials into a BatchPatch row in the grid for the target host? Does this make a difference (it shouldn’t, in theory, but let’s see). Another test would be to log on to your computer with the domain admin credentials and then run BatchPatch without using run-as and without entering alternate credentials. Let me know what happens.
When you execute BatchPatch, try watching the target computer’s working directory (C:Program FilesBatchPatch). You should see the BatchPatchRemoteAgent.exe appear and then you should see several temp/log files appear that are created by the executing BatchPatchRemoteAgent.exe. Let me know if you do or don’t see this happening.
Also, please watch the processes list in task manager on the target. You should see the BatchPatchRemoteAgent.exe as well as psexesvc.exe. Do you see these or not?
Lastly, please check the services on the target machine. Normal psexec behavior is to install a temporary service called psexesvc, which lives for however long the process runs, and then it is removed. Does this service get orphaned on the target instead of being removed? If it is orphaned somehow, that could be why you get different error the second time around. If that’s happening, try removing it with these two commands.
sc.exe stop psexesvc
sc.exe delete psexesvc
What is the percentage of your targets that you’re seeing this behavior on? Or is it just a single one?
-Doug
OK, thanks for the info. The logs you sent are not consistent with what you’re describing. What I mean to say is the log that errors with 1610 is erroring and then exiting BEFORE execution of the BatchPatchRemoteAgent.exe ever occurs. Yet, you’re telling me on the other hand that you’re seeing execution take place (this is confirmed by the appearance of “Searching…” and “Executing BatchPatchRemoteAgent.exe” in the console as well as the 3 .log files appearing in the target working directory. I’ve emailed you so that we can try to get things figured out.
-Doug
- You must be logged in to reply to this topic.