Internal Error [repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.)

This error message (generally repo_proxy) is a very generic error message and doesnt tell you much what is going on. Your problem may be different to mine. However this post shows the steps I used to troubleshoot the problem and make my windows client to connect properly.

Since my BO Enterprise server (Unix Solaris) and my Windows client PC is between a firewall, 4 ‘holes’ must be punched out to allow the data communication. These ports are for the CMS server (6400 by default & 6401) and the Input/Output repository servers (6402, 6403).

Step 1

In the ccm.config file, the following entries (in bold) must be added to ‘concrete’ the ports that BO will use for these 3 servers, otherwise it will use random ports and your firewall will just block it. Ports 6401-6403 can be any arbitary port number for which the firewall port is opened. <FQDN> is the fully qualified domain name of the server. For me, I always use the short hostname which also works.

add to cmsLAUNCH line: -port <FQDN> -requestport 6401
add to inputLAUNCH line: -port <FQDN> -requestport 6402
add to outputLAUNCH line: -port <FQDN> -requestport 6403

Step 2

Restart the above 3 servers, and make sure the servers are running by checking the CMC administrator web console. On the windows client PC, open a command prompt to verify no issues with firewalled connectivity.

telnet <FQDN> 6400
telnet <FQDN> 6401
telnet <FQDN> 6402
telnet <FQDN> 6403

Step 3

Modify your windows hosts file <C:\Windows\system32\drivers\etc\hosts> to include your BO server’s host. For example:

58.163.117.165 boserverhost01 boserverhost01.watashii.com

Step 4

Open your windows client PC’s list of Network Connections via Control Panel. Check how many LAN connections you have. Disable all of them except the one need to connect to BO. Or otherwise change your NIC binding order to the top of the list. Disable Windows firewall if you have to.

Related Posts:

1. BusinessObjects InfoView LDAP Authentication Error
2. BusinessObjects – Delete Universes in CMC
3. BusinessObjects – Insert Webi Report Images