CMS not working 4.1 SP5

[Former Member]

I was trying to fix a problem with the audit service and now I'm stuck with a no running CMS in 4.1 SP5

In the Windows Event Viewer I can see:

[Node Name: SAPBO] [User Name: Administrator] Server Intelligence Agent: no connection could be made to a CMS and there are no local CMSs available to auto-boot.

I can see the SIA working and no error appears on the configuration sheet, I can connect to the respository database (SQL Server 2008 R2) apparently with no problem.

If I try to go to Manage Servers from SIA the window says

Couldn't connect to server. Please check that the server name is correct and the server is running.

Could you help me with the steps to resolve this? what is the best approach? I've tried several KB's but mostly doesn't fit my case.

[Former Member]

What troubleshooting steps did you take while working on the audit service problem? It is important to know this before any steps can be suggested further.

However you may try the below step and let me know how things go:

1. Navigate to CCM>Properties of SIA>>Startup, and check if you see any CMS listed under Local CMS section. If yes, check if the command line; is the command line present or is it blank?

By default the Command line is: -loggingPath "<Install Dir>:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/" -startedBySIA

2. Recreating the SIA should help here. You can follow SAP KBA: 1730788 - How to Recreate a Server Intelligence Agent in BI 4.x on Windows server?[Video]

Let me know your observation after recreating the SIA.

Thanks,

Megh Vora

[Former Member]

Thanks a lot,

The problem came when I followed one note and I stopped SIA and Tomcat, ran wdeploy, undeployed web apps and then deployed them again, after that the cms didn't started.

My command Megh is just

-loggingPath "D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/"

I'm going to add the -startedBySIA command and try.

I did try to recreate the SIA but it gave me an error at the end that no cms was running I'll try again if the command doesn't fix it.

[denis_konovalov]

undeploying and deploying back webapps cannot affect auditing nor CMS starting or not starting. Unless -- how exactly did you do that ?

[denis_konovalov]

first - trace back the steps you did before things broke.

what was changed. most like you'll know what happened.

sounds like CMS is not starting, maybe there is a rouge CMS already running - when you stop SIA , are there any BOE processes still running in task manager ? (kill them and start SIA)
if doesn't help - what does CMS trace says ?
or you can try to re-create SIA. (hope your CMS DB is still alive)

[Former Member]

I have checked Auto.start at the SIA Properties - Startup - Local CMS Servers - Properties. And now the cms is working. I just have to deal with the Audit problem I suppose is better to open a new thread.

Thanks a lot and sorry if that was obvius, I really don't think I've unchecked that

[Former Member]

Hello again and thanks a lot for your help.

Changing the command line under local cms section of the SIA I've found at port I had the <Computer name>: port, it didn't let me save, I've changed it to just the port (6400).

Restarting SIA I have a lot of errors at the event viewer from BusinessObjects_SvcMgr like:

Failed to decrypt object 1076 using cryptographic key ID: 100

on several objects, then this error

Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. .

and finally:

[Node Name: SAPBO] [User Name: Administrator] Server Intelligence Agent: no connection could be made to a CMS and there are no local CMSs available to auto-boot.

I've tried also to recreate the SIA, it didn't work, here is the log, it repeats the last "Logging into... " several times and finish with ... Stopping CMS...

