Blackberry Enterprise Server upgrade

Hi

I was wondering if anyone can share with me the experience and guide step by step to perform an upgrade from 5.0.2 MR 5 to 5.0.4

Thanks
LVL 1
lomareeAsked:
Who is Participating?
 
Rodney BarnhardtServer AdministratorCommented:
Well, the step-by-step guide depends on your environment.  Here is mine:
Production (all separate servers)
BlackBerry Administration Service running on Windows 2008 R2
BlackBerry Enterprise Server running on Windows 2008 R2
BlackBerry Collaboration Services running on Windows 2008 R2
SQL 2008 running on Windows 2008 R2

Disaster Recovery Site
All services on one server running on Windows 2008 R2

These systems are set up as a High Availability system

I performed the upgrade on the DR site first. I simply ran the downloaded SP4 file, applied it to the server, and rebooted. Then, I manually failed over the users from the production server to the DR server. This way I could verify everything was working fine.


After some testing to ensure everything was working properly, I followed the process listed here:

http://btsc.webapps.blackberry.com/btsc/viewdocument.do;jsessionid=29ABE40D940197A059F2EA6370A58D4A?noCount=true&externalId=KB24541&sliceId=2&cmd=displayKCPopup&docType=kc&isLoadPublishedVer=&docTypeID=DT_SUPPORTISSUE_1_1&ispopup=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

I upgraded the BAS server first and rebooted it. Then I upgraded the BES server and rebooted it. Last, I upgraded the Collaboration server and rebooted it. I then moved everyone back over. However, I had a problem on the production BES server with the services stopping. Upon checking the logs, the .exe file location mentioned in the services were not there. I re-ran the SP again, still having the issue. I worked with BB support, and we watched the files. Any time I clicked "finish" after the services stopped, the files would disappear and be moved one folder down. We finally had to uninstall BES entirely from that server, including registry entries, and reinstall it. After that, it worked fine. They were figuring there was something wrong in the registry somewhere causing the issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.