cancel
Showing results for 
Search instead for 
Did you mean: 

BI Platform Support Tool Issue: Unable to logon to CMS

0 Kudos

My BI support can't login to my CMC. The CMC is on SuSE Linux, everything is on Tomcat 8. I'm running windows 7x64 on my desktop.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Robert ,

Since you have BI Platform configured for Corba SSL, you need to edit the BISupportTool64.bat to include the below parameters.

-Dbusinessobjects.orb.oci.protocol=ssl

-DcertDir=<SSLFILEPATH>

-DtrustedCert=cacert.der

-DsslCert=servercert.der

-DsslKey=server.key

-Dpassphrase=passphrase.txt


More details here:-

Thanks,

Swapnil

Toby_Johnston
Advisor
Advisor
0 Kudos

If the BI landscape is configured for Corba SSL then you can follow these instructions to connect from the BIPST:

https://wiki.scn.sap.com/wiki/display/BOBJ/SAP+BI+Platform+Support+Tool#SAPBIPlatformSupportTool-How...

Former Member
0 Kudos

Hello Toby,

Robert has an issue related to Corba SSL where he was requested for landscape report.

Thanks,

Swapnil

Toby_Johnston
Advisor
Advisor
0 Kudos

Ahh thanks for chiming in here.  That explains why he was having issues connecting to his CMS from the BIPST

0 Kudos

Thanks for your help. This was the correct information

Toby_Johnston
Advisor
Advisor
0 Kudos

Thanks for the update Robert.  Glad it's working now.

Answers (2)

Answers (2)

former_member398039
Participant
0 Kudos

Hi Robert,

Can you please clarify what do you mean the BI Support Tool cannot login to CMC? What is the error message? If you can attach a screenshot that would be great. The Support Tool wouldn't be connecting to your CMC, it would connect directly to the CMS. Are you able to telnet the CMS port (i.e. 6400) from your desktop?

Thanks,

James

0 Kudos

Thanks James;

I tested the connections using the Landscape tool

I get the same error regardless of using a host name or IP address. The error is returned very quickly, as if it doesn't make an effort to connect although I can see packets when I look at it through tcpdump.

