Hi All,
when I am trying to connect to DeskI(Client tools) through VPN, I am getting the following error ( “OpenSessionLogon with the user info has failed:
Transport Error : Communication Failure(hr=#0x80042a01)”).
I am successfully able to connect to the client tools using LAN.
I can able to launch infoview without any error(through VPN and LAN).
I have problem launching client tools(DeskI) through VPN.
we have no firewall issues, the port was open for all communications.
any body have any ideas or solution for this kind of errors.
I am facing the same issue.
I noticed that my CMS is setup on a different subnet domain and that could be a possible reason why I am not able to access the CMS from DeskI and Designer.
Is anyone aware of the port used by the client applications to talk to the server?
My issue got resolved.
Launching and logging into DeskI successfully (uses Ports A & B)
Retrieving/Sending documents to/from Input File Server (uses Port C)
Retrieving documents from Output File Server (uses Port D)
so we need to open all ports for communication from the client machine.
My issue has been resolved too, though temporarily.
There were 2 cms servers ruinning (on seperate machine, pointing to the same cluster).
I had to stop one and then I was able to login from DeskI and Designer.
I believe these are the default Ports BusinessObjects Uses in order for the web and the software client to function:
8080 - for the admin launchpad hosted by Tomcat
8005 - shutdown port - Tomcat
8443 - redirect port - Tomcat
3306 - MySQL Database for BO System Data
9080 - Websphere
6400 - BO-InfoView/CMC Login
Possibly 22, 80 as well. (Not 100% on these.)
I would make sure all of these ports are open to the server from your client location. If they are open on the firewalls, then you should be fine…
I think BO needs to document the ports better to make their product a little more user friendly because at the time of this posting, I did not find any good documentation. Good luck!
In order to know which port your application (deski or designer) is trying to connect, you can try following command from command prompt.
netstat -na
-a Displays all connections and listening ports.
-n Displays addresses and port numbers in numerical form.
First you apply credentials (System, Username, Password and Authentication Type) and press ok then you use netstat -na command on command prompt you will come to know which port it is trying to connect.
can you explain a little more. I’m having this problem (0013).
I run netsat -na on the client
Try to log into Deki from the client
I run netstat -na on the client again.
I don’t see any difference in the output of netstat -na from before and after I try and log into Deski.
With this problem is it the cliemt or the server thats the issue? Is it ports 6400,6401,6402 on the client that need opening or on the server. Sorry for such a dumb question but this isn’t my area of expertise.
We just installed BOXI R2SP2 on Linux RedHat. We can connect to CMS using Web interface from our Windows based workstations. We can run sample reports that were installed by default. However when we installed client software, like Universe Builder, etc. when trying to connect to CMS we are getting this error:
[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.
(hr=#0x80042a01)
Based on your other responses we opened ports 6400, 6401 and 6402, but it didn’t help. Any other suggestions? Since it is a Linux based server we cannot install the clinet part on the same machine and try it there to eliminate the firewall issues. How is one supposed to trace those problems? I did try netstat and like jane123 saw absolutely no difference.
That Linux machine already had a Web Server running on port 80 and another one - on port 8080 so when we installed BOXI we installed Tomcat and designated ports 8040, 8041 and 8042 for the ports to be used when asked about ports during installation. I am not sure it is relevant at all, but just in case… Since existing reports run from CMS and Infoview I asuume our port changes worked out fine. For CMS, though we didn’t change the default port and we are having problems.
I have recently installed BOE-XI onto the Sun platform on ORACLE database, now when I try to access the database,I am getting an error : "Cannot access the repository(USR0013).
We had a similar problem with a certain PC not accessing the Live server through Designer. some PC’s could, but certain ones that used to be able to do it before, were no longer able to, we re-installed the software, re-imaged the PC nothing changed. The solution was as follows :
1) Ping the BO Server you are trying to access, and note what is the Fully Qualified Domain Name of the BO Server (eg : DS3-LIVERSERV.COMPANY.LOCAL) 2) In your local machine where the error is occuring access the host file called “hosts”, usually found in : C:\WINDOWS\system32\drivers\etc 3) Open the file, and input the IP address of your Live server, and also write down the Fully Qualified Domain Name next to it, make sure this IP address is at the top of the list of any IP addresses that are there. 4) Save file and exit. 5) In Designer, at the login screen, in the System text box put the Fully Qualified Domain Name with the port number used to access the server, so for example : DS3-LIVERSERV.COMPANY.LOCAL:6400
…use your usual username/password… and that should work
I found the solution for this issue in Deski XI R2.
1.If you are in the different network please open the 6400 port into your firewall.
2.Install the Deski and goto the infoview.
3.Click new select the Desktop intelligent document.
Fist time must need to open from the Infoview so repository automatically saved in your system. Now goto the program file and open the deski it will open.
(BOB member since 2005-07-28)
(BOB member since 2006-07-21)
(BOB member since 2006-01-19)
(BOB member since 2006-02-22)
(BOB member since 2009-06-17)
(BOB member since 2007-01-09)