Skip navigation
Share This:

Have you installed BPPM 9.0 SP2 yet? We have had many successful installations of BPPM 9.0 SP2 and while we await our 9.5 release, this is our most current version so if you are running an 8.x environment, we encourage you to upgrade. The Service Pack has been installed at many customer locations without issue.


Read about Service Pack 2 here:


There are over 75 fixes included in this Service Pack. The fixes cover all areas of the product such as:

  • Fixing graphs in the Operations Console, framing and toolbar fixes in the Operations Console
  • Fixes to management data published to the cell, cell connections, and cell crashes have been addressed 
  • Various errors such as NullPointer errors have been corrected
  • Group access permissions have been modified for viewing Devices
  • Modification and maintenance of various application parameters
  • SCOM Adapter corrections


To see a listing of all the fixes, review the details under Corrected issues in Service Pack 2

Always remember, the first step to installing any Service Pack is to make sure you have a viable backup!

Here are some details for backing up the ProactiveNet Server on both Solaris and Windows:


The generic steps below should be sufficient to backup the configuration and data from the ProactiveNet Server running on Solaris.

  1. Shutdown the ProactiveNet Server.
    pw system stop
    Note: Verify all ProactiveNet Server processes are "!Not Running!" before creating the backup.
  2. Backup the ProactiveNet Server installation directory (/ProactiveNet/pw) using a TAR archive.
    cd /ProactiveNet
    tar cfp /backup/pronet_archive.tar pw
    Note: The Tar utility may complain about some files with very long names; these do not matter as they are only temporary files.
  3. Restore the ProactiveNet Server installation directory (/ProactiveNet/pw) over an existing installation of the same version which is not running (pw system stop).
    cd /ProactiveNet
    tar xvf /backup/pronet_archive.tar
    Note: Verify all ProactiveNet Server processes are "!Not Running!" before restoring the backup.


Additional details are documented in the Knowledge Base, "How to Migrate ProactiveNet Server to a different Solaris server?"


A backup of the "pw" directory is the most complete and direct way to archive the configuration and data from the ProactiveNet Server. The minimal list of files to archive the configuration and data is documented in the "Offline backup requirements" section, pages 18 - 21, of the "BMC ProactiveNet Performance Management: Disaster Recovery Best Practices"


Here are the instructions for Windows: Below are the steps to backup the ProactiveNet Server on Windows if the target ProactiveNet server (Windows) will have the SAME IP address and hostname as the original ProactiveNet server.

Step 1) The database archives are performed on a regular basis.  By default, the ProactiveNet server performs a full db archive once per week, with incremental archives once every day.


Step 2) Stop the ProactiveNet Server on the original server and backup the entire ProactiveNet Server installation directory.  The ProactiveNet Server installation directory can be determined by looking at the %PnServerPath% environment variable.  This is needed for restoring customized configuration files (custom monitors, Apache configuration, custom diagnostics, custom MIBs, etc.).  The running database file (located under the Sybase directory) can be left out of this particular backup since it will be restored separately from database archive (in general, a straight copy of a running database is not usable for archive purposes).


As a note, backing up the entire ProactiveNet Server installation directory should be performed at least on a semi-regular basis.  Also the archives should be kept on a separate physical disk from the ProactiveNet server installation to ensure maximum safety.


Note: There are no environment variables and Windows registry entries to backup for ProactiveNet Server on a Windows server.  The new ProactiveNet Server installation will take care of the environment variables and Windows registry entries and they are the same on all ProactiveNet Servers.


Below are the steps to restore the ProactiveNet Server on a target Windows server with the SAME IP address and hostname as the original ProactiveNet Server:


Step 1) Restore the Windows operating system and file systems.  Make sure there is a drive of the same name as the one on which ProactiveNet Server was originally installed.  If database archive was being sent to a different file system, make sure that drive name is also matched.


Step 2) Install the same ProactiveNet Server version as the original ProactiveNet Server.  Also install the same ProactiveNet patch as the original server ensuring to install to the directory of the same name as original.  Installing the ProactiveNet Server and patches ensures that all Windows environment variables and Windows registry entries are in place and all scheduled jobs are created properly.


Step 3) Stop the ProactiveNet Server on the target Windows server using the "pw system stop" command in the Pw Commands window or by stopping the services.


Step 4) Copy the backup of original ProactiveNet Server Installation directory on top of the new ProactiveNet Server installation on the target Windows server.


Step 5) If database archive is kept in a non-default location, restore it to that same location on the target Windows server making sure to use same drive and directory names (by default the database archive is kept under the %PnServerPath%\pw\dbarchive directory)


Step 6) Start the ProactiveNet Server on the target Windows server using the "pw system start" command in the Pw Commands window or by starting the services.