09:31:05.913129 IP (tos 0x0, ttl 127, id 29324, offset 0, flags [DF], proto TCP (6), length 52) pc00818.ad.dga.org.38462 > dgalx-ereports.dga.org.6400: S, cksum 0xbaa8 (correct), 3910135354:3910135354(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>

E..4r.@...{S.........>.....:...... .................

09:31:05.913161 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52) dgalx-ereports.dga.org.6400 > pc00818.ad.dga.org.38462: S, cksum 0x0e0b (incorrect (-> 0x7614), 3797829911:3797829911(0) ack 3910135355 win 14600 <mss 1460,nop,nop,sackOK,nop,wscale 7>

E..4..@.@.,............>.^I....;..9.................

09:31:05.913425 IP (tos 0x0, ttl 127, id 29325, offset 0, flags [DF], proto TCP (6), length 40) pc00818.ad.dga.org.38462 > dgalx-ereports.dga.org.6400: ., cksum 0xafc5 (correct), 1:1(0) ack 1 win 16425

E..(r.@...{^.........>.....;.^I.P.@)..........

09:31:05.917014 IP (tos 0x0, ttl 127, id 29326, offset 0, flags [DF], proto TCP (6), length 43) pc00818.ad.dga.org.38462 > dgalx-ereports.dga.org.6400: P, cksum 0xdb49 (correct), 1:4(3) ack 1 win 16425

E..+r.@...{Z.........>.....;.^I.P.@).I..aps...

09:31:05.917028 IP (tos 0x0, ttl 64, id 1961, offset 0, flags [DF], proto TCP (6), length 40) dgalx-ereports.dga.org.6400 > pc00818.ad.dga.org.38462: ., cksum 0x0dff (incorrect (-> 0xef78), 1:1(0) ack 4 win 115

...(..@.@.%C...........>.^I....>P..s

09:31:05.917095 IP (tos 0x0, ttl 64, id 1962, offset 0, flags [DF], proto TCP (6), length 44) dgalx-ereports.dga.org.6400 > pc00818.ad.dga.org.38462: P, cksum 0x0e03 (incorrect (-> 0xee34), 1:5(4) ack 4 win 115

E..,..@.@.%>...........>.^I....>P..s.......8

09:31:05.917117 IP (tos 0x0, ttl 64, id 1963, offset 0, flags [DF], proto TCP (6), length 457) dgalx-ereports.dga.org.6400 > pc00818.ad.dga.org.38462: FP 5:422(417) ack 4 win 115

E.....@.@.#............>.^I....>P..s....IOR:010000003500000049444c3a696d672e7365616761746573

09:31:05.917265 IP (tos 0x0, ttl 127, id 29327, offset 0, flags [DF], proto TCP (6), length 40) pc00818.ad.dga.org.38462 > dgalx-ereports.dga.org.6400: ., cksum 0xae86 (correct), 4:4(0) ack 423 win 16319

E..(r.@...{\.........>.....>.^J.P.?...........

09:31:05.918492 IP (tos 0x0, ttl 127, id 29330, offset 0, flags [DF], proto TCP (6), length 40) pc00818.ad.dga.org.38462 > dgalx-ereports.dga.org.6400: F, cksum 0xae85 (correct), 4:4(0) ack 423 win 16319

E..(r.@...{Y.........>.....>.^J.P.?...........

09:31:05.918501 IP (tos 0x0, ttl 64, id 24978, offset 0, flags [DF], proto TCP (6), length 40) dgalx-ereports.dga.org.6400 > pc00818.ad.dga.org.38462: ., cksum 0xedd1 (correct), 423:423(0) ack 5 win 115

E..(a.@.@..Y...........>.^J....?P..s....

former_member398039
Participant
0 Kudos

Hi Robert,

Can you try using hostname instead of IP address when connecting via the BIP Support Tool? Let me know if this works.

Thanks,

James

0 Kudos

I tried it both ip addresses and domain names with the same results. I also tested using A records and Cnames along with FQDNs and host name only,

Finally, I tested it against our old system, the one we're trying to replace on windows 2008. That connected as expected.

Thanks

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,


It could be that in the corba handshake the CMS is returning the local hostname of the server which is not resolvable by the client.  Try the following:


1. Logon the BI server (where the CMS is running) via a terminal.  Then run the command hostname.


2. Then on the client (where the BIPST is running) edit your hosts file C:\Windows\System32\drivers\etc


3. Add an entry to your hosts file with the BI hostname (as found in step 1 above) and the IP address (that is reachable/pingable from the client). 


Then try the CMS logon again and see if it works.

Regards

Toby

0 Kudos

The hostname in this circumstance is being returned as expected. I can ping the unadulterated host name without host file entries.

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

Thanks for confirming.

The BIPST client communication works the same as other BI clients.  Are you able to connect to this CMS from the Web Rich Client or Universe Designer?

Is there a firewall between the client and server?  Initially, the BI client will connect to the CMS on port 6400 but then once the handshake occurs, communication will continue on another port (request port).  The request port is dynamic (auto-assign) by default but can be set to static in the CMC-->Servers-->CMS Server Properties.

Let us know what you find out and we can suggest further troubleshooting steps.

Thanks

Toby

0 Kudos

The only firewall is the local workstation windows firewall. I was tested on a newly imaged computer that had no firewall settings nor any software that could interfere with data transmission. Same issue. I took a packet capture from my own computer trying to make a connections. I found this packet

I'm not sure what I should see on a normal connection. Do you have anything you can compare with?

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

Could you send this wireshark (.cap) capture to my email?  toby,johnston@sap.com

This was going to be the next thing that I was going to ask for.  Inside the payload of a certain packet will be the corba handshake reply from the CMS which should provide the necessary clue to understand the problem.

Also, did you try other BI clients to see if they are working? 

Thanks

Toby

0 Kudos

Toby

I haven't tried any other clients. I'll see if I can get one of the research people who kuse the design tools to logon for me to test.

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

Also, please run the following commands to help us understand if this server is multi-homed as this is a common issue with corba communication:

ifconfig –a

netstat -anp | grep 6400


If you would prefer to email me the results please send to toby.johnston@sap.com


Thanks

Toby

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

Thanks for sending that.  It looks like there is only one IP address for this host and I can see other BI servers connecting to the CMS but no connections from other hosts to the CMS.

I'd like to have you set the requestPort for the CMS.  Go to the CMC ( for example:   http://server:8080/BOE/CMC), Logon as Administrator, then go to Servers and right click and select properties of the CMS server.  Under Common Settings, find Request Port, then uncheck Auto Assign.  Then enter in a new port number that is unused on the host.  Then, save the changes  and restart the Server Intelligence Agent (stopservers.sh and startservers.sh). 

From the BIPST client, try again with the Communications Analyzer "Test a single TCP connection" and test the connection to the newly assigned static Request Port and let me know if that works ok.

Also, it would still be helpful to know if other BI clients (specifically Universe Designer or Webi Rich Client) are working against this server.

Will look forward to your reply.

Thanks

Toby

0 Kudos

Toby

I tried to change the request port from dynamic to fixed using an unused port. Once I did I lost access to my CMS and was unable to login to the CMC as well. In the end I ran a restore from my local backup. Next time I try that I'll make sure I have a snapshot ready. Its less stressful than waiting for Veeam to put the data back from the day before's backup.

former_member398039
Participant
0 Kudos

Hi Robert,

If CMS doesn't start after you have changed the Request Port, I would check the Event Viewer or /var/log/messages (or equivalent), it should be able to give you hint on what went wrong.

Thanks,

James

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

If you'd like to do this together next time on a Citrix GoToMeeting, I'd be happy to.  Just let me know and I can send you a meeting request.

Thanks

Toby

0 Kudos

Sorry, I hit post by accident. My BI is 4.2. SP2 patch 3. BI support is version 2.0.4 I'm trying to give SAP support a report on my configuration, I have an acknowledged bug they need to research.

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Robert,

Inside the BI Support Tool client, click on Landscape Tools, Communications Analyzer.  Then under 'Test a single TCP connection', enter your CMS hostname and port (for example  mycmshost and 6400).

Then click Test.  Does the result come back successful?

From the same client host, are you able to connect to the CMS with other BI clients such as Information Design Tool, Web Intelligence Rich Client, etc?  

Regards,

Toby