Here is the error meesage I get when try to log into server from Desiner.
Error Detail…
[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.
(hr=#0x80042a01)
Everything still up and running on client, just cant access from my local machine.
Any ideas??
jmyoung (BOB member since 2007-05-24)
JMY:
Did you ever get any relief to your problem? I too am suffering from the same exact problem, however, in my case, I once was able to access the repository, then the server’s hard drive died. The server was rebuilt, however, it’s old name was not used (it used to be called duck1, now it is duck), and now I can’t reach it w/ Designer. When I fire up my application software, Designer, its got duck1 pre-populated, I change it to duck and continue logging in and still get the same transport error problem. I had this problem over a year ago with the initial install and working with tech support they had me uninstall BO XI R2, “clean out the registry” and remove any remnant files under c:\program files, etc, etc. I’ve tried all of that this time as well and still puzzling is that duck1 remains pre-populated, even after uninstalling the software and re-installing. I can’t think of where duck1 is pre-populated from, and why it willn’t let me sign in to duck. This is terribly frustrating…
Thanks,
John
jsanzone 
(BOB member since 2006-09-12)
Hi,
do you have any firewall from local machine to server. if yes, you have to open the port.
RadN (BOB member since 2003-04-28)
John,
How did you ‘clean’ the registry? For client tools, the server name is read only from the registry.
I suggest uninstalling the product (all BO products), deleting all files under c:\program files\Business Objects, running CCleaner to delete all remaining BO registry keys.
This should fix it.
Regards,
-C
christinamaars (BOB member since 2007-06-12)
AarKayNet: in this instance there is no firewall. We’ve got a “lab type” situation going on here and I’m trying to run Designer on my laptop and connect to the server via a mini-hub in a bare-bones “peer-to-peer” setting.
C: thank you for the suggestion and plug to use CCleaner (quite a neat product).
I went ahead and uninstalled all BO products, removed all files under c:\program files\BO, ran CCleaner, rebooted, then re-installed BO client. All to no avail. This is crazy, I can see the database via MS SQL analyzer/Enterprise Manager, I can mount shared directories from duck, I just can’t seem to get the BO product (Designer) to connect to the CMS on duck. I’m going to have to submit another trouble ticket to BO Tech Support to see if they can coach me through this problem again. arrrrgh.
Thanks,
John
jsanzone (BOB member since 2006-09-12)
I am also getting the same error. Did you got the solution? If yes, please tell me, its very urgent…[/u]
ferozster 
(BOB member since 2007-06-14)
It was an issue with the firewall protecting the server the BO software is loaded on.
Our db admin pulled the whole firewall down, had me open the Designer to see what port it was coming in on and now keeps that port open.
jmyoung (BOB member since 2007-05-24)
Thanks for the reply, but i don’t have any firewall running when i enquired with dba. What might be other possibilities of this error???
ferozster (BOB member since 2007-06-14)
How did your db admin check, which port the Designer was trying to talk to?
Let know
~aquariansp
aquariansp (BOB member since 2004-07-27)
Reference my posting from 13 Jun, this is the rest of the story:
The [repo_proxy 13] error seems to be a catch-all for BO in that I’ve worked with this software (XI R2) for 1 1/2 years now and each time I’ve encountered [repo_proxy 13] it has been for a different reason, thus, I have found out that I need to apply troubleshooting checks all over the place until I’ve find the problem. In my particular case I just resolved my [repo_proxy 13] error I’ve been working on this week, and here was my scenario. Our server in the lab died due to a hard drive failure, so we cut our losses and installed a new & more powerful server. When the rebuild was done I could not connect from my laptop to the repository via Designer (good old [repo_proxy 13] error). After much angst, etc, etc I found out that the servers in the CMC (http:///businessobjects/enterprise115/admin/en/admin.cwrwere) were all down except for one (even though CCM showed all servers “up”). When I went to start the servers in the CMC I was prompted for an account, and no matter what account I tried it won’t work. So I went back to the CCM servers and stopped them all, then changed the default account it was using from LocalSystem to the administrator account, restarted all servers in CCM, went back to CMC and noted that all servers were now up as well. Then I went back to my laptop and used Designer and was able to successfully log in. Thus, the end of my story, however, it seems that many [repo_proxy 13] errors have different beginning and endings. For instance, a year ago I had the same [repo_proxy 13] error and brought it to BO tech support. They determined that I had to uninstall my client from my laptop, clean out the registry for any references to BO keys, and remove the c:\program files \Business Objects folder, then reinstall, and sure enough it worked in that case, but not in this case when I tried it again. By digging deeper I found out the root cause to my current problem, and voila, I’m in!
Thanks,
John
jsanzone (BOB member since 2006-09-12)
To resolve the error, change the binding order of the network interface cards (NICs) on the Enterprise XI server as follows:
Make sure to restart CMC.
Another way to resolve this error is specify :port on all BO services, this change can be done it in command of each BO servers in CCM
mchoure 
(BOB member since 2003-09-04)
Hi
thanx for all ur ideas…
I also face this issue often…
Cause of prblm in my case is that CMS gets stopped automatically.
Resolution: start the CMS thru CCM and the prblm is gone
Regards
Rajan
rajansehgal (BOB member since 2008-09-22)
Hi,
I have been having this issue every now and then. I have BO enterprise loaded in VMWARE windows 2003. When I log into designer, sometimes, it works and sometimes I got the USR0013 error. Few times, I restarted my database server and that clicked. And sometimes that solution didn’t help either. My firewall and port wasn’t an issue too. Today I hit the same error and eventually what worked is, I restarted the CMS server through the configuration panel. After that the issue has not been recurring.
Thanks,
Janaki
jgopalan (BOB member since 2008-02-25)
I am not able to log on BO XI 3.1 designer,after instalation when i am going to logon designer the error show “Cannot access the repository (USR0013)”
details:
[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(The system tssr0012 can be contacted, but there is no Central Management Server running at port 6400.
(hr=#0x80042a01)
Thanks in advance …
Vills (BOB member since 2007-10-24)
Were you able to resolve the issue? I too cannot log into Designer through my local machine after installing XI 3.1. I have restarted all my servers through the CMC and through the CMS but still no luck.
okiedokie29 (BOB member since 2008-06-26)
Hi There,
I have installed BO XI 3.1 client tool on my local machine. I am sitting at offsore location and BO CMC server is set Onsite location. Firewall to open ports 6400 is already done. Also i am able to Telnet the server using (server name /IP) for 6400 port.
Now when i try to login through Designer i get error “Cannot Access Repository (USR0013)”. As I am able to Telnet I am not able to find what can be the possible iissue in my case. The Operating System is Windows.
Please suggest some solution. Thanks in Advance 
Anita27 (BOB member since 2011-08-11)
Same with me…I got the Firewall opened for port 6400 to production server. Trying to access using client on my machine. I continue to get this transport error. Have you been able to resolve this issue? It is the same exact situation with me…
chetanmaniar (BOB member since 2008-02-06)