argv[0] = -cms argv[1] = XXXX0000WIN002:6400 argv[2] = -username argv[3] = Administrator argv[4] = -password argv[5] = ****** argv[6] = -authentication argv[7] = secEnterprise argv[8] = -platform argv[9] = win64_x64 argv[10] = -importdir argv[11] = D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\smartservers argv[12] = -name argv[13] = SAPBO argv[14] = -siaport argv[15] = 6410 argv[16] = -adopt argv[17] = -cmsport argv[18] = 6400 argv[19] = -usetempcms argv[20] = -dbdriver argv[21] = sqlserverdatabasesubsystem argv[22] = -connect argv[23] = DSN=BOEREPO;Description=BOEREPO;UID=boadmin;PWD=******;APP=SAP BusinessObjects;WSID=XXXX0000WIN002;DATABASE=BOEREPO;;Trusted_Connection=no argv[24] = -dbkey argv[25] = ****** argv[26] = -dots Logging into XXXX0000WIN002:6400 as user Administrator with secEnterprise authentication... Attempting to start CMS (1 of 1)... argv[0] = D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/CMS.exe argv[1] = -name argv[2] = SAPBO_temp_20170214_084443.cms argv[3] = -dbinfo argv[4] = D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/_boe_SAPBO.dbinfo argv[5] = -port argv[6] = 6400 argv[7] = -dbdriver argv[8] = sqlserverdatabasesubsystem argv[9] = -connect argv[10] = DSN=BOEREPO;Description=BOEREPO;UID=boadmin;PWD=******;APP=SAP BusinessObjects;WSID=XXXX0000WIN002;DATABASE=BOEREPO;;Trusted_Connection=no argv[11] = -dbkey argv[12] = ****** argv[13] = -noaudit argv[14] = -tempmode argv[15] = -fg argv[16] = -restart Using working directory D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64. Logging into XXXX0000WIN002:6400 as user Administrator with secEnterprise authentication... Sleeping for 5 second(s)...

.....

Logging into XXXX0000WIN002:6400 as user Administrator with secEnterprise authentication... Sleeping for 5 second(s)...

.....

... Stopping CMS...

[Former Member]

Hi Cesar,

Do you have SSL enabled in the SIA's properties? Navigate to CCM>>Properties of SIA>>Protocol and check if the checkbox is enabled or not? If it is enabled then uncheck it and then try to start the SIA. Before starting the SIA make sure there are no stale CMS.exes running in the Task Manager.

With what account are you running the SIA? Local system account or the Domain account?

When you start the SIA does the CMS.exe come up in the Task Manager and then crash or it does not come up at all?

Thanks,

Megh Vora

[Former Member]

Hi Megh,

SSL is not enabled, the account is the local Administrator, the System Account checkbox (bellow the Log on As) is not checked.

CMS.exe doesn't come up.

Thanks to you Megh!

[denis_konovalov]

Sounds like you need to open a support incident with SAP and have a proper investigation done.
the errors do not make sense if all you did was webapps re-deploy.

[Former Member]

Hi Denis,

I had the audit service not working before the re-deploy I did the re deploy trying to repair it that but instead it got worst,

Cms was working before the redeploy, I was able to enter the cmc but not to execute webi reports via launchpad.

I'm having some errors like this one in the Event viewer with source BusinessObjects_CMS

Failed to decrypt object 1082 using cryptographic key ID: 100.

[denis_konovalov]

what exactly do you mean by "re-deploy". What exact steps you took ?

[Former Member]

Sorry Denis, I'll try to tell the whole story. I just stopped SIA, stopped Tomcat, executed wdeploy, executed the cancellation of the deployment and then did It again. (Sorry but the system is spanish and maybe the words are not exact)

But I had problems before doing that, maybe it's all connected:

We had a phisical problem with the Server and the databases where marked as suspect. O fixed that and checked them, everything seemed correct but the audit service wasn't working.

I executed the setup - repair but lost two files with the repair that I had to recover I read that's a bug with SP5

Then the system was again working but not the audit. I tried to execute the configuration wizard but got an Error 500.

Then I read that may be fixed deploying again web apps and so I did It.

[denis_konovalov]

well, sounds like one of 2 things - bad install or bad CMS DB.
I really think you should work on this with SAP via Incident. It needs proper investigation which is not possible in a forum format.

[Former Member]

Thanks Denis, I undeployed and then deployed again the web applications and then came the problem Denis, where can I find the CMS trace?

[former_member185603]

As Dennis suggested recreate the SIA . CMS traces you will see in Logging folder.

[amitrathi239]

Sometimes restart of server will help..have you tried?

[Former Member]

Thanks Jawahar, I've done it again but still cannot log in. I get the same error. :_(

[former_member185603]

Stop the SIA and provide CMS DB credentials again.