Step 7) Restore the database by running the "pw database restore" command in the Pw Commands window.

This completes the backup and restore procedure for the ProactiveNet Server with the same IP address and hostname as the original ProactiveNet Server.


Here are some of our reported issues and solutions while installing BPPM 9.0 Service Pack 2

ISSUE: Installation of BPPM 9.0 SP2 generates a rather lengthy list of warnings. Can these warnings be ignored or is further action required? Per BMC Engineering the majority of the warnings can be ignored, see KA402151 "BPPM 9.0 SP2 installation completes with warnings, is this problematic?'

SOLUTION: There are 3 types of minor warnings in the log file but based on the contextual messages in the log these warnings can be safely ignored. These warnings have been verified by BMC Engineering and they can be ignored.

B) There is no Detailed Diagnostics deployment descriptors to register.
C) promail.MailSenderCLI


ISSUE: After installing BPPM 9.0 SP2 onto 3 Windows 2008 servers, two of the Windows servers are running the Integration Service. The PATROL Agent will not start showing an error code 3001.

The upgrade somehow changed the PATROL Agent to look in another directory for its config.default file. The PATROL Agent should be looking for the config.default in Patrol3\lib but it is looking in my pconfmgr directory. What should we do?

SOLUTION: While we do not have a root cause at this point for why the environment variables were changed, the solution is to reset the environment variables to the correct location. We have seen this issue only once and have not reproduced it internally so if any customers see this issue, please report it to Support so that we can investigate further.


ISSUE: I have downloaded the SP2 binary "BPPM_9022_CoreComponents_ServicePack_Linux.tar.gz" and am attempting to apply the patch to an Agent Cell by running the BPPMAgent9.0_b231178031.bin installation. When the installation gets to a certain point, it detects that there is already an active Cell on the system, and creates a "features selection error: Cell is already present on the system". There is no way to proceed with the SP2 install, cancellation is the only option. What should I do?

SOLUTION: This problem has been identified, and defect QM001775988 is opened on this.  In the meantime, the workaround from development is to install SP2 on a separate/new machine (as a fresh install), then copy the files to this machine that you need to upgrade.  The steps from development are:

  1. Install GA patch build in another machine with remote cell or IS option.
    2.            Copy files into the files to this machine.
    a.            Recommend to copy all files from <Install path>server\bin and <Install path>server\etc\default
    b.            For migrating KBs need to refer upgrade guide Appendix A "Using migrate utility".
    3.            Verify functionality.

The doc with the info for Migrating the cell kb is here: Page 89.


ISSUE: After applying BPPM 9.0 SP2 the command 'penv -p "InitMgmtData=T" -e PROD init' failed. When I attempt to run this command it fails with the following: ‘penv -p "InitMgmtData=T" -e PROD init' failed

==> Request failure: Loading baroc data from file /appli/BPPMR/BppmServer/pw/server/etc/ps_lfpmsf1t/kb/data/.load failed. LoadException: loading files from /appli/BPPMR/BppmServer/pw/server/etc/ps_lfpmsf1t/kb/data/.load : astItem no instance of AstDef

SOLUTION: The issue is due to blanks at the end of the baroc files. Defect QM001806526 was created and fixed.  The files in the ps_xxxx data directory need to be modified to remove

Please edit each of the files in the data directory, do Ctrl-End to get to the end of the file then delete any extra lines that exist so the last line in each baroc file is just END. If you do make the changes and the problem still occurs, please edit again with a different editor to verify that no blank lines exist at the end of the file.  Some editors will ignore blank lines and others do not.


ISSUE: I am having issues in installing SP2 for BPPM 9.0.. It keeps throwing an error of: One or more files under pw directory in your installation are locked.

SOLUTION: Please download process viewer from windows sysnternals site form this link, and then execute it please. Then select the Find option and enter the name of the file that is locked, so we can see which is process is handling such file.  We found that the Patrol Agent was using files in the ProactiveNet server path. So we stopped the Agent, configured the startup as manual, and set all the BPPM services to manual startup and rebooted the server. Once the install of SP2 was rerun the process ran smoothly and the SP2 installation was successful. There can be other processes causing a lock, but look to PATROL first.



Popular Knowledge Articles:

KA361960 - Is there a way to remove stale auto discovered devices from BPPM ? 

KA352096 - Unable to delete PATROL Adapter from ProactiveNet Admin Console  

KA359501 - How does the BPPM PATROL adapter auto-sync work?   

KA350682 - How can I install BPPM 8.6 with Oracle as the backend database ? How can I specify it is an Oracle RAC database? 

KA346342 - On Windows 2008 BPPM server 'pw system status' shows mcell as !Not Running! even though the cell is running






Was this helpful?  Are there related topics I missed? Please add comments to share your experience.

Filter Blog

By date:
By tag: