SAP Knowledge Base Article - Preview

3413618 - CMS fails with error on file infostoresubsystem.dll or SIA missing after update / fresh install to 4.3 SP04

Symptom

After update to 4.3 SP04:

  • In an update of BI from a previous release, the Central Management Server (CMS) won't start.

    If a log in to CMC (Central Management Console) / BILP (BI Launch Pad) is attempted, the following error will be seen: 
    Account information not recognized: Could not reach CMS '<HOST>:6400'. The CMS on machine '<HOST>' was stopped due to a critical error. (FWM 20031) 

    The following message will be seen in the error_cms6400.log file in the BI logging directory:
    33007    The library named infostoresubsystem could not be loaded. The system error message is Loading shared object failed. First tried to load library infostoresubsystem and failed because of error: [The specified module could not be found.  ]. Second tried to load library C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\infostoresubsystem.dll and failed because of error: [The specified module could not be found.  ].

    In the setupengine / errorsandwarnings logs:
    *#*_*|ERROR: Could not establish a connection with any CMS.|ERROR: Could not establish a connection with any CMS.*_*#*
    ERROR: An unexpected internal error occurred. The CMS has terminated unexpectedly with exit code 3. (FWM 23025)
    ERROR: Could not reach CMS '<HOST>:6400'. Specify the correct host and port and check for network issues, please refer to SAP Knowledge Base Article 2151044 on the SAP Support Portal. (FWM 20030)
     - CMS is unstable and will shut down immediately. Reason: The library named infostoresubsystem could not be loaded. The system error message is Loading shared object failed. First tried to load library infostoresubsystem and failed because of error: [The specified module could not be found. (FWB 00087)
     - The root server reported an error Initialization Failure. 

  • In a fresh installation of BI, the SIA will be missing / not present

    If a log in to CMC (Central Management Console) / BILP (BI Launch Pad) is attempted, the following error will be seen: 
    Account information not recognized: Could not reach CMS '<HOST>:6400'. The CMS on machine '<HOST>' was stopped due to a critical error. (FWM 20031) 

    In the ErrorsAndWarnings.log and setupengine.log, some of the following errors may be found:
    *#*_*FWM 20031|ERROR: Could not reach CMS 'PSG-84188:6400'. The CMS on machine '<HOST>' was stopped due to a critical error. (FWM 20031)
    ERROR: Could not reach CMS 'PSG-84188:6400'. The CMS on machine '<HOST>' was stopped due to a critical error. (FWM 20031)
    ERROR: An unexpected internal error occurred. AddNode - No suitable enterprise nodes could be found (FWM 23066)



Read more...

Environment

  • SAP BusinessObjects Business Intelligence (BI) Platform 4.3 SP04 Base
  • Windows OS (all supported)

Product

SAP BusinessObjects Business Intelligence platform 4.3

Keywords

BI 4.3 SP04 install fail Windows OS CMS error infostoresubsystem.dll file or SIA missing after update VC++ redistributable 2015 2022 , KBA , BI-BIP-INS , Installation, Updates, Upgrade, Patching , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.