Failure to login to BO XI Designer - repo_proxy 13

[MrHopkinson]

We’ve recently installed BOE-XI r2 onto a Sun Platform on an ORACLE 10g Database. Now when I try to access Designer I’m getting an error:- ‘Cannot access the repository. (USR0013)’

[repo_proxy 13] SessionFacade:penSessionLogon with user info has failed(Unable to log on: Could not connect to server . Please check that the server name is correct, and that the server is running.

I assume this is because there is NO ENTRIES in the top ‘System’ box of the login screen. This doesn't occur when using Desktop Intelligence Client - although we’ve placed the file ‘BUSOBJ_j2ee.extranet’ in our BO--/ locdata directory which gives us the ‘busobj:8080 (J2EE Portal)’ in the said System selection box.

Nb. Authentication type of LDAP if that’s any further help..

Many thanks in advance..
Steven

 

[skrandel]

You have to supply the name of the server yourself. It will NOT populate the box until you use it one time.

Designer is a 2 tier product. The entry gets there when you've logged in once.

Steve Krandel
Intuit

 

[MrHopkinson]

Steve,

Thanks for the suggestion but I believe you replied on the BOB board forum - although for the benefit of others.. the latest on this is that having tried to ent4er the server name into the System box followed by LDAP login details, the error message returned this time was:

.. and the error message returned was: ‘[repo_proxy 13] SessionFacade:penSessionLogon with user info has failed(Security plugin error: Failed to set parameters on plugin.(hr=#0x80042a01)’

nb. I can login fine using the 'Enterprise' Authentication username & password.

regards

Steven

 

[MrHopkinson]

to whom..

for those interested.. the solution was little to do with Business Objects but that the LDAP Authentication Server was within a private network which our PCs did not have access to... Once our Network people gave access for our Client PCs BO Designer success! It would seem that BO Desktop Intelligence wqas working with the aide of this J2EE file was simply a workaround and not the solution.

nb. This also somehow seemed to clear up a connection problem I was having between converted 6.5 to XI reports and Universes..

hope this helps..

Steven