ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Troubleshooting exit codes and return codes in Notification Server and Deployment Server environments


Article ID: 179951


Updated On:


Management Platform (Formerly known as Notification Server) Deployment Solution




What is the best way to troubleshoot exit codes and return codes that are reported in Notification Server and Deployment Server environments?

When a batch file, a script, a program installation process runs, or an application halts abnormally, they often times generate an exit or a return code that defines the exit status. In most cases, when Notification Server and Deployment Server display a return code, it was generated by a piece of software and is simply being reported by the Notification Server or the Deployment Server.

The best ways to troubleshoot exit or return codes are

  1. Document the Exit or Return Codes and any accompanying message description (screen shots often simplify this).
  2. Identify the active process or software that was being run on the agent computer or NS/DS server at the time that the code first appears.
  3. Check the OS Event Viewer logs, the agent logs, and/or the server logs to correlate the known information by timestamps and message descriptions.
  4. If a third-party application is thought to be the problem, check with the application vendor for the meaning of their exit or return codes (exit or return codes for many software vendors can be found with a Google search on the Internet).