UniVerse (Informix) ODBC Connection Problems

[Richard Wraith]

We have a problem with establishing an ODBC connection to our database. It is a VMark UniVerse (now taken over by Informix who have been taken over by IBM) database.

ODBC connections to the database have worked fine for years, and still work fine right now, using MS Excel (via MS Query) as the client.

Doing a comparitive sniff of the TCP/IP data stream between an MS Excel (MS Query) and StarOffice connection suggests that the Windows ODBC client is making the connection to the server OK but that the error is occuring when the list of database tables is being passed on to StarOffice for display.

StarOffice hangs until a Dr Watson error notification is acknowledged and dimissed on the server. The StarOffice client error is then displayed.

We are using the Informix Universe ODBC driver version 3.07.01.6041 on the client and UV ODBC Server version 3.7.1.3 build 3.7.1.6032 on the server.

The database is UniVerse DBMS 9.6.1.3 build 9.6.1.6032

The problem critically affects our ability to adopt StarOffice as a replacement for MS Office throughout our College. Any help that can be provided to resolve this problem will be gratefully received.

----

The error gernerated on the StarOffice client is as follows:

No connection could be established for the URL sdbc:odbc:Entity.

[Ardent][UVODBC][1800877]Error ID: 110 Severity: SEVERE Facility: LINKERR - TCP error

SQL Status: 08501
Error code: 10054

----

The matching error log in Event Viewer on the Windows NT server running Universe is as follows:

7/10/02 10:15:21 Perflib Error None 1008 N/A ADMINISTRATION The Open Procedure for service "universe" in DLL "C:\uv\UV\bin\uvutil.dll" failed. Performance data for this service will not be available. Status code returned is DWORD 0.
7/10/02 10:15:21 Informix UniVerse Error None 1004 N/A ADMINISTRATION UniVerse error: Performance data collector failed to determin First Counter value from UniVerse performance entry in the Registry. Win32 error: 0. The operation completed successfully..
7/10/02 10:15:21 Perflib Error None 1008 N/A ADMINISTRATION The Open Procedure for service "RemoteAccess" in DLL "rasctrs.dll" failed. Performance data for this service will not be available. Status code returned is DWORD 0.
7/10/02 10:15:21 rasctrs Error None 2001 N/A ADMINISTRATION The description for Event ID ( 2001 ) in Source ( rasctrs ) could not be found. It contains the following insertion string(s): .

[Richard Wraith]

Further investigation using the ODBC diagnostic tool called Dr. DeeBee Spy confirms that the problem is occcuring at the point that StarOffice is asking for a table listing. Comparative Dr. DeeBee Spy logs for MS Query and StarOffice can be supplied on request.

ODBC queries to other databases like MS Acess seem to work fine.

Could the problem be in the way StarOffice is asking for table listings? If so is there a way to change this?

[Aarti Sharma]

Hi Richard,

I'm working on your problem , will get back to you as soon as possible.

Aarti

Sun Microsystems

"All responses to questions posed in this News group are given on
an "as is" basis. We believe the solutions or explanations given here are correct, but do not guaranty that responses will be complete."

[Aarti Sharma]

Hi Richard,

After closely examining the information we received about this problem, we assume that these problems are most probably cased by the database server. It is currently not possible to change the the way tables are queried in StarOffice because these queries can be managed by other databases. A modification of this type would mean to change the complete concept of StarOffice.

We have forwarded your question as a feature enhancement request to our Development team so that they can determine if or when this feature can be implemented in a future StarOffice version.