If you have ever managed a SAP BusinessObjects server, there will be a time where you need to determine which Patch or Service Pack is installed on your server. There a a few ways to find this information and I will outline them below:
On a Windows Operating Systems you can check the “Programs and Features” MMC under the control panel:
You should see a list of both the Name and Version number of SAP BusinessObjects that is installed. Below is a version number table you can reference.
You can check the CMS.EXE version number on Windows:
Browse to “Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\cms.exe” and right click the cms.exe file. Chose the details tab and look for the version number. Please note that you are only checking one executable. It is possible that other service executables have a lower or higher version number. Therefore it is best to rely on “Programs and Features” MMC information.
You can check the boe_cmsd file on Linux
Browse to the “../sap_bobj/enterprise_xi40/linux_x64″ folder on you Linux server and run the following command:
strings boe_cmsd | grep BOBJVERSION
You will see results simular to this:
@(#)BOBJVERSION: 14.0.2.565 boe_cmsd release 11/12/21 linux_x64
View the Metrics property on the Central Management Server in the CMC
The metrics property on each server in the CMC contains the version number. You can obtain the version number via the web based central management console (CMC). As stated above you should also check the ”Programs and Features” MMC information. If you are on Linux or UNIX, this might be easier then using the command line.
Check the install inventry.txt file.
[BOBJ Install Directory]\InstallData\inventory.txt
SAP BusinessObjects 4.0 Version Number Matrix: (SAP NOTE 1602088)
SCN Posting with another matrix and version information (Link)
| BI 4.0 RTM | 14.0.0.760 |
| Patch 04 | 14.0.0.904 |
| Patch 05 | 14.0.0.918 |
| Patch 06 | 14.0.0.940 |
| Patch 07 | 14.0.0.954 |
| Patch 08 | 14.0.0.970 |
| Patch 09 | 14.0.0.986 |
| Patch 10 | 14.0.0.996 |
| Support Pack 1 | 14.0.1.287 |
| Patch 1.1 | 14.0.1.313 |
| Patch 1.2 | 14.0.1.330 |
| Patch 1.3 | 14.0.1.342 |
| Patch 1.4 | 14.0.1.360 |
| Patch 1.5 | 14.0.1.375 |
| Patch 1.6 | 14.0.1.397 |
| Support Pack 2 | 14.0.2.364 |
| Patch 2.1 | 14.0.2.388 |
| Patch 2.2 | 14.0.2.397 |
| Patch 2.3 | 14.0.2.416 |
| Patch 2.4 | 14.0.2.439 |
| Patch 2.5 | 14.0.2.455 |
| Patch 2.6 | 14.0.2.481 |
| Patch 2.7 | 14.0.2.508 |
| Patch 2.8 | 14.0.2.532 |
| Patch 2.9 | 14.0.2.556 |
| Patch 2.10 | 14.0.2.565 |
| Patch 2.11 | 14.0.2.594 |
| Patch 2.12 | 14.0.2.619 |
| Patch 2.13 | 14.0.2.641 |
| Patch 2.14 | 14.0.2.657 |
| Patch 2.15 | 14.0.2.682 |
| Patch 2.16 | 14.0.2.703 |
| Patch 2.17 | 14.0.2.721 |
| Patch 2.18 | 14.0.2.740 |
| Patch 2.19 | 14.0.2.762 |
| Patch 2.20 | 14.0.2.798 |
| Patch 2.21 | 14.0.2.846 |
| Feature Pack 3 | 14.0.3.613 |
| Patch FP3.01 | 14.0.3.630 |
| Patch FP3.02 | 14.0.3.657 |
| Patch FP3.03 | 14.0.3.678 |
| Patch FP3.04 | 14.0.3.691 |
| Patch FP3.05 | 14.0.3.711 |
| Patch FP3.06 | 14.0.3.735 |
| Patch FP3.07 | 14.0.3.757 |
| Patch FP3.08 | 14.0.3.777 |
| Patch FP3.09 | 14.0.3.796 |
| Patch FP3.10 | 14.0.3.818 |
| Support Pack 4 | 14.0.4.738 |
| Patch 4.1 | 14.0.4.770 |
| Patch 4.2 | 14.0.4.797 |
| Patch 4.3 | 14.0.4.819 |
| Patch 4.4 | 14.0.4.831 |
| Patch 4.5 | 14.0.4.855 |
| Patch 4.6 | 14.0.4.880 |
| Patch 4.7 | 14.0.4.896 |
| Patch 4.8 | 14.0.4.915 |
| Patch 4.9 | 14.0.4.936 |
| Patch 4.10 | 14.0.4.957 |
| Support Pack 5 | 14.0.5.882 |
| Patch 5.1 | 14.0.5.915 |
| Patch 5.2 | 14.0.5.927 |
| Patch 5.3 | 14.0.5.957 |
Jonathan Haun Consulting Manager Decision First Technologies
March 22nd, 2012 at 7:09 pm
Hi Jonathan !
Nice list… and very useful !
)
Just add:
——————————-
Patch 2.13 : 14.0.2.641
——————————-
to make it up to date. ;o)
But what the **** is this logic with FP releases numbers ?!?
Regards,
Steve.
March 22nd, 2012 at 7:22 pm
Steve. Thanks for the update on Patch 13. I am not sure what they were thinking when they decided to call “Service Packs – > Support Packs”, “Fix Packs – > Patches” and Major Versions Feature Packs. Between Business Objects and now SAP changing the naming conventions every few years, its difficult to keep track of updates.
April 18th, 2012 at 3:03 pm
In Linux, you could alternatively navigate to the install directory and run modifyorRemoveProducts.sh, this would list all the installed products with the version.
May 11th, 2012 at 9:57 am
HI !
(
On W2008 R2 server, I’ve just installed FP15 over a fresh BI4 SP2 installation and I get in CMS metrics:
14.0.2.641 !?!
…like FP13 .
Anybody noticed the same strange thing ?
Regards,
Steve.
May 11th, 2012 at 10:06 am
I have yet to install FP15 but I would recommend that you check the version on the CMS.EXE file (Windows) and compare. With that said, it is possible that FP15 made no changes to the CMS.EXE file and therefore the version reflects a previous patch.
June 21st, 2012 at 11:42 am
muchas gracias
August 13th, 2012 at 2:09 pm
Jonathan,
Thank you for your time to put this comprehensive list together. It has really come in handy for an audit we just did of installed software through out our company.
November 14th, 2012 at 8:32 am
Last week I installed BI 4.0 SP04 and FP 4. I just found out that SAP makes a mess of the version numbers. For instance the ccm.exe is still 14.0.4.738
The cms.exe is 14.0.4.819 (FP3, wich I never even download, let alone installed) and in the Control Panel (Installed Programs) the version is 14.0.4.831. (I double checked the installation files and this is really version 14.0.4.831)
Really sloppy
November 14th, 2012 at 10:14 am
Christian,
Feature Pack 3 versions have 14.0.3 not 14.0.4. Your CMS is running as a version equivalent to SP4 Patch 3. With patches, it is normal for there to be a mixed bag of versions. The update installer would require overriding every core file to avoid this. That is why I mentioned it is best to go by what’s listed in the Add / Remove Programs. With that said, this can also indicate that the patch install went very wrong. In the past BusinessObjects would list the binaries (with versions) that were updated with each ADAP in the release notes. They no longer do this so it’s impossible for an outsider to research and understand if they actually have an issue. Concerning patches going wrong, if a service is running while the patch installer attempts to override an existing binary, the file might not get updated. As a result the mix bag of binaries might actually create a compatibility issue which prevents services from starting. If all of your services are running and there are no issues, you are likely ok. Otherwise, contact support.
Thanks,
November 16th, 2012 at 5:03 am
BOE 4.0 SP04 Patch 6 is out as well
Build number – 14.0.4.880
Incase you want to keep your page updated.
January 24th, 2013 at 5:35 am
Hi, Could you kindly tell me the difference between Service pack, support pack, fixed pack. What exactly does each term represent.
Thaank you
January 24th, 2013 at 6:29 am
I would review Christopher Vozella’s Blog on SCN for more details: http://scn.sap.com/people/christopher.vozella/blog/2012/07/09/bi4-maintenance-demystified
February 12th, 2013 at 2:13 am
Hi Jon, In our environment I find in CMC setting the build is 14.0.3.738 but in services it is 14.0.4.738 Can you please tell me the reason what went wrong here.
February 13th, 2013 at 6:45 pm
I too have seen this. I am assuming that the patch did not update the value on the settings page but updated the the actual binaries associated with the services. For patches, it’s not unusual to see a mixed bag of revisions when looking at all the options mentioned above. The best way to insure you have the patch installed is to use the Windows (add / remove) Programs or Linux equivalent.
February 24th, 2013 at 7:47 pm
Thanks for posting this. It helped me track down an incompatibility issue between Dashboards 4.0 and the BO Edge Trial Edition that I’m running. The trial is SP2 and I needed SP3 which introduced RESTful Web Services.
March 24th, 2013 at 11:13 pm
[...] http://bobj.sapbiblog.com/2012/02/15/how-to-determine-your-patch-and-service-pack-in-boe-4-0/ [...]
April 5th, 2013 at 2:36 pm
Hi,
i have upgrade the BusinessObjects on Linux environment from BO4.0SP5 Patch 4 to BO4.0SP5 Patch 6. Installation say’s successfully installed BI Platform 4.0 SP5 Patch 6.
When i see in CMC still it says build “974″ but i expected it should be “1019″. Even i thought is installation didn’t happen successfully. Tried again to install, then it says Uninstall Confirmation.
Can you please tell me the reason what went wrong here.
April 5th, 2013 at 3:23 pm
What is listed in the [BOBJ Install Directory]/InstallData/inventory.txt file. That will be the best indication. Patches do not always change all of the version numbers.
April 5th, 2013 at 4:57 pm
Yes Jonathan.
In Inventory.txt file i have build # 1019. alongwith other build numbers.
Thanks for the response.