I'm new to BI Platform and recently installed BI Platform 4.0 FP2 on the Windows x86 platform. Though services are up and running and they are green on my CCM,
But when I try to login into BI Platform CMC, I get the following error.
I tried re-starting all the services in the CCM and still the Server isnt detected. Could you help me with the possible causes for this problem and solutions accordingly?
The SIA is a daemon that will start the CMS and all the processing servers of the system.
My first question would be:
- is the CMS up and running (check in task manager)
- is it listening on port 6400 (netstat -anb in a CLI)
Also check the Event Viewer Application logs. If there's a problem starting the CMS, you should get some hints from it.
One question though: BI 4 is a 64 bits apps. You did not install it on a 32 bits env, did you? (you quote "Windows x86")
Thanks a lot for all you replies,
The netstat has got entries which shows SIA SYN_SENT.
And didnt find anything helpful in event logs.
I'm using the database supplied (Microsoft SQL) by default and the SQL services are up and running.
I'm trying to access using the local host "http://localhost:8080/BOE/CMC"
The link http://localhost:8080/BOE/CMC is the web layer. But after the CMC logon page appears on the browser, enter localhost in place of INLN50798877A, under the "system" field on the CMC logon page.
Check whether this works or not.
OK. Your CMS is most likely not starting (SIA tries to communicate on default CMS port and get nothing back, so your TCP connections hangs in SYN_SENT mode)
Again, I would advise
- to check if cms.exe is visible in task manager
- if it is, check in netstat -anb what port would cms.exe be listening on.
- if not, what the event viewer states about the reason CMS would not start.
Go to CCM and press Manage server button, then enter username/password. if it succeeds then I see no problems, if it fails, then it means that the CMS repository is down and you need to investigate why repo is not available
Also you can go to Task Manager and check for the CMS.exe and other SAP BO services (Jobserver.exe), it might be that both SIA and CMS are up and running, but the database is down, so you can not access it and the system is sending this error.