Error: "RDBRead.C Line . . . , RDBGTSet.C Line . . . " on NAD client after Notify Client. (Assertion)


Legacy Number# 9892
Doc ID: FAQ3725
Version: 6.0
Last Modified: 01/12/2009

ANSWER

Error: "RDBRead.C Line . . . , RDBGTSet.C Line . . . " on NAD client after Notify Client. (Assertion)
Error: "RDBRead.C Line . . . , RDBGTSet.C Line . . . " on NAD client after Notify Client.
The application is corrupt.
Application corruption can be caused by various actions which are hard to trace once the corruption has occurred. Examples include improper shutdown of the computer while files are in use, a power failure or surge, and unacceptable characters in a file.

FORCE RECOMPILE THE INTOUCH APPLICATION, use a working backup, or rebuild the application following Tech Note 112.
Click for more information.
Corrupted Application Information:

If the basis files of the application are not corrupted, the application can be force-recompiled. To force a recompile of an application, delete the *.WVW, *.AVL, *.$$$ and the RETENTIV.* files.  Upon restarting WindowViewer, the runtime files will be recompiled and re-created.

If the application is not successfully recovered after a forced recompile, the basis files are likely to be corrupted or damaged.  If you do not have a working backup of the application, you will need to rebuild the application.

Click here for Tech Note 112: "Recovering a Corrupted InTouch Application".


Excerpt:

Tech Note 112
Recovering a Corrupted InTouch Application

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See theTerms of Use for more information.

Topic#: 000720
Created: October 1998

This Tech Note outlines the most common reasons Wonderware® InTouch™ applications can become corrupted and provides a step-by-step procedure to rebuild and recover your application.

Note You should always backup your InTouch application files. If a backup of your application is not available and the DBDUMP.EXE utility is unable to create a CSV file from your application database, then only a partial restoration of your application will be possible and your database must be recreated from scratch. In such cases, the windows and scripts can often still be recovered.

Identifying a Corrupted Application

Most InTouch application corruption occurs after an application’s windows, tagname database, or scripts have been modified. You will know your application is corrupted primarily because a Wonderware Technical Support engineer has determined that this is the case. Here are some common indications of a corrupted application:

  • Opening a window or running a script causes WindowMaker to terminate or shut down abnormally.
  • When starting WindowViewer, you see an assertion error. Assertion errors indicate that there is a problem with the database entries in the animation links or scripts. Typically, assertion errors appear as FDRD errors. FDRD is the prefix used in the error message dialog box, such as FdRdKey element #1.
  • WindowViewer starts and runs properly for a while and then suddenly, for no apparent reason, a GPF or an Assertion error occurs. Usually this happens when a corrupted script executes on the change of an event or a corrupted window is called to open.
  • During the conversion of your application from one version of InTouch to another, the conversion halts with an error.

Note If the conversion halts as described above, move the error message aside and take note on which window or what type of script the conversion program stopped. Most likely, that window or script is corrupted.

 

Author Notes

Concept_Creator: WALTERB
Concept_CreationDate: 5/7/2002 5:01:10 PM
Concept_LastModByUser: richc
Concept_LastModDate: 1/12/2009 10:58:38 PM