Problem: UASL transactions communicating with Microsoft SQL Server issuing SQL Statements receive TDS protocol errors (although the SQL statements are processed). Solution: This is resolved in UniAccess 10R1-3, 10R2-1, 10R3-0 and up.

Read More

Knowledge Base: UniAccess Server Issues

Problem: UASL ACOB transactions do not permit the ability for the UASLSTUB and the parameters to be in an RSEG. Solution: This is resolved in UniAccess 10R1-1, 10R2-0, 10R3-0 and up. (This functionality was broken between UniAccess 8R1-0 and 8R2-0.)

Read More

Knowledge Base: UniAccess Server Issues

Problem: If a transaction contingency occurs while a test-and-set lock is locked, any subsequent request for this lock will be queued. Solution: This is resolved in UniAccess 10R1-2, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: UniAccess Server Issues

Problem: A multiple-inital ACOB UASL transaction whose MCB time has expired has the contents of the MCB return code destroyed. Solution: This is resolved in UniAccess 10R1-2, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: UniAccess Server Issues

Problem: There are a number of situations that may result in hung PIDs. The hung PID may initially be identified as a problem connecting additional client applications or as the result of a UACS STATUS keyin. The most common of these situations are: UACS TERM PID,<pid> does not terminate the PID, but it places the […]

Read More

Knowledge Base: UniAccess Server Issues

Problem: A UACS TERM PID, not only does not terminate the PID, but it places the PID in an ERROR state. Solution: The following scenarios can lead to a PID being placed into an ERROR state that will not be automatically resolved: UACS successfully schedules the transaction, but the transaction does not execute. UACS successfully schedules […]

Read More

Knowledge Base: UniAccess Server Issues

Problem: RPCs receive an error when an update is attempted. The UACS trace file indicates the following: “[14] Basic mode CMS call error [cmstor][400000072006]”. Solution: This error indicates invalid message/program options. Check the VALTAB settings for the RPCs, particularly the REC option. If recovery is not configured in the EXEC, make sure this option has […]

Read More

Knowledge Base: UniAccess Server Issues

Problem: RPCs receive an error when an update is attempted. The UACS trace file indicates the following: “[14] Basic mode CMS call error [cmstor][400000072006]”. Solution: This error indicates invalid message/program options. Check the VALTAB settings for the RPCs, particularly the REC option. If recovery is not configured in the EXEC, make sure this option has […]

Read More

Knowledge Base: UniAccess Server Issues

Problem: UniAccess Server-Library transactions may appear to stall until the TDWAITTIME specified in the TDFHEIBLK expires. The apparent stall of the UniAccess Server-Library transaction may cause the client application to indicate that the server has timed out. This has been determined to be caused by modifications to memory handling introduced by the EXEC change 00006-61620-PCR. […]

Read More

Knowledge Base: UniAccess Server Issues