Enterprise Console: troubleshooting errors 0000002e and 0000003b

This article provides troubleshooting steps to follow when error 0000002e or error 0000003b is displayed in the Enterprise Console

1. From the computer on which Enterprise Console is installed, browse to the client computer that cannot be deployed to:
   \\computername\c$\windows\tasks ('winnt' if applicable)
   If you have to authenticate, put in the username and password that was entered in the 'Protect Computers' wizard.
2. Right click and choose New|Scheduled task.
3. Open up the properties of the new task and set:
   • 'Run': choose c:\windows\notepad.exe
   • 'Run as' and 'set password'. Ensure this is the username and password specified in the 'protect computers' wizard.
   • OK your settings
4. Run the new task you created.
5. Verify that Notepad has been launched on the system.
   • If Notepad did run, go to step 7.
   • If Notepad did not run, go to step 6.
6. Notepad did not run: the issue you are seeing is probably caused by another vendor's software, i.e. not Sophos software.
   • there is a permissions issue or other restriction on running remote tasks
   • you can either correct this issue and then use the Console to deploy or else use another deployment method, e.g. manual installs.
7. Notepad did run. Return to step 1 above, and repeat the procedure, setting up the scheduled task to run the relevant Sophos setup.exe file, and using the same username and password as you used in step 1 above.

If you cannot run the setup.exe file, this suggests that there is a specific limitation on running certain files, or from certain locations. You will need to determine what restrictions are in place, for example, checking firewall settings or by trying to run other local .exe files or by copying the Sophos install folder to a local path, etc.

See also Enterprise Console: cannot deploy to a managed computer.