Attachmate Error Messages
Contents |
note lists Reflection X 14.x error messages and related troubleshooting suggestions. About Reflection X Error List The status and error messages in Reflection the settings file was specified on the command line but could not be found X are listed by number in this technical note. These messages
Reflection For Unix And Openvms Has Stopped Working
may appear in a Microsoft Windows alert box or in the Reflection X log file. Some Reflection a timeout occurred during a call to transport code X errors are not listed here either because they are self-explanatory, or because they require assistance from Technical Support. Error Numbers 0-1000 Error Numbers 1000-1999 Error Numbers
Reflection Ftp Client Has Stopped Working
2000-2999 Error Numbers 3000-3999 Error Numbers 4000-4999 Error Numbers 5000-5999 Error Numbers 6000+ Error Messages Without Numbers 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 Technical a secure shell error occurred while trying to make a connection Note 1586 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
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
preceded by the identifying string "WINSOCK error:") are returned by the Windows Sockets library if an error occurs in the network
Attachmate Reflections
interface layer between Windows and the TCP/IP stack you are using. The
Reflection For Unix And Digital
Windows Sockets library (supplied in a module called Wsock32.dll) is included as part of the Windows operating system. For some network Windows Sockets implementations, when you are connected to a server, several things can cause this message to be displayed: You tried to start a file transfer http://support.attachmate.com/techdocs/2301.html or perform a directory operation (such as changing directories or refreshing the current directory). If you see this error when attempting to transfer a file or to obtain a directory listing, then your network implementation does not work with the FTP Client. You started another instance of the FTP Client and tried to open another connection to the same server. https://www.attachmate.com/documentation/reflection-desktop-v16/rdesktop-guide/data/t_6552.htm If you get this error message when trying to connect, it indicates that your network implementation supports only one connection at a time to a given server. You cannot start separate instances of the FTP Client and attempt to connect to the same server with each instance. Connection refused The connection attempt was unsuccessful due to a problem on the host; possibly the host is down or the server is not running at this time. Wait a while, and then try to connect again. Connection reset by peer During a file transfer, the remote host reset the server connection. Close the server connection, reconnect, and try the transfer again. Connection timed out The attempt to connect to a server was timed out by your network software without establishing a connection. This may be because the server is not running. Wait a while, and then try to connect again. Network is down The Windows Sockets implementation has detected that the network subsystem has failed. Your network should be restarted. Network is unreachable The network can't be reache
reached the maximum TCP/IP session quota) SOCKETS ERROR: connect call failed, errno=ddd (errortext) The Client is unable to connect to DBServer. In http://docs.attachmate.com/databridge/6.2/errors/20767.htm this case, check the following: Did you enter the correct host name or IP address? Did you enter the correct port number? The port number you enter must match http://support.attachmate.com/techdocs/1433.html the port number as it is defined in DBServer parameter file. Is the host running? If so, is DATABridge Engine and DBServer running? SOCKETS ERROR: getaddrinfo call failed, errno=ddd reflection for (errortext) This message appears when the Client cannot resolve any of the host names supplied to the Client via the define command. Check the following: Did you enter the correct host name? If you entered the host name, did you set up your domain name resolution parameters correctly in the Windows Network folder (in control panel)? If reflection for unix you entered the host name, is the domain name server running? If the domain name server is down, change the host name in the DATASOURCES table to the IP address and try the command again. SOCKETS ERROR: recv call detected a closed { server | console } connection This message appears when the Client is reading TCP data, and indicates that the Client received an abnormal status that indicates the connection to DBServer is closed. SOCKETS ERROR: recv call failed for { server | console } connection, errno=ddd (errortext) This message can occur during a define, process, clone, or switchaudit command. It indicates that the Client encountered an error while receiving data. This error typically occurs when DBServer aborts or resets the TCP/IP connection. In your Winsock documentation, look up the error code indicated by ddd. SOCKETS ERROR: recv call returned 0 after select reported data available This message, which only occurs when the connection to DBServer is being initialized, indicates that the Client could not obtain the requested data. T
the Web 2011 (All Editions) Reflection for the Web 2008 (All Editions) Summary This technical note explains how to view the Java Console in popularly used browsers. The Java Console is a useful tool for isolating problems that occur with Reflection for the Web sessions. Viewing the Java Console Log Follow the steps for your browser to view errors in the Java console: Internet Explorer for Windows Firefox for Windows Netscape 7 Safari and Mozilla Firefox for Macintosh Internet Explorer for Windows Internet Explorer for Windows can use either the Microsoft Virtual Machine or the Sun Java Plug-In 1.4 or higher as the default virtual machine for Java applets. To view your Java console, follow the steps in the section below that applies to your Java virtual machine. Microsoft Virtual Machine On the Tools menu, click Internet Options. Click the Advanced tab. Scroll down to the section titled Microsoft VM. Select "Java console enabled" and "Java logging enabled." Restart your browser. Repeat the steps that caused the problem. On the View menu, click Java Console. Note any error messages that appear. You can copy the contents of the console by selecting the text with your mouse and pressing Ctrl+C on your keyboard. Sun Java Plug-In 1.4 or Higher Click Tools > Sun Java Console. Repeat the steps that caused the problem. Note any error messages that appear in the Java Console. To copy the console, click the Copy button in the console window. Note: Alternately, you can open the Java console by double-clicking the Java Plug-in icon in the Windows system tray while the Reflection for the Web session is running. Firefox for Windows After launching Reflection for the Web, look for the Java Console icon in the notification area (system tray) of the Taskbar. (This is typically located in the right bottom corner of your Windows desktop.) Right-click the Sun Java icon and select Open Console. Repeat the steps that caused the problem. Note any error messages that appear in the Java Console. To copy the console, click the Copy button in the console window. Netscape 7 Start the Java Console. On the Tools menu, click Web Development > Java Console. Repeat the steps that caused the problem. Note any error messages that appear in the Java Console. To copy the console, click the Copy button in the console window. Safari and Mozilla Firefox for Macintosh Open the Application directory under Utilities. Select Java. Then select Java 1.x.xx Plug-in Settings and enable “Use Java Console.” Perform the steps that caused the problem. Note any error messages that appear in the Java Console. To copy the