Skip to Content

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

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. Siddhartha Nirgudkar

    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

    (0) 
  2. Sivakanth Panchagnula

    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.

    (0) 
    1. Andreas Sbrzesny Post author

      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.

      (0) 
  3. Jerry Liu

    Thank you very much for this helpful info. I had just experienced same situation last week and finally found your solution.

    Jerry

    (0) 

Leave a Reply