Skip to Content
avatar image
Former Member

BOBJ Client Tools unable initialize connectivities layer after 4.2 SP5 Update

The below error message is returned when trying to login to UDT after updating from 4.1 SP7 to 4.2 SP5. The update completes successfully, no errors noted during the install of the server platform or client tools update packages. New license key successfully updated in CMC. Receiving the error with the UDT, Desktop Intelligence, etc...

[repo_proxy 60] IDataAccess::init : unable to initialize the Connectivities layer : unexpected exception

I feel like I'm probably overlooking a simple configuration or install step?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jan 19, 2018 at 12:26 PM

    If this is happening on a server box where both client tools and BOE server both are installed, then it is not a connectivity issue.
    In which order have you upgraded your BOE server and client tools ?
    Do you see any errors or failures in the setupengine.logs from server and client tool upgrades ?
    If you can login to CMC and BIlaunchpad and run reports there and all services in CMC are green - then your server install is fine and you can try to repair client tools install.

    Add comment
    10|10000 characters needed characters exceeded

    • those KBA's are not exclusive to unix.
      enable high level traces for both connection servers and try to start them - a more detailed connection server logs might show what's wrong.
      try to create new connection servers, see if they start - if yes, delete the original.

      Are you sure the setupengine.log files from server upgrade do not have any relevant errors ?

  • Jan 19, 2018 at 12:53 AM


    Please make sure the network between your server and client is working as below:

    1. This client can ping the server's IP and hostname.

    2. If possible, disable the firewall or make sure all the request ports have been opened.

    3. If clustered, please access one of the CMS servers directly instead of using the cluster name.

    4. If multiple NICs in your BI server, please make sure all the servers are binded to the correct ip address, which can be checked in CMC->Servers->Metrics.

    5. Please try to log into BI Launchpad in this machine.

    If the issue still happens, a wireshark trace is helpful.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I'm receiving the error in a test environment, not clustered, one win server machine with the client tools installed there locally. I am running through the update process again, once complete I'll take a look at the ports, firewall, etc, and update. Thank you.