Reflection X 14.x Error Messages

  • 7021804
  • 10-Mar-2008
  • 26-Feb-2019

Environment

Reflection X version 14.x

Situation

This technical note lists Reflection X 14.x error messages and related troubleshooting suggestions.

Resolution

About Reflection X Error List

The status and error messages in Reflection X are listed by number in this technical note. These messages may appear in a Microsoft Windows alert box or in the Reflection X log file. Some Reflection X errors are not listed here either because they are self-explanatory, or because they require assistance from Technical Support.

Error Numbers 0-1000

RX108
Unable to open the filter file '%s'. Reflection X Trace is unable to open the selected output filter file. Make sure that the file is a valid filter file. See product help or KB 7021767 for information on selecting and editing output filter files.
RX112
The number of entries in your hosts database exceeds the maximum allowed. The first %d entries have been used. When the Reflection X Wizard loaded the hosts database file, it truncated the file because the file contained too many host entries. The hosts database file can contain a maximum of 1024 host entries. See product administrator help for information on setting up a host database of clients.
RX113
Could not open text editor ('%s') for '%s'. The <editor> you tried to run is not available. You see the following message if, for example, you choose Edit in the XRDB Settings dialog box, and Windows Notepad.exe is not available:
Could not open text editor ('notepad.exe') for 'c:\Program Files\Attachmate\Reflection\User\Xrdb.txt'
You can specify a different text editor by changing the TextEditor keyword in the Reflection X initialization file.
RX120
Unable to initialize .xie extension. The XIE imaging extension lets the server handle certain kinds of image processing locally (decreasing network traffic and the burden on the host). The XIE extension could not be initialized.
RX255, RX257
This unlicensed time-limited evaluation copy expired on %s. Please contact AttachmateWRQ or your authorized Reflection reseller to update this product. See https://www.attachmate.com/How+To+Buy/.
RX263
The -d option must be followed by a host name. Option ignored. The option for Reflection X in the shortcut Properties dialog box was incorrectly specified and will be ignored. The -d option connects Reflection X to the specified host on startup, with the XDMCP Method set to Direct. For information on command line syntax, see Startup Parameters in the product help.
RX264
Unrecognized option '-%s' ignored. The startup parameter specified on the command line is not valid. Reflection X will ignore the switch and start up anyway. For information on command line syntax, see Startup Parameters in the product help.
RX265
The settings file specified (%s) does not exist. The file name specified by the -s parameter in the Reflection X startup command is invalid. Correct the file name so that it is a valid file name.
RX267
Reflection X has not been installed correctly. Please run Setup to correctly install Reflection X.
RX268
Master configuration file location: '%s'. The master Rx.ini file, located in the indicated directory, is in use. Ask your system administrator to verify that the file is not opened by any other applications on the network.
RX273
Insufficient system resources to start Reflection X. There is not enough available system memory to start Reflection X. Close other applications to free system resources before trying to restart Reflection X.
RX278
Unable to write to initialization file (%s). You may not be able to start X clients, and no configuration changes can be made to Reflection X. Reflection X cannot write to the indicated initialization file. Use the -s parameter in the Reflection X startup command to specify a valid initialization file. For information on command line syntax, see Startup Parameters in the product help. Note: If you see error RX278, RX279, or RX281 when opening an .rxc file, the issue may be fixed in version 14.0 Service Pack 6 (see KB 7021762).
RX279
Your user path (C:\Program Files\Attachmate\Reflection\%PersonalFolder%\Reflection) is invalid. This path, which is specified during installation, must exist and you must be able to write to it. Reflection X cannot find your User directory, which contains your Reflection X user files. You must re-install Reflection X and specify the correct path to the Reflection User directory. Note: If you see error RX278, RX279, or RX281 when opening an .rxc file, the issue may be fixed in version 14.0 Service Pack 6 (see KB 7021762).
RX280
Your user path (%s) is invalid. This path, which is specified during installation, must exist and you must be able to write to it. Reflection X cannot find your User directory, which contains your Reflection X user files. You must re-install Reflection X and specify the correct path to the Reflection User directory.
RX281
The registry key specified (%s) is invalid. Using the 'config' registry key. The registry key that you specified with the -s parameter in the Reflection X startup command is invalid. Reflection X is using the default registry key, config, to obtain initialization settings. Check the spelling of the registry key you specified with -s parameter. Also, make sure that the registry key you specified exists in the registry. Note: If you see error RX278, RX279, or RX281 when opening an .rxc file, the issue may be fixed in version 14.0 Service Pack 6 (see KB 7021762).
RX284
The Registry data for this evaluation version of Reflection X is missing or has been corrupted. You must reinstall Reflection X to continue. The specified registry key may be missing, or you may not have sufficient privileges to read the registry.
RX299
The monitors are configured in negative coordinates format. Reflection X will not work properly. Features like Panning, Remote window manager, Reflection Window manager and Treat windows desktop as XRoot will not function as desired. If you wish to use those features then make primary monitor to be leftmost or uppermost monitor. See KB 7021806.
RX322
Windows GDI resources are running low (only %d%% left). Please close unneeded X clients and other Windows applications. As an alternative to closing unneeded X clients and other Windows applications, you can increase the amount of GDI memory that Reflection X attempts to make available to other Windows applications. For more information, see X Server Resource Usage in the product help.
RX452
The specified host access security file name is invalid. The file does not exist or is invalid. The host access security file, specified in the Security Settings dialog box, is invalid. The keyword for this setting is XHostsPath.
RX453
No host access security file has been specified. Specify a Host access security file in the Security Settings dialog box. The keyword for this setting is XHostsPath.
RX461
You have enabled access control, but the Xhosts file is empty. Only XDMCP clients will be allowed to connect to Reflection X. If you want to allow non-XDMCP clients to connect to Reflection X, you must make the appropriate entries in the Xhosts file or select a Security mode other than Host-based security (Security Settings).
RX500
The specified Base file name is not valid. Make sure that it is a file name (not a directory or folder name), and that you can write to it. Enter a valid file name in the Base file name box (Clipboard Settings).
RX501
You cannot specify a file name extension for Base file name. Extensions are assigned automatically based on file type. Re-enter the Base file name (Clipboard Settings).
RX550
The specified keyboard map file does not exist. Use internal keyboard map? You have specified a file that is not a keyboard map file or that is a keyboard file from an incompatible version of Reflection X. If you click Yes, Reflection X will use an internal keyboard map that is based on the default US keyboard map (Us.kmp). If you click No, you must specify a valid keyboard map file in the Keyboard map box (Keyboard Settings). See the product help for more information on mapping the keyboard.
RX551
The specified keyboard map file is invalid. Use internal keyboard map? You have specified a Keyboard map file that has an invalid format. If you click Yes, Reflection X will use an internal keyboard map that is based on the default US keyboard map (Us.kmp). If you click No, you must specify a valid file in the Keyboard map box (Keyboard Settings). See the product help for more information on mapping the keyboard.
RX557
You have selected the LK250 keyboard type. If you do not have an LK250 keyboard connected to your computer, your computer will probably hang. Do you still wish to choose this keyboard type? Do not use the Lk250.kmp Keyboard map file or select the LK250 keyboard type unless you have an LK250 keyboard. If you try to use this keymap file with another keyboard, you might encounter problems.
RX600
The specified log file name is invalid (make sure that the specified folder exists, and that the file is writable). The Reflection X log file is read-only. In the Log file box (X Server Settings dialog box), specify a path and file name to which you have write access.
RX601
No log file has been specified. In the Log file box (X Server Settings dialog box), specify a path and file name to which you have write access.
RX602
Cannot view a remote logfile. You cannot view a remote log file. Make sure that the UDP connection is specified correctly in the Log file text box (X Server Settings dialog box). Make sure that the syslog daemon is set up correctly on the server and is running.
RX603
The specified log file does not exist. You have specified a log file that does not exist. In the Log file box (X Server Settings), specify a path and file name to which you have write access.
RX608
Using When Mapped as your Backing store setting reduces network traffic, but it also requires more memory than the By Request setting. In X terminology, a window is "mapped" when it is eligible for display on the screen. When Mapped tells the X server (Reflection X) to maintain the contents of obscured regions when the window is mapped. This setting reduces network traffic, but it also requires more memory than the By Request setting. See product help for more information on Backing store (X Server Settings dialog box).
RX609
Using Always as your Backing store setting reduces network traffic, but there are two drawbacks: It requires more memory and not all X clients will behave correctly. Set Backing store to When Mapped if you see a problem. In X terminology, a window is "mapped" when it is eligible for display on the screen. The "Always" setting tells the X server (Reflection X) to always maintain the contents of obscured regions when the window is mapped. This setting reduces network traffic, but it also requires more memory than the other settings. See product help for more information on Backing store (X Server Settings dialog box).
RX700
You must specify a Font path. The font path is specified in the Font Settings dialog box.
RX701
'%s' is an invalid directory. The font path (specified in the Font Settings dialog box) is invalid. Click Fonts on the Settings menu and specify another path.
RX702
You must specify a Font path. There is no entry for the font path box in the Font Settings dialog box.
RX703
The font path contains at least one bad element. For example, a directory in the font path does not contain a fonts.dir file, a Windows font has not been properly added, or a font server is not reachable. The Reflection X Log file may contain additional information.
RX705
'%s' is an invalid temporary font path. The entry for Storage directory for font server fonts in the Font Settings dialog box is invalid. The default location is the Reflection X installation path followed by a final directory node that is composed of your computer's IP address translated into an 8-character hexadecimal string, or your computer's DECnet node address (without periods).
RX707
Unable to find cursor font '%s' in current font path. Edit Font path to include a location that contains this font. The font path box does not include the cursor font requested. In rare cases, you may need an updated video driver (or try the standard Windows driver).
RX711
Unable to set font path to ‘%s’. Please enter a valid font path. See information on error RX703.
RX750
The Keyboard map file '%s' is invalid. Using internal keyboard map. An incorrect or incompatible keyboard file is specified in the Windows registry or the Reflection X initialization file. Reflection X will use an internal keyboard map that is based on the default US keyboard map (Us.kmp).
RX751
Unable to find the Keyboard map file '%s'. Using internal keyboard map. Reflection X cannot find the Keyboard map file and will use an internal keyboard map that is based on the default US keyboard map (Us.kmp).
RX755
There is not enough memory available to convert your custom keymap (.kmp) file for use with this release of Reflection X. Close a few local applications and reset the server. Using internal keyboard map. The internal keyboard map is the one that Reflection X uses by default: The program detects the keyboard driver you are using in Windows (as defined by the International option in the Windows Control Panel) and uses the appropriate keymap.
RX850
No Winsock.dll could be found. Before you restart Reflection X with this setting, make sure Winsock.dll is in your path. Make sure that Winsock.dll is included in your path. To display the path, enter PATH at an MS-DOS prompt. For additional Winsock.dll troubleshooting information, see Windows Sockets Troubleshooting in the product help.
RX851
PATHWORKS Pwsock.dll could not be found. Before you restart Reflection X with this setting, make sure Pwsock.dll is in your path. Make sure that Pwsock.dll is included in your path. To display the path, enter PATH at an MS-DOS prompt. See also DECnet requirements in the product help.
RX852
Invalid syntax for local IP address. Example: 161.207.52.99. IP addresses must consist of four numbers between 0 and 255, separated by periods. For example, 150.215.60.99 is a valid IP address, and 150.2.15.60.99 is not valid.
RX853
Invalid IP address. Each section must be less than 256 and the first section must be greater than 0. IP addresses must consist of four numbers between 0 and 255, separated by periods. For example, 123.123.12.12 is a valid IP address, and 123.123.12 is not valid.
RX854
Invalid IP address. There is no node specified for this class of address. The specified IP address is invalid. Make sure that you have specified the correct IP address.
RX855
Invalid syntax for local DECnet Node ID. Example: 63.1023. A DECnet node ID must consist of two numbers separated by periods. The first number must be in the range 1-63, and the second number must be in the range 1-1023.
RX856
Invalid DECnet node ID (area number). The area portion (first section) must be 1 through 63. A DECnet node ID must consist of two numbers separated by periods. The first number, which is the area number, must be in the range 1-63.
RX857
Invalid DECnet node ID (node number). The node portion (second section) must be 1 through 1023. A DECnet node ID must consist of two numbers separated by periods. The second number, which is the node number, must be in the range 1-1023.
RX865
DECnet interface is not available on this platform. Install PATHWORKS on your computer, or select another network transport (Enable TCP/IP) in the Network Settings dialog box. For information on PATHWORKS versions, see the product help.
RX866
Winsock interface is not available on this platform. The TCP/IP (Winsock) transport is selected in the Network Settings dialog box, but Winsock is not installed or available on your computer. Select another network transport (Enable DECnet listening socket), or see the product help for Winsock.dll troubleshooting information.
RX867
PATHWORKS Dnetw.dll could not be found. Before you restart Reflection X with this setting, make sure Dnetw.dll is in your path. Make sure that Dnew.dll is included in your path. To display the path, enter PATH at an MS-DOS prompt.
RX872
PATHWORKS Pwsock32.dll could not be found. Before you restart Reflection X with this setting, make sure Pwsock32.dll is in your path. Make sure that Pwsock32.dll is included in your path. To display the path, enter PATH at an MS-DOS prompt.
RX873
PATHWORKS Nmapi32.dll could not be found. Before you restart Reflection X with this setting, make sure Nmapi32.dll is in your path. Make sure that Nmapi32.dll is included in your path. To display the path, enter PATH at an MS-DOS prompt.
RX874
Serial loopback interface is not available on this platform. Serial support in Reflection X is available only on Intel machines.
RX908
Unable to open processed output file '%s'. You are trying to view a processed output file that does not exist. Make sure that the correct path and file name are specified in the Processed output file box (Reflection X Trace dialog box).
RX911
The range for the client number or the event number is invalid. They must be numeric. Filter will not be saved. You must enter non-negative numeric values for the By client number and By event range options (Trace Output Filter Settings dialog box).
RX912
The range for the client number or the event number is invalid. The FROM values must be less than or equal to the TO values. Filter will not be saved. Make sure that the From (first) value specified in By client number and By event range is less than the To value (Trace Output Filter Settings dialog box).
RX913
The window you have selected cannot be traced because it is not an X client window. Would you like to select another window? You can perform a trace only on an X client window. Select an X client window for the trace.
RX914
Unable to start the replay process: Replay.exe may not be installed. The file Replay.exe is either not installed on this PC or cannot be found by Reflection X. Typically, the Replay... and Text Output... buttons will be disabled under this condition. To correct this, install the Replay feature using Add/Remove Programs or see your system administrator for more information.
RX915
Cannot write to or create trace file '%s'. Enter a different file name. If you attempted to start a trace, make sure that the correct path is specified in the Trace file box (Reflection X Trace dialog box). If you attempted to process a trace, make sure that the correct path is specified in the Processed output file box.

