RP/TUX 6.4, 6.5, 6.51 - Get LIBTUX_CAT:1292 when NT client and server are on different drives
(Doc ID 765120.1)
Last updated on JANUARY 28, 2019
Applies to:Oracle Tuxedo / Tuxedo / 6.4, 6.5x
Information in this document applies to any platform
Error LIBTUX_CAT:1292 File transfer open failed on Windows NT A Tuxedo server running on Windows NT returns a buffer that is larger than the maximum message queue size. The client's tpcall fails with: LIBTUX_CAT:1292: ERROR: File transfer open failed, file=\s57., errno=No such file or directory, Error during request to service, Tperrno = 7 The file transfer does not work if the client and server are on different drives. This problem has been observed in two different scenarios. In the first scenario, the Tuxedo server was booted from the C: drive, where NT was installed. The Tuxedo client was run from a network drive. In the second scenario, the Tuxedo client was run from the C: drive, where NT was installed. The server was booted from the D: drive. The two hard disks(C: and D:) were controlled by separate disk controllers. In both scenarios, the customer got the error LIBTUX_CAT:1292. This error occurred because the temporary file created for the buffer did not have the drive letter(e.g. \tmpfil.1). Therefore, one process created the temporary file on its current drive(say the C: drive), and sent the message to the other process. The receiving process tried to read this file (\tmpfil.1). However, by default, it looked for the file in its own current drive(not the C: drive), and the read failed because the file was not there.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document