on 01-20-2023 7:14 AM
Hi All,
As part of upgrading our BOBJ production environment from version 4.2 SP8 patch 9 to version 4.3 SP2 patch 7, we encountered one problem in upgrade of production environment for which we need your input on. Although the upgrade installer completed 100%, it ended with errors. The setupengine log indicated that many DFOs were unable to deploy to CMS databases because of the license key issues outlined below.
" [InstallEntDfoWrapper.UploadDFO] UploadDFO Failed: Your license key is invalid or has expired. If you received a temporary license key by purchasing another SAP BusinessObjects product, you must register SAP BusinessObjects BI platform to receive your permanent license key. (FWB 00016) "
The license key, however, is permanent and works fine in the existing 4.2 system. And since DFO deployment failed, not all BOBJ 4.3 features were getting reflected in the application. Even manual deployment of DFO and running repair didn't help much.
In addition, when we tried to add the 4.3 license key, the existing key was not getting deleted. It was throwing the same invalid license key error in CMC as it did during installation. SAP also tried batch scripts from the OS to add an emergency key, but the batch scripts too failed. Below is the screenshot of the error while adding or deleting license after 4.3 upgrade
Also attaching error log which got generated during the upgrade. the upgrade ended with a license key error while deploying DFO. prd-error-log.txt . This didnt happened in non production enviorment
Greetings sivadurgarao,
This is because BOBJ 4.3 license keys are not backward compatible. BI 4.3 therefore requires new license keys. If you try using older license keys, you will receive errors.
References
2944889 - Are new license keys required for SAP BusinessObjects Business Intelligence Platform 4.3?
Best Regards,
Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseph,
During non-production, we used to delete the 4.2 key after the upgrade and apply the 4.3 key, allowing services such as APS and AJS to start. During production, it won't even let us delete the 4.2 key. Based on our analysis, this is a post-step to add 4.3. Let us know if it's otherwise
User | Count |
---|---|
83 | |
9 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.