Installation BO 4.1 SP5
Hello,
if you try to install BO 4.1 SP5 as update on existing installation of BO 4.1 SP4 on Windows 2012 Server R2 you get an error after the restart of the system.
The BO System can not connect to the CMS system.
In CCM, in the properties of Server Intelligence Agent (SIA), on configuration tab, getting the error: Failed to retrieve the cluster name from the database. Reason: Parser failed to initialize. If you try to configer the cms new, the error “FWB 00090” occurs.
To fix the problem, check if the files sqlrule.llr and sqlrule.dfa are in <BI_install_folder>\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64.
If not, copy the files newest version from a sub-directory of <BI_Install_folder>\Install Data\Install Cache to <BI_install_folder>\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64
Restart the SIA and the problem is solved.
Regards
Andreas
This is usually observed during patch upgrades / installations.
1711203 - Error: "Failed to retrieve the cluster name from the database. Reason: Parser failed to initialize" on Configuration tab in SIA in BI 4.0
One way to help reduce the occurrence of this issue, ensure the pre-requisites are set:
1952120 - SAP BusinessObjects (XI 3.1 and BI 4.0) Installation pre-requisites & best practices
We were on Sp4 Patch1 Clustered Environment and I started installing Sp5 on my with my CMS Server first and received :"either the remote cms cannot be reached or the logon credentials are incorrect" error after the System is restarted. Could you guys suggest me any Solution here? I have uninstalled Sp5 as I could not solve this error.
Hi, have you check if the files sqlrule.llr and sqlrule.dfa are in <BI_install_folder>\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64.
It worked Guruji 🙂 ! Thanks
Hi,
these errors are already documented in the following SAP Note:
http://service.sap.com/sap/support/notes/1711203
I only saw this issue when the Patching Best Practices where not applied. When you apply them, you usually dont face this kind of issues. You can find the Best Practices here:
http://service.sap.com/sap/support/notes/1757132
Regards
-Seb.
Thank you very much for this helpful info. I had just experienced same situation last week and finally found your solution.
Jerry
Thanks very much for the info.
Andreas, thank you! your answer just solved the issue. .
This saved me a TON of grief. Thank you Andreas!
Thank you so much for this. Saved LOTS of time for us trouble shooting!