Error 1150 or Exit Code 1150 trying to check for available updates (or install)

[doug]

We recently received the following email from a customer:

Hello,

I’m getting Error 1150 or Exit Code 1150 trying to check for available updates (or install updates, etc.) on a Windows 2008 R2 server. I haven’t seen this before. Could you help me sort it out?

——————————–

This message would generally appear as: Error 1611: 1150. Failure or Error 1620: 1150. Failure

The problem was resolved after the customer followed the instructions below to remove the orphaned psexec service:

Look at the target system in the services console (start > run > services.msc) and see if there is a “psexesvc” service listed. Note, the service name would be different if you have specified a value in BatchPatch under ‘Tools > Settings > Remote Execution > Use PsExec -r switch to specify remote service name‘. Under normal operating circumstances this service will only exist while psexec is executing, and then it is removed as soon as execution finishes. However, in your case it might be that the service has been orphaned, which could either be the cause of the problem or a symptom of another problem.

If the service exists on the machine even when not using or trying to use psexec, then go ahead and try to stop it if it’s running and then remove it. Use the following syntax:

sc.exe stop psexesvc
sc.exe delete psexesvc

After this, things should start working, but it’s also possible that the inability for psexec to clean up and remove the service was really just a symptom of some other problem. If things still don’t work, please verify that everything that psexec needs to operate/function is working.

If you have windows firewall enabled on that computer, you might try disabling it temporarily just to see if the firewall is the root cause. If disabling the firewall fixes the problem, then go ahead and re-enable it and then make sure the following allowances are set.

1. Make sure you can browse from the BP computer to \\targetcomputer\admin$

2. Make sure “file and printer sharing” is enabled

3. Make sure ports 135 and 445 are allowing traffic through (this would normally be handled by allowing file and printer sharing in the windows firewall)

There’s a bit more on firewall config here: Using BatchPatch with Windows Firewall

[Author]

Posts