
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
(SHR) Support Tip: All Content Pack installs fail on Windows
Unable to install any new content packs on Windows. The console and packagemanager.log shows errors of the form:
ERROR, com.hp.bto.bsmr.rpack.Autopilot.processRunCommand , run_command Error processing Run Command directive: {PMDB_HOME}/bin/trend_proc -f {PMDB_HOME}/packages/abc/abc.ap/abc.pro
ERROR, com.hp.bto.bsmr.rpack.Autopilot.directiveFatalError , run_command :The Run Command exited with a return code of: 1
So the trend_proc command running the .pro file is returning with a return code of 1.
Take a look at the .pro file to see what commands it is trying to run. For example these may be commands such as:
- %PMDB_HOME%/bin/datapipe_manager
- %PMDB_HOME%/bin/loader
- %PMDB_HOME%/bin/collection_config
- %PMDB_HOME%/bin/abcimportdef
- %PMDB_HOME%/bin/stage
We have seen occasions when the %PMDB_HOME%/bin directory conatins files with these names (but without the .exe extension) with a size of 0 bytes. As a result the trend_proc command is trying to run for example the 0 byte file "loader" rather than the correct file "loader.exe".
The solution is to delete the file that has no .exe extension and is 0 bytes in size.
This can occur with any of the files in the %PMDB_HOME%/bin directory that are of the same size as the "launcher.exe" file. The reason for this issue is unknown. (It was also seen in the Performance Insight product that used a similar set of commands.)