Problem: @ISQL is hanging when issuing an ‘X’ to cancel results following a select statement in @ISQL against MS SQL Server 2000 sp3a. Note: the ‘C’ command to continue displaying results works. Solution: This is resolved in UniAccess 10R1-3, 10R2-1, 10R3-0 and up.

Read More

Knowledge Base: Transaction Client Issues

Problem: After logging in using @ISQL, the following message is displayed: “CT_CONNECT() network packet layer: internal net library error: specified server name attribute could not be found.” Solution: Verify that the UniAccess Transaction Server environment has been successfully configured in the UniAccess Configuration File. The SERVER configuration statement defines the server to which a client […]

Read More

Knowledge Base: Transaction Client Issues

Problem: When a ISQL logon is issued, the following message is received: “ct_connect(); network packet layer: internal net library error: Specified CT-Library call to ct_connect failed.” Solution: When a user executes ISQL, if the userid check is not bypassed, the userid and server information are immediately validated with the UAUSER and SERVER entries in the […]

Read More

Knowledge Base: Transaction Client Issues

Problem: UniAccess Transaction Client-Library (UACL) program receives “Receive request failed – library error 31” on a ct_results function call. The identical select statement works using ISQL against SQL Server. Solution: UAMM Error 31 is the result of a Network error. You should check the UACS trace file for error information. If the UACS trace file […]

Read More

Knowledge Base: Transaction Client Issues