Can't log in to CMS

[former_member403878]

Hi,

We are having an issue with a new-ish install of SAP BO. We installed the application a few weeks ago and were able to log in to the CMC console and make a few minor adjustments (setting email, sftp servers for AdaptiveJobServer).

We had to put the process on pause for a couple of weeks and now, on returning, cannot log in to CMC - not aware of anything changing in between. Looking at task manager, on a SIA restart, I can see the CMS.exe process but after around a minute, disappears

Nothing meaningful within the log folder although the tail end of cms_xx.CentralManagementServer_ncs.trc has

[Thr 5176] tracesize_threshold=1000000;
[Thr 5176] zombie_check_interval=300;
[Thr 5176] zombie_timeout=86400;
[Thr 5176] NCS configuration info end----------------

[Thr 5176] Thu Aug 10 18:17:42 2023
[Thr 5176] NCS_ProcExit API started
[Thr 5176] Timer threads are successfully finished
[Thr 5176] Data sending threads are successfully finished
[Thr 5176] *** WARNING => NiCloseHandle: invalid hdl 0 [nixx.c       1713]
[Thr 5176] *** WARNING => NiCloseHandle: invalid hdl 0 [nixx.c       1713]
[Thr 5176] NCS_ProcExit API invoked

and cms_xx.CentralManagementServer_trace.000003.glf has

The SIA trace file did have something meaningful... although doesn't help me to know what went wrong or how to resolve, these being

CentralManagementServer has been started.CentralManagementServer stopped with exit code = 0 (0x0).CentralManagementServer is considered failed because it has stopped 5 time(s) within 60 minute(s). Please restart this server.CentralManagementServer has failed and the Server Intelligence Agent has not been able to connect to the cluster. Please verify your CMS port and database settings are correct.Restarting the SIA (which I assume is what it was saying to do), repeats the failure process... while it was going through this, I was monitoring ports and nothing was showing as on port 6400
Any other suggestions on what I need to look for or can try?

[DellSC · Accepted solution]

I would make sure that the CMS can connect to its database. Not being able to connect can cause this issue.

-Dell

[former_member403878 · Accepted solution]

Hmm... how do I confirm this?

I can log on to the database using the user we configured during installation

However, it has made me think... (I know little of BO, just following instructions provided to me), we are installing BO BI Platform on one machine and BO Data Services on another. On the Data Services installation instructions, I had to put SIA on that box first... so for installing BI Platform on one machine and the SIA on the other, both requested a CMS database for which we gave the same user to same db... this was supposedly as a cluster... is that the way it is meant to be done or should they have their own user?

[DellSC · Accepted solution]

It's been a few years since I've installed Data Services, so I'm going on rusty memory here....

- The CMS service should only be installed on the BOBJ server - it shouldn't be running on the DS server. Also, the DS repository should NOT be in the same schema as the BOBJ CMS database.

- The BOBJ server should be installed first so that you can point DS to that as the CMS when you do the DS install. You need to use the same "Cluster Key" for the install on both servers, along with connecting them to the same CMS database.

- In the Central Configuration Manager on the BOBJ server, stop the SIA and go to its Properties. Go to the Configuration tab and you'll see where you can set the cluster name for your cluster. This configuration is not done by the installer and must be done manually after installation. You can also change the Cluster Key on this screen - what it displays is the encrypted version of the key.

If none of this information helps, you'll probably need to open a case with SAP support to get your system working.

-Dell

[former_member403878 · Accepted solution]

Thanks again... apologies, I did say one thing wrong, on the "DS" server, the instructions required the installation of Information Platform Service (rather than SIA) which itself asks for a CMS (and audit) database - it is this which I'm suspecting has "overwritten" the BO CMS and caused the CMS service to fail - not sure what this Information Platform Service is but should this be having its own CMS database?

[former_member403878 · Accepted solution]

Thanks for your help, repointing to the other database resolved this issue