repo_proxy 69 error when connecting to universe

[Former Member]

On the BO server (BI 4.1 SP2) I have created a 32 and a 64 bits connection with exactly the name. In Designer I created a connection linked to this ODBC.
Everything is working fine. Reports can be modified, freshed and scheduled. So far so good.

When I import a universe in Designer I get the message "[repo_proxy 69] ConnectionFacade::getConnection - Unknown exception raised" followed by the message "Universe succesfully imported" and the message that I am not authorized to use this document.
I am logged on as administrator so I have all the authorization

I repaired the software, but still get the error message. It seems to be a problem with the connection. When I select from the menu "Tools/Connections" I get the error message "An Invalid argument was encountered". I can view the connections created in Designer, but as soon as I want to change the connection I get the repo_proxy69 error.
I deleted the connection and when I then select "Tools/Connections" I do not get the error message anymore until I create a new connection the repo_proxy69 appears again.

Anyone came across this problem and knows how to solve this?

[Former Member · Accepted solution]

Are you facing this issue with universes (NOT ALL) based on a specific connection?

Also, please test the behavior on another client machine.

[Former Member · Accepted solution]

I have 2 ODBC connections available for the universes and I have this issue with both connections. I already deleted both connections and when I then go to  "Tools/Connections" I do get the error message (there are no connections defined).

When I add a new connection I immidiately get the error again as soon as I have entered the connection name and selected the data access driver (which take a while to load).

Is it normal that all the data access drivers are greyed out (see below)? When I go in detail and select Microsoft SQL server 2012 that is yello, but the ODBC driver is greyed out again.

I have tried it on another client machine and I have there the same problem.

[Former Member · Accepted solution]

I have found the problem. Besides 4.1 SP2 also Crystal Reports 2013 SP4 was installed. When deleting CR I did not have any problems with importing universes or changing connections in Designer.

I then installed CR2013 SP2 and that works without any issues.

[Former Member]

Hello,

Could you verify whether the BI server and Client are on same Service Pack and Patch level?

Please check SAP KBA for additional reference.

http://service.sap.com/sap/support/notes/2032852

- Mahesh

[Former Member]

Both BI server and Client are on tversion 4.1 SP2 (14.1.2.1121)