Browse Failure
If all methods were successful, then a complete list of the servers found on the machine is displayed. If no servers were found on the machine, the message "No servers were found on the machine" is displayed. You must then verify that either the correct machine name/TCP/IP address was entered in the previous page or that the OPC server(s) are correctly installed on the given machine.
If one or more methods fail, a message box is displayed indicating the methods that were used and which ones succeeded or failed. It also displays an error message indicating the reason for failure, as returned by the system. Any server(s) found are listed. You can select a server from the list or remedy the reason for the failure and rerun the search.
DDE
The following table describes the errors, associated messages, and corresponding explanations associated with the DDE Client task. These messages appear in the Last Error fields on the DDE Client Task dialog box and in the configured message destinations.
Communication Messages
Message Explanation
None No communication problems have occurred.
Cannot establish conversation. Server rejected request.
If the connection is local, the error indicates that either the server is not running or the topic does not exist. iFIX prompts you to start the server the first time this error is detected.
Communication Messages
Message Explanation
If the connection is through NetDDE, this error may indicate a network problem.
Cannot establish conversation, cannot create advise list.
The system has run out of memory while the DDE Client Task is attempting to make a connection to a server.
Cannot establish
conversation, cannot add to list.
The system has run out of memory while the DDE Client Task is attempting to make a connection to a server.
Cannot start advise loop,
server rejected request. The conversation with the DDE server has started but there is a problem with the item.
Cannot start advise loop,
cannot add to list. The system has run out of memory while attempting to establish communication.
Cannot start advise loop, server rejected data request.
The server rejected the initial request for data made by the client. The advise loop has been successfully established but the server refuses to pass data back to the client. This may indicate the server is overloaded.
Cannot start advise loop,
request timed out. The server took too long to acknowledge a request by the client to start an advise loop and the client timed out. This indicates the server is temporarily overloaded.
Cannot execute
command, request timed out.
The DDE client attempted to execute a command on the server.
Server is busy. The server was overloaded while a DDE transaction was attempted.
Low on memory. The server was low on memory while a DDE transaction was attempted.
Memory allocation failed. The server was low on memory while a DDE transaction was attempted.
User does not have rights to shut down the DDE Client Task.
The user attempted to shut down the DDE Client Task but does not have sufficient security rights to do so. The user must have the Background Task Exit application feature in his user profile in order to shut down the DDE Client Task.
Invalid Maximum Links. The user has entered an invalid character or a value out of range in the Maximum Links field. The valid range is 1 - 1000.
Invalid access period. The user has entered an invalid character or a value out of range in the Access Period field. The valid range is 0 to 172800 seconds.
Communication Messages
Message Explanation
Cannot create I/O list
(check memory). The system has run out of memory while establishing communication with a server.
Cannot create advise
loop list. The system ran out of memory while the user was opening the Active Advise Loops dialog box.
The following table describes the system messages and corresponding explanations associated with the DDE server.
DDE System Messages Error Code Explanation
1150 iFIX is not running.
1209 Invalid field.
1212 Field's value not known or block may be off scan.
1213 Invalid field.
1314 Invalid field.
1608 Network-related problem.
1620 Session not established. Cannot find remote node.
1624 Session with remote node has been lost.
1750 Tag is not defined in the database.
2005 Network-related problem.
2302 Either waiting for data or node name is not in the network table.
1620 Session not established. Cannot find remote node.
?E100 Invalid node, tag, or field entered, or problem returning data.
E-1? No communication established with DDE.
ERROR:99 Invalid node, tag, or field entered, or problem returning data.
The following table describes the messages and corresponding explanations that can occur when starting the DDE Client Task. The error will be displayed in the Runtime Error field and the configured message destinations.
DDE Client Startup Messages
Message Explanation
Cannot initialize DDEML A connection could not be made to the DDEML.DLL file. Either the file does not exist or it is not in the Windows search path.
Cannot create conversation
list (Check memory) The system ran out of memory trying to set up the conversation list.
Out of timer resources There are too many tasks running simultaneously. You should shut down a task to free up a timer for the DDE Client task timer.
Access
iFIX provides the SQLERR.TXT text file, located in the C:\Program Files\GE Fanuc\Proficy iFIX\App directory, to help you troubleshoot communication errors from your relational database.
This file contains communication error numbers. When a communication error occurs, iFIX displays @ symbols (by default) in a data link to indicate the problem.
If you are using Access, some of the same error numbers listed in the SQLERR.TXT file are used to indicate relational database errors. As a result, you may see @ symbols in the run-time
environment when no communication error has occurred. To correct this problem, delete the SQLERR.TXT file.