Topic
Please see the following for recommended troubleshooting steps in the case that you encounter an issue with the Install Application native script.
Environment
- NinjaOne Automation library
- Scripting
Index
- The script is running but takes hours to complete to a failure. The installer is running in the Task Manager.
- The install fails right after the script is deployed.
- The install succeeds, but there is no 'Software Added' entry in the Activity Feed.
The script is running but takes hours to complete to a failure. The installer is running in the Task Manager.
This is generally caused by a bad parameter or a missing parameter.
To try to stop the script, you can kill the installer process (which is usually named after the software you are attempting to install) via the Task Manager.
The install fails right after the script is deployed.
This can be caused by a few different things but is often caused by the software already existing. Or, if you are updating a piece of software, the program may be running or in use, causing the install to fail (as the program may need to be closed).
This may also indicate an issue with the installer itself. The Application Event Viewer may provide more specifics as to why it failed.
The install succeeds, but there is no 'Software Added' entry in the Activity Feed.
This typically occurs if the software being installed is just installing a service. In this case, the install may not leave a registry key in the Uninstall registry keys that the Ninja Agent is pulling its inventory from.
These keys are as follows:
HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindowsCurrentVersionUninstall
- and -
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall