Applies To:
  • CitectSCADA 4.x 5.x
Summary:
I am getting the following error message running Citect under Windows 95:

This program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.

How can I find the cause of this problem?

 

Solution:
This error message is displayed when Citect has caused an exception. Under Windows 3.x you can use DrWatson to capture information about this trap and send into Citect support. If you are running the 16 bit version of Citect under Windows 95, the DRWATSON.EXE from Windows 3.x will also capture this exception. You may also capture this exception under Windows NT with DRWTSN32.EXE. However there is no DrWatson for Windows 95.

When you get this message under Windows 95 you can click on the Details>> button to get some more information about the problem. You may copy this to the clipboard and paste into notepad. You will see something like this:

CITECT32 caused an invalid page fault in
module CITECT32.EXE at 013f:00488092.
Registers:
EAX=00000000 CS=013f EIP=00488092 EFLGS=00010246
EBX=012c0051 SS=0147 ESP=008af744 EBP=008af758
ECX=00000000 DS=0147 ESI=00000000 FS=44d7
EDX=7efefeff ES=0147 EDI=81597080 GS=0000
Bytes at CS:EIP:
66 0f be 01 e9 78 00 00 00 e9 6b 00 00 00 68 74
Stack dump:
81597080 00000000 012c0051 00af8079 00000000 008af774 004bb58c 00515260 00515264 00515265 00515266 815a4935 008af8e0 004a019b 00487f8a 00500001

If the above message says CITECT32 caused an invalid page fault in module CITECT32.EXE at (some address) then send this information into Citect support along with details of the version of Citect you are running and what you where doing to cause the exception. If the message says CITECT32 caused an invalid page fault in module <not Citect> at <some address>, then the exception has occurred outside of Citect and this information will not be able to tell support enough to find the cause of the problem.

To get more information on the exception you can either run the 16 bit version of Citect and use DRWATSON.EXE to capture the fault or run 32 bit version of Citect under Windows NT and use DRWTSN32.EXE. If you have a debugger you can see Q1883 for details of how to get more information on the exception under Windows 95.

In version 4.10 rev 2 and later Citect has a built in exception handler. When an exception occurs Citect will display the error message "A severe error has occurred. Process will terminate". Citect will then write details of the fault to the SYSLOG.DAT file in the windows directory and then terminate. You should copy the Exception report from the end of this file and send into Citect Support. As version 4.10 rev 2 has the built in exception handler you should upgrade to this version if you have getting any exceptions under Windows 95. In version 4.20R2 with SP D and version 5.xx these reports will now be logged to a DRWTSN32.log file in the windows directory instead of the SYSLOG.DAT file. Refer to Q2047.

 
Keywords:
 

Attachments