Rocket U2 | UniVerse & UniData

 View Only

 Error with U2 ODBC on windows client connecting to UniVerse - IM998/ODB930019

Seth Hudson's profile image
Seth Hudson posted 09-18-2024 02:32

Hi all,

i have a bit of an issue with U2 ODBC trying to connect to uniVerse DB.

I installed (at the then time v530 of client tools (ODBC 64bit) onto a workstation and then i was able to connect to the DB and query.

Since then i have installed ODBC tools onto another workstation/pc/server (both on premise and within Azure) and completed the same setups i did previously but on these they do not work. i keep getting the same error message (as shown at the bottom of this post)

i cannot use the existing workstaiton/PC as that client is not the one i will be completing the connection from when in prod (as it is my workstation used for testing) and also cannot use as unirpc is locked down to specific IP (the new workstation/PC i want to use in Azure). 

With this being said, if i try to install ODBC onto another workstation, same result, doesn't connect.

i am using both the ODBC Tester from the ODBC tools and the Test Connection option from windows (ODBC Data Sources 64-Bit) after creating a user or system DSN.

The uci.config i am using is the same as the original workstation but i also re-created using uci editor and same result with both as i can see that the error relates to invalid config file.

Error from ODBC Test Connection (Windows)

-------------

-------------

 

Error from ODBC Tester (U2 Tools)

-------------

Start:

Failed:ERROR [00000] [Rocket U2][U2ODBC][0302086]Error ID: 46  Severity: ERROR  Facility: DBCAPERR - UCI Error. Func: SQLConnect(); State: IM998; U2 Database code: 0; Msg: [U2][SQL Client]ODB930019.

ERROR [00000] [Rocket U2][U2ODBC][0400182]Connection not open.

Paul Chang's profile image
ROCKETEER Paul Chang

It might be related to one old U2 ODBC client registry key. When using 64-bit U2 ODBC client, it might read the 32-bit U2 ODBC client registry key. You can also install 32-bit U2 ODBC client or upgrade to 5.4.1 client to solve the registry key issue. 

John Jenkins's profile image
John Jenkins

I suspect Paul has it here, but it's still worth remembering that the ODBC driver bitwise sense must match the bitwise sense of the client application. It's also possible to have  both 32-bit and 64-bit versions of client software and drivers on 64-bit Windows - but not vice-versa.

i.e.

  • 32-bit Windows with 32-bit Excel, 32-bit DSN  and 32-bit driver - OK 
  • 64-bit Windows with 32-bit Excel, 32-bit DSN and 32-bit driver - OK
  • 64-bit Windows with 64-bit Excel, 64-bit DSN and 64-bit driver - OK

Regards

JJ