Cannot access the repository (USR0013)

Hi All,

I am getting the following error when I login to Deski in Enterprise mode.

[repo_proxy 13] SessionFacade::openSessionLogin with user info has failed(Unable to connect to cluster @BOXISERVER to retrieve CMS member list. Locally cached member list not present. Logon cannot continue.(hr=#0x80042a01)

Can anyone please help me on this.

For all your information, the same software has been installed in various other Desktop PC’s and there was no pbm at all. This one has been installed in my LAPTOP and can you please help me to sort this out.

Thanks all.


Help_me_BOB (BOB member since 2007-10-23)

This error message appears because the laptop may not be having ‘@CLUSTERNAME’ listed in the following registry key

 HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Enterprise\CMSClusterMembers 

Update the registry key by adding a new string value with the name of the key as ‘@CLUSTERNAME’ (value of this key is the actual server name)
eg
value name: @SERVERNAME.DOMAIN.NET
value data: servername.domain.net;

.


haider :es: (BOB member since 2005-07-18)

I tried this and it did not work. I even rebooted the XP machine to reload the registry and it still does not work.

Here’s the setup:

One XP SP3 workstation with Designer installed
One Lab server (RHEL 4) running Edge (essentially a mock-up of the client server)
One Client site server (RHEL 4) running Edge accessed through VPN

Registry values in XP machine:
@LABSERVER.LABDOMAIN.NET labserver.labdomain.het;
@CLIENTSERVER.CLIENTSITE.COM clientserver.clientsite.com

When I bring up Designer and point it to the local machine, it logs on. Values:
System: labserver.labdomain.net
User Name: Administrator
Password: (blank)
Authentication: Enterprise

Logon succeeds.

When I point Designer to the client machine, I get the “Cannot access the repository” message (precise error below). Values:
System: clientserver.clientsite.com
User Name: Administrator
Password: (blank)
Authentication: Enterprise

I insure I have the VPN running. There is an entry in the hosts file on the XP machine mapping the clientserver.clientsite.com name to the proper IP address, so it’s not a DNS problem. I can point a web browser to the clientserver.clientsite.com address and bring up both the CMC and the Desktop, and both work fine. Any hints?

Logon message error text:

[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communications failure) (hr=#0x80042a01)

rbfthomas (BOB member since 2008-06-24)

rbfthomas,

In the beginning part did you mean to say the following?

“When I’m on the client machine, load Designer and point to the server machine”

Would it be possible to have the client machine get an IP address in the same subnet as the server? What I mean is this:

Server: 192.168.1.1
Client: 192.168.2.1 (cannot connect)
Change Client to: 192.168.1.2 (can connect)

Do you see the difference between the two outcomes for the client? You mentioned something about VPN but I’m not sure how that plays into it. You also mention that accessing the CMC and Desktop is fine, it’s just seems to be a problem with Designer. In my experience, being on different subnets has spelled the difference in getting access to Designer as it seems BO has put some kind of network “test” on the capability to get in via Designer.

Just a shot in the dark and something to think about as you further narrow down the problem/resolution.

Thanks,
John


jsanzone :us: (BOB member since 2006-09-12)

Thanks, John. That was what I meant - firing up Designer and trying to log into the server.

If it’s a being-on-the-same-subnet problem, it may be an intractable problem. The VPN is what connects my local machine to the client network, and I’ve no idea how our network admin set it all up. To give you an idea:

My lab network: 192.169.10.xx
My XP machine primary NIC IP: 192.168.10.69
VPN connection IP: 10.98.0.10
VPN routing connection: 10.98.0.1
Client network: 172.60.0.xx
BO machine: 172.16.0.128

If Business Objects gets confused by machines on different subnets, this looks impossible. Yet I can’t believe I’m the only person who has ever tried to manage this over a VPN.


rbfthomas (BOB member since 2008-06-24)

rbfthomas,

Maybe everyone else whose tried it had dumb luck in landing in the same subnet and never noticed a “problem”. Is there any way that your network engineers can land you (client) and the server (BO machine) on the same subnet? As you wrote:

Try something like this:
Client network: 172.60.0.xx
BO machine: 172.60.0.128

If this works then “my theory” proves out, if it doesn’t then I’ll get my coat and you’re still stuck and will probably need BO Tech Support to help troubleshoot. Good luck and please keep us posted.

thanks,
John


jsanzone :us: (BOB member since 2006-09-12)

I’m getting the same error.

It’s not the network as I can connect no problems when I point Designer to each machine individually.

I have currently BOE XI R3.1 FP1.6, but over the years have had on my laptop numerous other versions of BO clients.

In the registry I have two paths:

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Enterprise\CMSClusterMembers

and

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12\Enterprise\CMSClusterMembers

This is where it gets interesting.

I add a multi string value called it @ClusterName, and for the string values added the machine names.

It didn’t work.

However, at this point in time I was mindful that I was adding thiis to Suite 12 and not suite 11.5.

I carried out the same in 11.5 and hey presto, it works.

I repeated the steps on a machine that only has suite 12 installed, and it doesn’t work.

So to cut a long story short, there seems to be an issue with clustering of the client in XI R3.1. :hb: :hb: :hb:

Is anyone able to carroborate my findings?


The Emu :australia: (BOB member since 2002-09-13)

I posted this elsewhere, this solution may work for anyone else encountering this issue…

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 :lol:


Veronica (BOB member since 2002-11-22)

Just encountered the exact same problem, and thought I’d post my fix.

I had the same situation - a user could log on with her desktop, but not with her laptop. In the end we fixed it by copying the contents of the My Documents\My Business Objects Documents\LocData folder across from her desktop onto her laptop.

It appears these files hold security information for each CMS name you log on to, and in the case they’re not present BO gets a bit confused and just says it can’t connect to the CMS and get the member list.

Hope this helps,
Colin


crmckay (BOB member since 2006-08-29)

Wanted to chime in with another fix.
I have a 2-node cluster in XI r2 on Solaris.
When trying to connect Import Wizard for the first time, I was getting this error.
But I found that once I connected IW to one of the nodes directly, the proper @CLUSTERNAME key was added to my Windows Registry on my laptop. Now I can connect to the @CLUSTERNAME just fine with any client tool. :mrgreen:


gmyers :us: (BOB member since 2008-07-14)