Skip to Content
Author's profile photo Akhilesh Kiran

Resolve : could not reach the CMS.CMC was stopped due to critical error (FWM 20031) or Failed to retrieve the cluster name from the database/Error: FWB (00090)

Resolve: could not reach the CMS.CMC was stopped due to critical error (FWM 20031) or Failed to retrieve the cluster name from the database/Error: FWB (00090)

There can be several reasons to cause this issue. Some of the below methods to resolve this issue.

Check the log files in the <installation directory path> SAPBusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging.
Check for SvcMgr log for any errors.

  • Check if the CMS DB password has been expired.

            Open Administrative Tools-> Local Security Policy-> Account Policy->Password Policy status.

  • Open Central Configuration Manager-> Select Server Intelligence Agent(SIA)-> Stop the SIA

Go to properties-> Select Configuration Tab. If you see the below error.

Copy those file to <Installation directory path>\SAPBusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

Open Central Configuration Manager-> Select Server Intelligence Agent (SIA)-> Properties->
Configuration Tab-> Click Specify


Select the Update data source settings


Select your ODBC Driver


Select Machine Data Source. Select your ODBC Connection.

Provide the credentials. .

Select OK then Start the SIA.


Then you can successfully login to the CMS. I hope this document will help you out.

Regards,

Akhileshkiran.




Assigned tags

      6 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Anil Lingam
      Anil Lingam

      Thanks much Akhilesh......this helped me fix our issue.

      Author's profile photo Safa Akar
      Safa Akar

      Also you can check log backup full or not.

      Author's profile photo Former Member
      Former Member

      Thanks a ton..You saved my life..Very well documented and well explained..Thanks 🙂

       

      Author's profile photo Zach Haupin
      Zach Haupin

      Thanks for sharing. In our case we had hundreds of GB of .hprof log files that were consuming 100% of the disk space on the installation drive (windows).

      Author's profile photo Nelson Chamba
      Nelson Chamba

      Hi dear all,

      I have the same error, did all the steps but unfortunately it didn't fix my bug, can someone give me some more inputs?

      regards,

      nelson chamba\

      Author's profile photo Navneet Kaur
      Navneet Kaur

      Awesome...This really helped to resolve it.Tons of thanks.