Error Code 1072

[jlantano]

We have been getting The specified service has been marked for deletion error code 1072. Anyone getting this error? Restarting the device resolves it but gets the same error after running another command.

[doug]

Can you please describe the exact steps to produce this result? What action are you executing? Please be as specific and detailed as possible.

When you said that restarting resolves it, are you restarting the target computer or the BatchPatch computer?

The more details you can provide, the more likely I’ll be able to assist.

[jlantano]

So, issue is when deploying applications to a remote device or every time psexec executes. After the command completes, PSEXESVC service on the remote device gets marked for deletion and the service is stuck. This is a problem if you have another application to deploy or need to run another command. Deployment: Exit Code: 1072 return on the second deployments. Yes, restarting the target computer resolves it temporarily.

[doug]

Is this happening on a single target computer or all target computers?

If it’s happening on all target computers then I think the most likely culprit would be some other application such as anti-virus or HIPS or other similar security suite is locking the file, thereby preventing Windows from removing it.

If it’s happening on a single target computer the cause could still be what I described above, especially if that computer is running different software from all of your other target computers. However, it could also be something else going on. Hard to say for sure.

You might be able to gain insight into what’s preventing the service from being removed by using Process Explorer ( https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer ) to see what might be locking the service executable.

A workaround that you could use is in BatchPatch ‘Tools > Settings Remote Execution.’ There’s a setting to “Append random string to remote service name” which would cause each action to create the remote service with a different name, which should effectively stop this error from occurring. However, it won’t stop the issue with the service not being able to be removed, so you’ll end up with potentially numerous undeleted services on the target computer(s) that presumably then will not be completely removed until after reboot.

[Author]

Posts