Error Numbers 1000-1999

RX1108
This unlicensed time-limited evaluation copy will be inoperable in %d days on %s. Contact Attachmate Sales or an authorized partner.
RX1109
This software is an unlicensed time-limited evaluation copy. Once installed, it will function for %d days and then become inoperable. The evaluation period will end in %d days on %s. Contact Attachmate Sales or an authorized partner.
RX1130
The following modified setting(s) will not take effect until Reflection X is reset: This message appears after you have made one or more changes that require Reflection X to be reset before they take effect. A reset closes any clients that are running. If you do not reset Reflection X right away, your changes are recorded, but they will not be in effect until you reset or restart Reflection X.
RX1131
Reflection X must be restarted for the following modified setting(s) to take effect: For some settings changes to take effect, Reflection X must be shut down and restarted. This message indicates that one or more of these changes has been made.
If you close the server now, your clients will be closed. If you do not close the server, your changes are recorded, but they will not be in effect until you restart Reflection X.
For more information about closing Reflection X, see the Control Menu topic in product help.

RX1150
For an XDMCP connection, the Direct and Indirect methods require a host name or IP address. In the Host name option (Reflection X Manager), either select a host from the list, or specify the name or IP address of the X client host machine.
RX1201
There are X clients running. Closing Reflection X will close all clients. Are you sure you want to close? You may want to close clients individually before closing or resetting Reflection X.
RX1207
Client %d closed because of a failed network read operation. See the log file for details. Problem may be caused by a firewall.
RX1300
A client's attempt to connect to Reflection X was refused for this reason: %s. One of the most common situations in which this error message appears is one where you have selected Host-based security in the Security settings, and then tried to connect to a host that is not in the xhosts file.
RX1304
Client %d: Error (%s) in %s request. Indicates that the server responded to the client's request with an error, which was written to the Log file (specified in X Server Settings).
RX1411
Windows Clipboard is currently in use. Unable to open Clipboard. Another Windows application is using the Windows Clipboard. Shut down that application so that Reflection X can open the Windows Clipboard.
RX1412
Insufficient memory for selection conversion. There is not enough available system memory to copy a graphics selection from an X client to the Windows Clipboard. Close other applications to free system resources.
RX1413
Insufficient memory to print selection. There is not enough available system memory to print your selection. Close other applications to free system resources before trying to print.
RX1414
Insufficient memory to write graphics selection to file. There is not enough available system memory to save your graphics selection to a file. Close other applications to free system resources before trying to save your graphics selection.
RX1420
Could not convert selection to Windows format. This message indicates that Reflection X could not convert the requested font to a Windows font. Log the font activity (Font Settings dialog box) to determine the required font.
RX1421
%s is specified as the Client encoding method, but the incoming string probably contains %s. You have probably selected the wrong Client encoding method (DBCS Settings). If you are attempting to display Kanji characters, try selecting Detect client Kanji encoding method (DBCS Settings).
RX1422
Operation will continue with %s as the Encoding Method. Because the Detect client Kanji encoding method (DBCS Settings) is selected, Reflection X is automatically converting double-byte Kanji characters to the correct encoding method when a client receives them.
RX1423
If the Kanji strings appear to be incorrect when pasting, please change to the correct Client encoding method setting. You have selected the wrong Client encoding method (DBCS Settings).
RX1424
If you continue to operate with this setting, there is a danger of system failure. Please change to the correct Client encoding method setting. Reflection X could not detect what encoding method the X client is using. Reflection X will make an attempt to decode the text received from the client. Change the client encoding method (DBCS Settings).
RX1425
Unable to copy selection: the rectangle selected is empty. You started to make a rectangular selection (the cursor became a crosshair), but you released the mouse button before a rectangle could be formed. For more information, see Copy Rectangle in the product help.
RX1471
Ambiguous (EUC or Shift JIS). The text received from the X client does not contain enough information to distinguish between the EUC or Shift JIS encoding methods. The encoding method used by the client, however, is one of these two encoding methods. If Reflection X is not decoding the client text properly, try the other encoding method (DBCS Settings).
RX1475
Warning: Could not match Local XRDB Resource entry: %s. You can specify a client encoding method on a per client or per host basis in the Local X resource file. Use this syntax:
RXServer.<host>.<client_class>.<registry_var>: <value>
This error message is displayed if the syntax you've used is incorrect. See the product help for some sample entries.
RX1476
Using Local XRDB Resource to change registry variables. Reflection X is using the Local X resource file to change values in the registry.
RX1506
The specified RGB color file name is invalid. Use built-in version? The RGB color file is missing from the Reflection X User directory (it may have been moved, or the file may be corrupted). The server can use a built-in color name database, but this should be a temporary fix. A valid color file is preferred because the built-in database cannot be edited. Check the RGB color file name in the Color Settings dialog box. To get a new Rgb.txt, re-install Reflection X.
RX1550
This PCF font file does not have a standard version number and cannot be read by Reflection X or compiled into FON format. This PCF (Portable Compiled Format) font file cannot be read by the X server. If you are transferring the font using the FTP Client, set the transfer method to binary.
RX1551
This PCF font file does not have a standard format and cannot be read by Reflection X or compiled into FON format. This PCF (Portable Compiled Format) font file cannot be read by the X server. If you are transferring the font using the FTP Client, set the transfer method to binary.
RX1552
Could not read font properties; make sure that this PCF font file is not in ASCII format. This PCF (Portable Compiled Format) font file cannot be read by the X server. If you are transferring the font using the FTP Client, set the transfer method to binary.
RX1701
Processing Error: cannot open the file '%s'. Reflection X cannot open the trace file specified in the Trace file box (Reflection X Trace dialog box). Ensure that the path and file name are correct.
RX1703
Translation error: input file format error in file '%s'. Be sure to turn off tracing before attempting to process the output file. You may need to perform the trace again.
RX1710
Unable to write to processed output file '%s'. Reflection X cannot write the processed trace file to the file specified in the Processed output file box (Reflection X Trace dialog box). Ensure that the path and file name for the output file are correct.
RX1800
Failed to run '%s'. Windows internal error # %i. The client startup portion of Reflection X (Rxstart.exe) cannot be executed because of a Windows problem. Close other applications and try again.
RX1801
Not enough memory to start client. There is not enough available system memory to start the X client. Close other applications to free system resources before trying to restart the client.
RX1802
Could not find the client startup executable '%s'. Reflection X could not find the executable file specified in the Command box (Reflection X Manager, Connection Settings). Check the name of the file and make sure that it is available on the host.
RX1803
The transport required for starting this client is not enabled. Enable the appropriate transport (click Network on the Reflection X Settings menu). Select the appropriate network transport for the client in the Network Settings dialog box. Depending on which transports are enabled for your PC, you can select Enable DECnet listening socket.
RX1804
The file '%s' does not exist. Removing entry from history list. The client file you selected from the File menu has been deleted, renamed, or moved to a new location. Reflection X will remove the name from the File menu history list.
RX1805
The file '%s' does not exist. Unable to edit file. You cannot edit the selected client file because it does not exist.
RX1900
Reflection X is unable to load Rcom.dll. Rcom.dll is a file provided with Reflection for Windows. Reflection X needs to make use of this file to establish a local connection. This message indicates that Rcom.dll is missing or corrupt.
RX1901
Incorrect version of R1win, R2win, or R4win.exe. The version of Reflection for Windows specified in the .EXE box (shown under Connection Settings when you're configuring a local connection) is incorrect.
If you have a newer version installed, change the .EXE file setting. Otherwise, install Reflection for UNIX and OpenVMS (a component of Reflection X) in Add/Remove Programs.

RX1950 - RX1955
Reflection Xpress is no longer supported for serial connections. Instead, use Low Bandwidth X over TCP/IP (with Windows dial-up networking, which supports PPP or SLIP). See also Technical Note 1104.

Error Numbers 2000-2999

RX2000
Server shutting down by user request. This is typically a follow-up error that you see after an initial error that causes Reflection X to terminate. If you can solve the problem generating the earlier error, this later error will not occur.
RX2059
Excessive server resets. An XDMCP connection has been established, but the client cannot run. Check the log file for errors. Do you want to end this XDMCP session? This message occurs when XDM keeps trying to start a client that won't stay running. Click Yes to interrupt this process, or click No to keep trying.
RX2100
XDM: %s, declaring session dead. The XDMCP session with the host was disrupted. Try to connect to an XDMCP host again. If you are using the direct or indirect method, you may want to specify a new host in the Host name box (Connection Settings).
RX2101
UDP set broadcast socket-option failed. If you are using HP ARPA Services for DOS, there are two lines in your Protocol.ini file regarding UDP packets. Comment these lines out and you will no longer see this message.
RX2102
Your XDMCP connection timed out. See KB 7021671.
RX2103
Your XDMCP connection has terminated. The host to which you were connected is no longer responding. It may have gone down, or it may not be on the network. See KB 7021671.
RX2104
Unable to access the specified XDMCP host. Verify your host IP address in the Connection Settings area of the Reflection X window. See KB 7021671.
RX2106
XDMCP UDP socket creation failed. Refer to your network documentation to increase the number of UDP sessions. XDMCP uses UDP (user datagram protocol) packets; if you are running a third-party DOS-based TCP/IP stack, it may need to be configured to increase the UDP sockets. Refer to your TCP/IP software documentation.
RX2107
XDMCP UDP socket cannot bind. A previous XDMCP session is running and needs to be closed before continuing.
RX2108
XDM host on strange network. You are trying to connect to an XDMCP host over a non-TCP/IP network. You can connect to an XDMCP host only over TCP/IP. Select Enable TCP/IP in the Network Settings dialog box.
RX2109
The specified XDM host is unwilling to manage. The host is currently unable to support XDMCP.
RX2110
XDM authentication failure (%s). Reflection X has been denied access because you do not have appropriate permissions on the host.
RX2111
XDM session declined by host (%s). The host is currently unable to support XDMCP.
If you are using HP ARPA Services for DOS, there are two lines in your Protocol.ini file regarding UDP packets: Comment these lines out and you will no longer see this message.

RX2112
XDM session to host failed: Cannot open display. See KB 7021671.
RX2151
The Reflection X Manager has been disabled; single-click the Reflection X icon to get to the menu. Your system administrator has disabled the Reflection X window. To access the Reflection X Control menu, single-click the Reflection X icon.
RX2152
The Reflection X Settings dialog box has been disabled. Your system administrator has disabled the Reflection X Settings dialog box. You cannot change any of the settings for the Reflection X server.
RX2153
The Reflection X Trace dialog box has been disabled. Your system administrator has disabled the Reflection X Trace dialog box. You cannot run a trace.
RX2154
There are X clients running. Resetting Reflection X will close all clients. Are you sure you want to reset? For information on when a reset occurs, and what effect the Disable server reset setting has, see Resetting the X Server in product help.
RX2157
XDMCP is being disabled. There is currently no TCP/IP support. Reflection X is disabling XDMCP because there is currently no TCP/IP support. To enable XDMCP, select Enable TCP/IP in the Network Settings dialog box and restart Reflection X.
RX2159
There are X clients running. Starting an XDMCP connection will close all clients and reset the server. Are you sure you want to start XDMCP? For information on when a reset occurs, and what effect the Disable server reset setting has, see Resetting the X Server in product help.
RX2160
A system change has occurred. Unless you reset the server, the appearance of X clients will be affected. Reflection X must reset or restart after certain settings changes, such as a larger or smaller desktop work area or a change to color depth settings. Even locking or unlocking the Windows system taskbar may slightly re-size the desktop area. Unless you reset the server, the appearance of your X client applications and features such as panning may be affected.
If you are frequently seeing this error, do one of the following:
- Try changing your Windows Taskbar Properties (such as locking or auto-hide) and/or Windows Display Properties (on the Appearance tab, change Windows XP style to Windows Classic style).
- If you are using version 14.0, update to Service Pack 4 or higher. This update includes an option to suppress further warnings during your session, and a new Display setting “Ignore Windows taskbar.” For more information, see KB 7021762
.
RX2162
A system change has occurred. Unless you restart the server, the appearance of X Clients will be adversely affected and the GLX extension won't function properly. Note that you must restart the server as opposed to resetting it. Reflection X must reset or restart after certain settings changes, such as a larger or smaller desktop work area or a change to color depth settings. Even locking or unlocking the Windows system taskbar may slightly re-size the desktop area. Unless you reset the server, the appearance of your X client applications and features such as panning may be affected.
If you are frequently seeing this error, do one of the following:
- Try changing your Windows Taskbar Properties (such as locking or auto-hide) and/or Windows Display Properties (on the Appearance tab, change Windows XP style to Windows Classic style).
- If you are using version 14.0, update to Service Pack 4 or higher. This update includes an option to suppress further warnings during your session, and a new Display setting “Ignore Windows taskbar.” For more information, see KB 7021762
.
RX2443
Connection refused. The host may be down or non-existent, or it may not allow the connection method you specified. Try a different connection method or a different host. If you are using version 14.0 over a slow connection or VPN, install Service Pack 1 or higher and increase timeouts (see “Problems with slow connections or connecting over VPNs” in KB 7021762).
RX2455
No more transport sessions are available. You may see this message upon starting or resetting Reflection X if it is unable to obtain a listening socket from your network software. Make sure your network software is available and is configured properly. A quick test would be to try making a connection over the same transport from another application.
You may also see this error if you try to exceed the number of sockets supported by your network software or by Reflection X. You may be able to reconfigure your network software to support more sockets; Reflection X supports up to 128 sockets.

RX2488, RX2489, RX2490
Socket error. Click Tools > Log File to view the log file. Look for the socket error message, which may help you determine what the problem is. If there is a socket error but no explanatory message, the error identifies a vendor-specific networking software problem.
RX2755
Client %2d: did not find font '%s' When an X client requests a font that isn't found, and when the Log font activity check box is selected in the Font Settings dialog box, this message is written to the log file. "Windows font used" is added if the registry entry for using the closest Windows font is set.
RX2758
<...> found font in font cache. An X client found a font in the Storage directory for font server fonts.
RX2762
No font name specified; returning error. An X client did not specify a valid font name, so Reflection X returned an error message to the client. Log the font activity (Font Settings dialog box) and supply the log information to the developer of the X client application.
RX2763
Could not find Reflection X '%s' font in Windows font table. When Reflection X uses a Windows format (.fon) font, the font is added to the Windows font table. You can view this table by double-clicking the Fonts icon in Windows Control Panel. You might also see this error if another application has already added a font with the same file name to the Windows font table. Reflection X will be unable to open that font (because it requires .fon fonts to be in a Reflection X-specific format). This is particularly likely to happen if you run another PC X server before you run Reflection X, because that X server will also use the standard fonts used in the X Window System (such as Fixed.pcf). To solve the problem, go to the Fonts category of Windows Control Panel and delete the font specified in the error message.
RX2764
Could not connect to font server specified (%s). To satisfy a font request made by an X client, Reflection X attempted to retrieve the font from a font server. Reflection X could not connect to at least one of the font servers specified in the Font path box. Typically Reflection X Manager will reattempt a font server connection if all information for the font server is correct.
Make sure that the font server(s) are specified correctly in the font path and that the specified font servers are running and are available on the network. Font servers are available only when TCP is active.

RX2800
Correct syntax is '<filename> <XLFD name>'; offending line was '%s'. Each font directory contains a file called Fonts.dir that serves as a database for the X server of the fonts contained in the font directory. Each entry in the directory file contains the name of the file containing a font, and the font's full name. This full name is usually an X Logical Font Description (XLFD). The following line is an example of an entry in Fonts.dir:
timb12.pcf -Adobe-Times-Bold-R-Normal—12-120-75-75-P-67-ISO8859-1
Correct the syntax of the offending line indicated in the error message. To update the fonts database, click Directory > Build Fonts.dir.
RX2801
Unable to add font file '%s'. Can't add a font to the Fonts.dir file. Check the permissions for the file and make sure that the file is not locked by another application.
RX2802
Invalid font directory file syntax in file '%s' at line %d. Each font directory contains a file called Fonts.dir that serves as a database for the X server of the fonts contained in the font directory. To update the fonts database, click Directory > Build Fonts.dir.
RX2803
Invalid font alias file syntax in file '%s' at line %d. A font directory may contain a fonts alias file called Fonts.ali that allows you to specify an alias for a FON font. Correct the syntax of the indicated line in the Fonts.ali file. For information on Fonts.ali, see the product help.
RX2804
Missing Fonts.dir in directory '%s'. Each font directory contains a file called Fonts.dir that serves as a database for the X server of the fonts contained in the font directory. To update the fonts database, click Directory > Build Fonts.dir.
RX2810
Fonts.dir file has no entries. Each font directory contains a file called Fonts.dir that serves as a database for the X server of the fonts contained in the font directory. To update the fonts database, click Directory > Build Fonts.dir.

Error Numbers 3000-3999

RX3300
Unable to obtain local DECnet node ID. Make sure your node is listed in the static portion of the DECnet node database. Make sure the host/node is listed in the static portion of the DECnet node database. This can be done by running the PATHWORKS Ncp.exe program and using this command:
DEFINE NODE <node-id> NAME <node-name>
RX3301
%s host (%s) in XHOSTS file could not be resolved. This host will not have access to the X server. Reflection X could not resolve a host name (listed in the Xhosts file) to an IP address. Make sure that the host name is correctly spelled in the file. Make sure that the Domain Name Resolution settings for your computer are correct. Make sure that the domain name server is running and is available on the network.
RX3302
None of the hosts in the Xhosts file are valid. The Xhosts file does not contain any valid entries. If Host-based security (Security Settings) is selected, only XDMCP connections are allowed.
RX3303
%s is currently not available, but your Xhosts file contained %s hosts. An X client application disabled access to the specified host.
RX3304
Unable to get your computer's Internet address from your TCP/IP hosts file. Add your computer's IP address to your local TCP/IP hosts file. Alternatively, clear the Autodetect network interface check box in the Network Settings dialog box and enter the correct IP address in the text box below it.
RX3305
The XDMCP broadcast address (%s), specified in the Reflection X initialization file, has an invalid format. Reflection X will use the default address.
RX3400
Unable to create a TCP socket. Verify that your TCP/IP network software is loaded and is in your path. Also, check the name of the TCP/IP software shown in the About box.
RX3401
Unable to bind to a TCP socket. This message will appear if you have turned off Autodetect network interface and you have specified an incorrect IP address for your local machine. It will also appear if have disabled your TCP interfaces on your local machine but still have the stack installed and TCP enabled in Reflection X.
RX3404
Unable to listen on a TCP socket. If your computer has multiple interfaces, turning off Autodetect network interface and manually supplying the correct IP may solve this problem.
RX3405
Cannot establish any listening sockets. Check your Windows Sockets file (Wsock32.dll or Winsock.dll): It must be the one your network software vendor provided, it must be in your path, and there must not be more than one copy.
Reflection X cannot open sockets to allow for connections over any of the enabled transports. This message can be caused by a variety of problems. When you click OK, the Network Settings dialog box opens. See the product help for suggestions.
RX3406
Cannot bind to the X server's address. If another X server is already running, close it. Otherwise, reload your TCP stack. The memory address needed by Reflection X is not available. You may get this message if another X server is running on your computer. If so, close the other server before you start Reflection X. The message may also appear if there is a problem with your TCP/IP networking software.
RX3408
Unable to create a DECnet socket. Please verify that your DECnet network software is loaded and is in your path. Verify that your DECnet network software is loaded and is in your path. For more information regarding support for DECnet in Reflection X, see the product help.
RX3409
Error binding DECnet socket. An application could still be bound to the socket. Try restarting Reflection X. If this does not solve the problem, try rebooting your computer. If this does not solve the problem, look for another network application that might be bound to the socket. If you find such an application, shut it down.
RX3413
Client could not successfully authenticate itself to Reflection X server. Would you like Reflection X to connect this client as an UNTRUSTED client? This X client cannot be run as a trusted client. The setting for If Client Cannot Be Authorized (in the Security Settings) determines how untrusted clients are handled under host- or user-based security (allow, prompt, or refuse).
RX3500
Could not open RGB color file '%s'. Using built-in version. The RGB color file is missing from the Reflection X User directory (it may have been moved or the file may be corrupted). Reflection X will use a built-in color name database. This should be a temporary fix: A valid color file is preferred because the built-in database cannot be edited.
Check the RGB color file in the Color Settings dialog box. To get a new Rgb.txt, re-install Reflection X.

RX3501
Could not allocate buffer for RGB color file '%s'. You do not have enough memory for Reflection X to read your Rgb.txt file (the color name database). Free up Windows memory (for example, by closing other applications) and try again.

Error Numbers 4000-4999

RX4002
Could not find Xkmap.fon. Some characters on keyboard remapping dialog may display incorrectly. Xkmap.fon is a font file used to create the characters that appear in the Keyboard Remapping dialog box. If this font is missing or corrupted, you can restore it by re-installing Reflection X.
RX4450
%s transport is initialized via %s. Reflection X initialized the indicated transport software (TCP/IP or DECnet).
RX4452
No transport (TCP/IP, DECnet, or UNIX domain sockets) is enabled in the Network Settings dialog box. To start a client, you must have at least one transport (TCP/IP or DECnet) enabled in the Network Settings dialog box.
RX4527
You have not saved your modified keyboard map to a file. These changes are in effect now, but will be lost if you exit or reset Reflection X. Save keyboard map to a file now? Changes to the Keyboard Remapping dialog box take effect immediately, but in order to preserve them from one Reflection X session to another, you must save the changes to a keymap (.kmp) file. You can switch between this file and other keymap files by changing the Keyboard map in the Keyboard Settings dialog box. A .kmp file can also be distributed to other users.
RX4528
You are attempting to reset your Alt Gr key. If you reset this key, you will not have access to mappings 3 and 4 in your keyboard map. Reset this key to its default? The key Alt Gr is used in non-U.S., non-Japanese keyboards. Keysyms 3 and 4 (Alt Gr and Shift+Alt Gr) are only available if there is a key mapped to Alt Gr (the X Window System Mode_Switch keysym). For more information, see the product help (keyboard mapping, selecting a PC key).
RX4551
Could not find default keyboard map file '%s'. Using internal keyboard map for defaults. By default, Reflection X detects the keyboard driver you are using in Windows (as defined by the International option in Windows Control Panel) and uses the appropriate keymap. If no keymap is specified, or if the specified file can't be located, Reflection X uses an internal keyboard map that is based on the default US keyboard map (Us.kmp).
RX4557
Character not found. The character that you typed in the Search box in the Keyboard Remapping dialog box was not found in the character sets currently available. You can add a character set provided by a vendor by copying a header file to your Reflection X user subdirectory and adding its name to the Vendor.lst text file.
RX4560
WARNING Although X will allow keysyms 5-8 to be mapped, there is no protocol to access these mappings. Do you still wish to map keysyms 5-8? The X Window System supports mapping for only four characters per key. It is possible to map four additional characters (keysyms 5 - 8), but this is only useful if you are using X clients that support these additional shift states. For more information, see the product help (keyboard mapping, selecting a PC key).
RX4561
You have not chosen a valid Alt Gr key. To use the third and fourth mappings, you must map a key to Mode_Switch, and assign a modifier (Mod1-Mod5) to it. Use that key as Alt Gr. In the X Window System, you can map up to four characters to each key. To map the third and fourth character (using a key in combination with Alt Gr and Shift+Alt Gr), you must have a key on your keyboard that serves as an Alt Gr key - it must be mapped to the Mode_Switch keysym, and it must be defined as one of the modifier keys in the range Mod1 through Mod5.
RX4562
All modifiers (Mod1-Mod5) are in use. Select a modifier (Mod1-Mod5) for Mode_Switch and assign it to the Alt Gr key in order to have access to mappings 3 and 4. In order to use a key as Alt Gr, that key must be defined as one of the modifier keys in the range Mod1 through Mod5. This message indicates that all these modifiers have already been mapped; you must remap one of them to the key you want to use as the Alt Gr key.
RX4800
Unable to auto increment file '%s'; using '%s' for output. Reflection X was unable to copy the text or graphics selection to the indicated file. The file name was supposed to be autoincremented from the Base file name specified in the X and Windows Clipboard Settings.
RX4802
There is no destination specified for the selection you just made. Select one or more Default destinations (Clipboard, Printer, and/or File) in the X and Windows Clipboard Settings dialog box.

Error Numbers 5000-5999

RX5003
Missing user prompt in '%s'. The indicated client (.rxc) file is missing a user prompt. For more information on client files and interactive login prompts, see the product help.
RX5010
Connecting to %s... Reflection X is attempting to connect to the indicated X client.
RX5011
Connection reset by host. You may not have sufficient privileges for the attempted operation. Contact your system administrator to verify your privileges.
RX5030
DECnet is unavailable. Please verify that your network software is loaded and is in your path. Verify that the DECnet network software is loaded and in your path. To display the path, enter PATH at an MS-DOS prompt.
RX5031
Unable to resolve host name. Make sure the host/node is listed in the static portion of the DECnet node database. This can be done by running the PATHWORKS Ncp.exe program and using the command DEFINE NODE <node-id> NAME <node-name>.
RX5032
Unable to create a DECnet socket. Please verify that your DECnet software Mdecnet.exe is loaded. Verify that your DECnet network software is loaded and is in your path. For more information regarding support for DECnet in Reflection X, see the product help.
RX5035
Unable to resolve host name. You may need to add the host's name and address to the local hosts file or node database. If you are using TCP/IP, you may need to add the host name and IP address to your local hosts file. If you are using DECnet as a transport, make sure the host and node are listed in the static portion of the DECnet node database. This can be done by running the PATHWORKS Ncp.exe program and using this command:
DEFINE NODE <node-id> NAME <node-name>
RX5036
The network settings are configured so that DECnet support is not enabled. You are trying to use a DECnet client startup method when DECnet is not available as a transport. Be sure the Enable DECnet listening socket option is selected in the Network Settings dialog box.
RX5038
Invalid login. Typically indicates that the host is not configured to accept an REXEC login. Invalid login. Typically occurs when you're using REXEC as your connection method and indicates that the host is not configured to pass the username and password to the client, as required under REXEC. See the man page for REXEC on your host for more information.
If your login has worked in the past and stops working suddenly, it may simply be a matter of your network administrator making changes on your network. Try rebooting the PC.

RX5043
Unable to expand %s macro because command would become too long. When the %IP% or %DN% parameter is replaced by your IP address or DECnet node number, the Command in the Reflection X Connection Settings exceeds the limitations of the host system. Edit the Command so that it is shorter.
RX5044
Unable to expand %s macro because local computer name and address could not be resolved. Add your computer's name and address to the local hosts file. If you are using TCP/IP, you may need to add your computer's IP address and name to your local hosts file. You can also clear the Autodetect network interface option in the Network Settings dialog box and type your computer's IP address there.
RX5045
Unable to expand %s macro because local computer name and address could not be resolved. Add your computer name and address to the local hosts file or node database. If you are using TCP/IP, you may need to add your computer's IP address and name to your local hosts file. You can also clear the Autodetect network interface option in the Network Settings dialog box and type your computer's IP address there.
If you are using DECnet, you may need to add your computer's node number to the static portion of the DECnet node database (in PATHWORKS 4.x, this database is called Decnode.dat; in version 5.0, it is called Pwnode.dat). Run the PATHWORKS Ncp.exe program at the DOS prompt, and enter the following command:
DEFINE NODE <your node id> NAME <your node name>
You can also turn off Autodetect local node ID in the Network Settings dialog box and type your computer's node ID there.
RX5046
Unable to expand %s macro: could not resolve your computer's node. Your node must be listed in the static portion of the DECnet node database. Run PATHWORKS Ncp.exe and use DEFINE NODE <node-id> NAME <node-name>. You may need to add your computer's node number to the static portion of the DECnet node database (in PATHWORKS 4.x, this database is called Decnode.dat; in version 5.0, it is called Pwnode.dat).
You can also turn off Autodetect local node ID in the Network Settings dialog box and type your computer's node ID there.

RX5047
Unable to expand %s RXC string macro because associated transport could not be initialized. Reflection X could not establish an interface with the TCP/IP software.
RX5049
This connection (%s) was dropped. It probably timed out waiting for your response. The connection with the indicated host was dropped. If you have automated your login process with the Advanced Client Settings dialog box, try decreasing the Prompt timeout. If the Prompt timeout setting is too high, the Enter Response dialog box may open at an inappropriate time (for example, if the host has displayed a prompt specified under Prompts, but Reflection X hasn't yet responded to it).
RX5052
PCX$SERVER could not locate the .com or .exe file to execute. Make sure that Pcx$server.com is installed on your host. For more information, see the Reflection X administrator help.
RX5054
The DECnet object PCX$SERVER could not be found to connect to. Make sure that Pcx$server.com is installed on your host. For more information, see the Reflection X administrator help.
RX5056
Unable to open '%s'. File does not exist or is invalid. Reflection X cannot find the specified client file. The file may have been moved, deleted, or corrupted. Create a new client file.
RX5060
TCP/IP is unavailable. Please verify that your TCP/IP network software is loaded and is in your path. Verify that your TCP/IP network software is installed and properly configured. Also, check the name of the TCP/IP software shown in the About box.
RX5061
Unable to resolve host name. Verify that you are using the correct host name. Also verify that your machine is using a name server (such as DNS or NIS). If you're not using a name server, make sure the host is listed in the Hosts file for your TCP/IP software (check for this file in ..\system32\drivers\etc of your Windows directory). The Hosts file is a list that maps recognizable names to Internet addresses, similar to a domain name system. Each Hosts file entry associates a host name, and optional host name aliases, with the IP address of a host system. When you connect to a host, you can use its host name, or an alias, instead of specifying an IP address.
If you have no domain name server on the local network and you don't use a Hosts file, you must specify the full IP address when you start a host session.
On a PC running Windows, the Hosts file must be located in the \Windows\System32\Drivers\Etc folder. Note that this folder is not normally added to any path.

RX5062
Unable to create a TCP socket. Please verify that your TCP/IP network software is loaded and is in your path. Verify that your TCP/IP network software is installed and properly configured. Also, check the name of the TCP/IP software shown in the About box.
RX5076
Connection closed by host. Ask the host administrator to verify that you have the correct privileges on the host.
Make sure that the client startup command in the Command box is correct. For example, make sure that a closing parenthesis is not missing. You may have to specify the complete path to the X client in the client startup command.

RX5079
Validating %s... The client starter is validating the indicated client file before trying to use the file. If this message is displayed long enough to be read, the client starter is requesting the address of the host from the domain name server.
RX5086
The file '%s' is incomplete. Starting editor view. The indicated client file does not contain all the information needed to start an X client. Enter the needed parameter values in the client file.
RX5087
A command is required for a client connection. A client command file requires a valid client startup command.
RX5098
The folder specified (%s) is invalid (the file must be writable). If you see an error message when you try to create a shortcut for an X client file, it’s likely that you do not have sufficient NT File System (NTFS) privileges to write to the folder specified in the Shortcut dialog box.
RX5100
Invalid login for RSH. Local user name ('%s'), Remote user name ('%s'). The attempt to connect to the host failed because of an invalid RSH login or the host does not have an RSH daemon installed. For more information on RSH method, see the product help.
RX5104
The ('%s') connection method is not enabled. The attempt to connect to the host failed because the connection method has been profiled out and cannot be used.
RX5115
The connection file could not be run for the following reason: %s. Edit the file to correct the problem. To edit the file, select the file in the connection list on the left side of the Reflection X Manager. Then, edit the Connection Settings displayed on the right side of the window.
RX5116
The connection file could not be saved for the following reason: %s. Edit the file to correct the problem. To edit the file, select the file in the connection list on the left side of the Reflection X Manager. Then, edit the Connection Settings displayed on the right side of the window.
RX5119
User aborted connection. The user aborted the connection with the host.
RX5120
Reflection X Connection. Reflection X has connected with the host.
RX5130
Could not find the Reflection X Client Wizard executable '%s'. The Reflection X Client Wizard (Rxwizard.exe) is normally located in the Reflection User directory. If Rxwizard.exe is not in this directory, move it there, restore it to the directory from back-up, or re-install Reflection X. Also, make sure that the Reflection directory is in your path. To display the path, enter PATH at an MS-DOS prompt.
RX5131
Not enough memory to start Reflection X Client Wizard. The Reflection X Client Wizard (Rxwizard.exe) cannot be executed because there is not enough available memory. Close X clients and/or other Windows applications and try again.
RX5132
Failed to run '%s'. Windows internal error # %i. The Reflection X Client Wizard (Rxwizard.exe) cannot be executed because of a Windows problem. Close other applications and try again.
RX5134
Could not find the Reflection X Virtual Desktop executable '%s'. To install this application, open the Control Panel and run Add/Remove Programs. See also KB 7021685.
RX5135
Not enough memory to start Reflection X Virtual Desktop. The Reflection Virtual Desktop (Rvd.exe) cannot be executed because there is not enough available memory. Close X clients and/or other Windows applications and try again. See also KB 7021685.
RX5136
Failed to run '%s'. Windows internal error # %i. The Reflection Virtual Desktop (Rvd.exe) cannot be executed because of a Windows problem. Close other applications and try again. See KB 7021685.
RX5167
Telnet is unavailable. Please verify that Rntelnx.dll is installed and is in your path. If you are running version 13.0, either install the Reflection for UNIX and OpenVMS component, apply Service Pack 1 (version 13.0.1) or higher, or upgrade to a later version.
RX5168
Reflection Kerberos has not been properly configured. Please redo user configuration. Kerberos is an authentication protocol that provides a highly reliable means of verifying that users are who they claim to be. With Kerberos, the administrator can assure authentication of Telnet connections (used to start X clients) between Reflection X and a network host. Reflection Kerberos must be installed to use Kerberos.
RX5169
Could not connect to host. There are numerous reasons that this error message could appear. Make sure you are using the correct host name, and you are able to ping or establish a Telnet connection to the host.
RX5173
Could not connect to host with Secure Shell. Enable the Reflection Host Response dialog box to see the connection log. Unable to complete the OpenSSH connection. Select the Host Response command (View > Host Response) and attempt the connection again. A log will now be created that can be used for troubleshooting purposes. See KB 7021803.
RX5174
Secure Shell is unavailable. Reflection Secure Shell must be installed. OpenSSH is unavailable because Reflection OpenSSH is not currently installed.
RX5176
You may have connected to an unsecure host or Kerberos negotiation did not succeed. This error message displays if the Reflection Kerberos check box (Security Properties dialog box) is selected, and you attempted to log on to a host computer that does not support Telnet authentication. To fix this, connect to a host that supports Telnet authentication, connect to a host using TELNET instead of KERBERIZED TELNET as your Method, or clear the Reflection Kerberos check box.
RX5179
Connection terminated due to user authentication failure. This error message displays if an incorrect user name is presented when a Secure Shell with Kerberos authentication connection is attempted. Type the correct user name to avoid this error message.
RX5202
Unable to read XRDB file. The Local X resource file (Xrdb) may have been deleted or corrupted. Make sure that you are attempting to open a valid Xrdb file.
RX5203
Unable to write server resources to '%s'. Reflection X is unable to save the server resources to the specified file. Make sure that you have specified a valid file name and are not trying to write over an existing file.
RX5205
Unable to open XRDB file. The Local X resource file (Xrdb) may have been deleted or corrupted. Make sure that you are attempting to open a valid Xrdb file.
RX5206
XRDB parse error at line: %d. You may be attempting to load a file that is not a Local X resource file (XRDB). Make sure that the file is a valid XRDB file. It's also possible that the XRDB file that you are attempting to load contains invalid syntax. Click Edit to view the file. Check the contents at the indicated line number.
RX5213
No local resource database has been loaded, and no X client or XDM session has stored resources in the RESOURCE_MANAGER property. Before you can view a local resource database, you must load it. In addition, the database file must contain valid X client properties. (The file cannot be empty.)
RX5401
Unable to automatically restart Reflection X server. Reflection X is probably already in the process of shutting down; just restart the server manually.
RX5403
There are X clients running. Restarting Reflection X will close all clients. Do you want Reflection X to automatically restart with your new settings in effect? When you make a change to a Reflection setting that requires a restart, you see a warning message to that effect. If clients are running, you may not want to restart right away.
RX5502
The Custom help file specified (%s) does not exist. The customized help file specified in the Rx.ini file does not exist. Make sure that the path and file name assigned to the CustomHelpFile parameter in the Rx.ini file are correct. Make sure that the customized help file exists at the specified location.
RX5503
No Custom help file has been specified. A CustomHelpMenuName has been specified but no custom help file is available from the custom help menu name.
RX5602
Can't access the wizard's initialization file. Make sure it is in the same location as the wizard's executable file. The wizard initialization file, Rxwizard.ini, and the wizard executable file, Rxwizard.exe, are normally located in the Reflection User directory. If Rxwizard.ini and/or Rxwizard.exe are not in this directory, move the file(s) there, restore the file(s) to the directory from back-up, or re-install Reflection X.
RX5605
You must enter a user name. The client file that you attempted to use does not contain a user name. To edit the file, select the file in the connection list on the left side of the Reflection X Manager. Then, edit the Connection Settings displayed on the right side of the window.
RX5606
You must enter a command to start an X client application. You must enter a command in the Command box (Connection Settings) before attempting to connect to a host.
RX5607
Could not locate host application. Reflection X could not locate the X client application specified in the Command box (Connection Settings). Make sure that you specified the X client correctly in the command. If Reflection X still cannot locate the X client, make sure that it is available on the host in the specified location.
RX5609
Could not start Reflection to connect to host. Reflection for UNIX and OpenVMS (or Reflection for ReGIS Graphics or Reflection for HP) could not be started. One of these programs is required to use the Client Wizard. If you think you already installed the program, check to see where it is (should be in the same directory as the Reflection X executable program, typically \Program Files\Reflection). If it's not there, install the "Reflection for UNIX and OpenVMS" component of Reflection X in Add/Remove Programs.
RX5610
Unable to log into the specified host. While the Reflection X Wizard was waiting for a login prompt or a password prompt from the host, the operation timed out. Make sure that the UserPrompt variable in the Wizard initialization file (Rxwizard.ini) specifies the correct login prompt. Make sure that the PasswordPrompt variable in the Wizard initialization file specifies the correct password prompt.
RX5611
Could not get command prompt from host. While the Reflection X Wizard was waiting for a command prompt from the host, the operation timed out. Make sure that the correct host prompt is specified in the Wizard's Command prompt text box. To find out the correct host prompt, select Show login processing and attempt to connect to the host. The login process is displayed in a Reflection for UNIX and OpenVMS window. You can see the prompt that the host is returning. If the correct host prompt is specified in the Command prompt box, you may have to increase the ResponseTimeout setting in the Wizard initialization file (Rxwizard.ini). The default value for ResponseTimeout is 10 seconds.
RX5614
Unable to locate Reflection for UNIX and OpenVMS, which is required to connect to hosts and locate X clients. Click Add/Remove Programs in Control Panel, select Reflection X, and then select Reflection for UNIX and OpenVMS. Reflection for UNIX and OpenVMS (or Reflection for ReGIS Graphics or Reflection for HP) could not be started. One of these programs is required to use the Client Wizard. If you think you already installed the program, check to see where it is (should be in the same directory as the Reflection X executable program, typically \Program Files\Reflection). If it's not there, install the "Reflection for UNIX and OpenVMS" component of Reflection X in Add/Remove Programs.
RX5618
Unable to create shortcut. You probably do not have adequate NTFS privileges for creating the shortcut in the desired location.
RX5622
Connection to the host has been lost. The Reflection X Wizard has not received the string of text on the host that it expected. It's possible that the connection between your PC and the host has been lost.
RX5623
Could not validate the command. Perhaps the connection to the host has been lost. The Reflection X Wizard could not verify that the client file (specified in the File name box) is in the specified directory on the host. Check the path and file name, then try to reconnect.
RX5624
Could not connect to the specified host. Make sure the host name is valid and that the host is available. Make sure that the specified host name is correct. If the host name is correct, verify that you can reach the desired host by using the Ping utility provided with your TCP/IP network software.
RX5702
When this check box is cleared, a remote window manager cannot be run. At session startup, most XDM environments—such as HP VUE or the Common Desktop Environment (CDE)—start a remote window manager. No remote window manager (such as HP VUE, Motif, olwm, and so forth) is able to run. X client windows will be controlled by the Microsoft window manager.

Error Numbers 6000+

RX10061
Connection refused. Please confirm the host's Telnet Server is running on the non-standard port (%d). Also, verify the host name or address. The host may be down or non-existent, or it may not allow the connection method you specified (for example, .rsh). Try a different connection method or a different host.
RX10650
A new toolbar button can be associated with a command to either run a client file or perform a menu function. This error message is displayed when there is no command specified, or when there is more than one specified. You must specify one (and only one) kind of Action for a custom button. For information on creating a button to execute a Reflection X command, click Settings > Toolbar > Customize and refer to the product help.
RX16063
%d PCF font was too large to convert to FON format. Reflection X can use this font in its original BDF/PCF format. The font you have selected is too large for conversion to the FON format (it exceeds the limitations of the Microsoft Windows internal resource table), but Reflection X can still use it by reading the font directly. This takes more time than using a font that is in FON format, but it allows Reflection X to display large fonts which are commonly used in Japan. Large fonts must be added to the Fonts.dir file in the directory where they are located before they can be used.
RX16067
%d PCF font was not converted to FON format. Portable Compiled Format (PCF) files are binary; it is possible that the one you are trying to convert is corrupted.
RX25002
Unable to open '%s'. File does not exist or is invalid. This error message occurs when a 16-bit version of Reflection X has been installed onto a machine running a 32-bit operating system, and Reflection X has been installed into a folder with a long file name that contains a space (for example, "Program Files").
RX33006
Could not map image to server during replay. There is most likely a mismatch between the color model on the computer used to perform the trace and the color model on the computer used to replay the trace. Make sure that both computers are using the same color model (in Reflection X Manager, open Settings > Color).
RX33007
Replay complete. Ignore errors selected: %s X protocol error(s) received during replay. See log for details. Open the log file to view the errors that occurred during the replay of the trace.
RX33008
Display format is invalid. Correct format is <address>:<server>.<X screen>. The display format in the xterm startup command is invalid. For more information on the xterm -display parameter, see Command xterm examples in the product help.
RX33009
Could not contact server at address %s. The IP or node address is incorrect or the host is down.
RX33013
Error received on socket. The socket couldn't be initialized (that is, replay can't connect to the X server), or there was a connection that is now gone (for example, if you're doing a replay on a remote machine, and the remote X server is reset).
RX33014
Connection to X server has been lost. The X client on the host lost the connection to the Reflection X server. Try connecting to the X client again.
RX33015
Connection to server lost. Stopping replay. This error message can occur when you play a trace on a remote node. Try replaying the trace again on the remote node. If the problem persists, check the connection between your computer and the remote node.
RX33016
Trace file contains invalid information. There is something in the file that cannot be processed. This can happen in the following cases:
The trace file has been corrupted in some way. If it was transferred in ASCII mode (as opposed to binary), for example, you will see this message when you try to replay it.
The file isn't a trace file.

RX33017
Could not contact server at address %s. Most likely, the address is incorrect or the host is down.
RX33024
Request type (opcode = nn) not supported in replay. Replay cancelled. An X client made an unsupported X protocol request. You cannot replay the trace.
RX33023
X protocol error received during replay. See log file for details. Open the log file to view the protocol error that occurred during the replay of the trace.
RX33028
Received an atom error. While replaying a trace, Reflection X detected that it received an undefined atom from an X client while performing the trace. You may want to change how Reflection X is configured to handle X Protocol Errors during trace playback.
RX33029
Pixmap format during trace is not compatible with replay. The pixmap format requested by an X client recorded during a trace is not compatible with the video card on the computer used to replay the trace. Trying changing the setting for the AdvertiseMSBByteOrder keyword in the Windows registry (for more information, see Reflection X administrator help).
RX33035
Visual format during replay not compatible with trace. The display hardware of the computer on which you are trying to replay the trace cannot handle the display requirements of the trace file. For example, your computer graphics card may support less colors than the computer that performed the trace. The replay can't continue. Replay the trace on the computer that you used to perform the trace.
RX33045
Connection refused by X server during replay. Reflection X attempted to replay a network trace to a remote node. The remote node refused the connection. Check the X server on the remote node and check the connection to the remote node.
RX33046
Trace file does not include full message data. It cannot be replayed. If you want to be able to replay the trace, select Full message data in the Reflection X Trace dialog box and perform the trace again.
RX33048
Replaying to a remote server: %s. Colormapping will be disabled. Reflection X is replaying a network trace on a remote node. Color mapping is disabled.
RX33073
Client cannot find or load TCP/IP stack and thus cannot contact local server. Install and/or configure your TCP/IP for a successful connection to the local server.
RX33057
Trace file includes client that was started prior to trace. The trace file cannot be replayed because it contains information from a client that was started prior to the trace. When a client is first started, a lot of information is exchanged between the X client and the X server (Reflection X). For example, this is when the client finds out how many colors the X server can display on what size screen. When a trace is performed after a client has started, the resulting trace file does not contain all of this header information.
RX33074
Client %d will be ignored during replay. The indicated client will be ignored during the replay because it has been filtered out.

Error Messages Without Numbers

WSAECONNREFUSED
Connection refused. The host may be down or non-existent, or it may not allow the connection method you specified (for example, .rsh). Try a different connection method or a different host.
WSAECONNRESET
Connection reset by peer. Socket error. The connection has been closed by the host. In many cases this message indicates a problem in the entry for Command (in the Connection Settings). Click Host Response on the Connection menu, set Method to TELNET, and try again. Check the text in the Host Response box to see if you can diagnose the problem.
WSAETIMEDOUT
Connection failure. Please verify that the remote host name or IP address is valid and that there is a network service listening for this transport. The specified host is not responding. It may be down or not on the network.
WSAHOST_NOT_FOUND
Host not found. Socket error. The host name could not be resolved. If you are using a domain name server, verify that your TCP/IP software is properly configured for domain name service (DNS). If you are not using a domain name server, make sure the specified host is listed in your TCP/IP host names file.
See your network software's documentation for more information. Another workaround is to specify the host by IP address in the Connection Settings.

WSAEMFILE
No more transport sessions are available. Refer to your network documentation to increase these values. Socket error. Refer to your network documentation to increase the number of TCP sessions for which your network is configured.
WSAENOBUFS
No more buffers are available. Refer to your network documentation to increase these values. Socket error. Refer to your network documentation to increase the number of TCP sessions or buffers for which you are configured.
WSAEWOULDBLOCK
Operation would block. Socket error. This message indicates a problem in the entry for Command (in the Connection Settings): You may be using an IP address or name for DISPLAY that is not listed in the hosts file (/etc/hosts) on the host to which you want to connect.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 2301.