Share This:

Users who are upgrading to BPPM 9.6, please be advised of an important perquisite for upgrading to BPPM 9.6. BMC Software is alerting users to perform the following steps before upgrading to BMC ProactiveNet 9.5.00 on Microsoft Windows computers. This requirement is applicable to 9.6 as well.


Before upgrading:


1. Take a backup of the computer in which the BMC ProactiveNet Server is installed.

2. Update the following files (if available) located in the <installationDirectory>\pw\custom\conf directory:•For the JServer process, comment the following line in the pnjserver.conf file:



•For the Rate process, comment the following line in the pnrate.conf file:



•For the Agent Controller process, comment the following line in the pnagentcntl.conf file:




•For the Agent process, comment the following line in the pnagent.conf file:




This requirement is documented under:Alerting users to follow the key upgrade prerequisite on Windows - BMC ProactiveNet 9.6 - BMC Documentation


There is a problem where the files in pw\custom\conf contain “jre64” in the path and the path is now referenced as “jre”. This is evidenced by jre64 references in the proservices.log file see below:




If you see this reference in your BPPM 9.6 ProServices.log file (\\BMC Software\ProactiveNet\pw\pronto\logs) your upgrade did not go well. This can have a negative impact on your environment. The only way we can fix this problem completely is to restore from backup and do the upgrade again after modifying the custom configuration files before the upgrade.


Any attempts to modify the files after the fact will result in an unsupported environment. We cannot guarantee there will not be any other negative effects of the missed change before the upgrade. Our experience with other customers who have attempted to modify the files after the upgrade resulted in several different product issues which all traced back to a botched upgrade.


Therefore, we require you to restore from backup and start the upgrade process again.  We have seen this issue with the upgrade between 9.0 and 9.6 but it may affect other versions as well. So please be sure to include the changes above in your perquisites for upgrading to BPPM 9.6.



In order to be sure you are on the right track for your upgrade, we encourage you to take advantage of our free AMIGO program. There is a BPPM 9.6 Checklist for AMIGO which contains the details of the requirements for the upgrade. This checklist does contain a check for the jre64 indicator in the conf files.



Check each of the conf files in the pw\custom\conf directory for the parameter:   ProcessName=$PROACTIVEHOME\jre64\bin\.......

Just before starting the upgrade, comment out the ProcessName line:


Do not restart BPPM after making this change before the upgrade is run.



The BPPM Assisting MIGration Operations (AMIGO) program is designed specifically to help you upgrade quickly, easily and safely.



The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

To get started review the checklist items found here: KA408618

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.





Newly Published Knowledge Articles - New Content has been added over the last month!

This is our opportunity to share with you some of the most recently created knowledge articles in case they may help you with something you would like to know more about.

KA418568 How does BPPM 9.5 IBRSD look up the BPPM server, and cellname to send INCIDENT_INFO events to? 

KA407196 Is there a way to migrate thresholds from one BPPM server to another?

KA380112 How the TAG match works between CMA on the BPPM side and the PATROL Agent side

KA386298 The Diagnostics menu option is grayed out when right clicking on an event within the ProactiveNet Operations Console

KA400040 Details of shadow logging feature

KA405755 After manually closing an ALARM event with IX or mquery or msetmsg, the event is closed on BPPM but another new event is seen when threshold for that attribute is still in breached state.

KA359014 Need to automate the import of an enrichment file every 15 minutes   


Popular Knowledge Articles
This list represents our most widely used knowledge articles, take a look to see if they may help you too!

KA318711 How to change the hostname/IP Address of BPPM ProactiveNet Server on Windows Platform

KA330178 What ports are required on the firewall for the BMC PATROL Adapter within ProactiveNet Server 8.5 or 8.6?

KA361627 The installation of the ProactiveNet CMDB Extensions from BPPM 8.6.02 and failed on Atrium (AR) version 7.6.04 SP2

KA357339 How to configure/scale ProactiveNet (MaxHeap, RAM, etc.) on server components like jserver, rate, Agent Controller and remote ProactiveNet Agent.

KA359011 How to configure/troubleshoot LDAP authentication in BPPM.


Looking for a previous blog posting? Find it here:  BMC ProactiveNet Pulse Blogs



Feedback Request:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!