Troubleshooting Guide for ECCE

Here are common ECCE errors users might encounter. There are various components involving with an issue. The solutions on this page are possible ones. When the suggested troubleshooting solution does not solve an issue, please report it to Customer Support via e-mail at support@cimetrix.com.

If you are having problems connecting ECCE to an equipment or simulated equipment, please run the EDA Connectivity Test to confirm basic network access, security setup and web service availability.

Symptom Possible Causes Troubleshooting Action
After pressing the Connect button in the "Create new Interface A Connection" window, a dialog with the following text appears:

Failed to connect to ECCE Consumer web service. The request failed with HTTP status 405: Method not allowed. Do you want to continue with establishing the connection?
IIS is not installed before .NET framework installation, and .NET framework is not installed correctly. From the command window, change a directory to .NET framework you have installed (ex: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322). Then, type "aspnet_regiis -i" (without quotes) and hit enter key. This will configure ASPNET to use IIS. It also add the configured ASP.NET to the Web Services Extensions list. Make sure the status is "Allowed".
No log is displayed on Command History tab of ECCE. A checkbox for logging is not checked. Put a check on "Enable Report logging in Command History" checkbox on Command History tab.
ECCE doesn't receive Consumer callbacks such as NewData. ECCEConsumer is not configured to use the correct version of .NET framework (1.1.4322). If you have installed .NET framework before IIS in installed, register .NET framework by the following instruction:

From the command window, change a directory to .NET framework you have installed (ex: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322). Then, type "aspnet_regiis -i" (without quotes) and hit enter key. This will configure ASPNET to use IIS. It also add the configured ASP.NET to the Web Services Extensions list. Make sure the status is "Allowed".

Make sure to configure ECCEConsumer web service to use .NET framework 1.1 SP1.
Windows XP:
  1. Open Internet Information Service from Control Panel.
  2. Select ECCEConsumer's property and set ASP.NET version to 1.1.4322.
Windows 2003 Server:
  1. Open Internet Information Service (IIS) Manager from Control Panel.
  2. Select ECCEConsumer under Web Sites folder and open a property dialog of ECCEConsumer.
  3. Make sure ASP.NET version on ASP.NET tab is 1.1.4322. Note that if multiple ASP.NET versions are installed on the Windows Server 2003 computer, then you must create multiple application pools with at least one pool per version. Configure ECCEConsumer to run in the application pool using ASP.NET 1.1.4322.
(Note: If your PC for ECCE installation only has .NET Frame 1.1.4322 installed. It will be used it by default.)
CPU usage of aspnet_wp.exe increases to 100%, the unmanageable level, and put too much stress on a computer. The data collection frequency of activated DCP is below 10ms. Or, the logging for ECCE is turned on. Both cases causes to increase CPU usages. Change the data collection frequency of the activated DCPs to over 10ms. Or, turn off the ECCE logging.
Can not see the full set of SOAP XML. This feature is not supported by ECCE. In order to see the entire SOAP XML message, we recommend using a "network sniffer", such as WireShark (www.wireshark.org). It is freeware. Other products are also available.
Click "Add Event..." button to create an event request. But can not select multiple events. As dictated by the E134 standard, an EventRequest is only permitted to specify one event ID. Temporarily disable all anti-virus/computer protection software, and uninstall .NET framework. Then reinstall .NET framework. If there are multiple versions of .NET framework, reinstall them in the order of ascending version numbers.