UADriver Troubleshooting

Knowledge Base: UADriver Troubleshooting

The very first step in resolving a UADriver related problem is to use the “Test” tab on the UADriver setup. This feature can be accessed via the ODBC Data Source Administrator by selecting the UniAccess DSN in question.

Problem:
Attempts to use UADriver result in “system error 5”.
Solution:
This is due to permissions problem in the \dll directory in pre-2.10.0004 and 2.11.0001 versions of UADriver. The workaround is to grant appropriate permissions in this folder or to install the latest 10R1 or greater UniAccess ODBC Driver.
Problem:
ASP page returns an “unable to connect to data source” error.
Solution:
The UADriver creates a temporary file in the default temp directory. As a result, the user needs write privileges to this directory. The location of the temp directory can be different depending on whether the DSN is a system or user DSN. For file DSNs, the user needs to be granted write privileges to the directory that contains the file DSN.
Problem:
UADriver settings not saved after a test is performed.
Solution:
The workaround is to save the DSN prior to performing the test. This is corrected beginning with the 9R2 release of the driver (2.09.0001).
Problem:
A CTlib client cannot access Sybase SQL Server after accessing UniAccess. The error generated is:

SQLState – 08001
[INTERSOLVE][ODBC SQL Server driver][SQL Server]ct_connect(); directory service layer; internal directory control layer error; Requested server name not found.

Solution:
Beginning with the 9R1 version of the driver (2.08.000x), set the option ‘Load Open Client Interfaces File’ under the Advanced Tab option of the UADriver setup.
Problem:
The UADriver traces do not get captured when tracing is activated.
Solution:
Verify that the user has change privileges to the directory where the trace is being captured.

Knowledge Base: UADriver Troubleshooting