BODS CMC port not working

[svkarthikeyantce]

Hi Experts,

I'm upgrading our BODS system to version 4.3.

BO (BuildVersion=14.3.2.4073.businessobjectsserver_one_aurora43_sp_rel) and DS BuildVersion=14.3.2.545.dataservices64_DS_4.3.2_Patch_REL

After upgrade, the CMC port 6400 is not working and not reachable. Also, I tried to create a new SIA process, but I couldn't get much information to create one on windows sever. All the available docs are for BODS on Linux or if it is windows, then the recommendation is to create a CMC portal, which wasn't working in our case.

Error: Account information not recognized: Could not reach CMS '<servername>:6400'. Specify the correct host and port and check for network issues. (FWM 20030).

Telnet to the port 6400 from within the server is also not working.

Regards,

Karthikeyan.SV

[ayman_salem]

As I can see from the version number you mentioned, you are using BIP 4.3 SP02 Patch 0 (14.3.2.4073) with DS 4.3 SP02 Patch 2 (version 14.3.02.545) which are incompatible.

Therefore it does not work and you should use a compatible version of BIP 4.3 and DS 4.3

see:

3197694 - SAP Data Services 4.3 and SAP Information Steward 4.3 compatibility with SAP Business Inte...

[former_member633820]

Can you confirm if under SIA->properties->configuration you are able to see the hostname?

[svkarthikeyantce]

Thanks for the answers. the telnet to CMC port 6400 is not working even within the server. Looks like the port is corrupted.
Is it possible to create a new SIA process without accessing CMC in windows?

[omkarsambare]

The error is very generic and could be because of multiple causes.

Check the update logs to find the exact cause. Additionally check if the port 6400 is utilized by any other service and available to be used by CMS Server. Involve the network team to check the same.

Check if your DS Server (CMS Server) is able to communicate with the DB Server and CMS schema specifically.

[jmuiruri]

Greetings svkarthikeyantce,

Always look for error log under BI_INSTALL_DIR/sap_bobj/logging before attempting to create a new SIA as you might end up corrupting your CMS repository.

I am sure in the logging directory there is an error*.log that should explain why this is the case.

Best Regards,

Joseph

[jmuiruri]

Greetings svkarthikeyantce,,

There is nothing like a corrupt port, you need to check why SIA could not bind to the port, could be that another process is already listening in that port.

Bottom line, the error log should provide you with a clear direction to follow.

Best Regards,

Joseph