I've hit an emergency situation with an older setup that controls a critical system. There's a Windows XP "server" that interfaces with a Rockwell PLC via ethernet.
The server had a processor thermal issue that was causing intermittent shutdowns for a period of time prior to being called in. I managed to repair this and the filesystem corruption from these shutdowns, but after I brought the system back online the RSView32 application will still not start properly. The errors are as follows:
If I'm reading this correctly the startup fault is ultimately due to the "record not found" and thus that leads me to believe that this is a database issue. Anyone able to confirm or correct my assumption here based on this message (and many repeated identical messages)?
Ultimately I'm guessing that Watcom TagServer is the problem with a database corruption. Is there a way to check/correct the consistency of this database server that would then in turn resolve this record error?
This is operating with Watcom SQL Database Engine Version 4.0e. If this sounds reasonable, is there a way to check and restore consistency to the database .db file?
Unfortunately there's no one around that understands this system any longer and the original developers are no longer available, thus I'm left trying to resolve this issue alone.
The server had a processor thermal issue that was causing intermittent shutdowns for a period of time prior to being called in. I managed to repair this and the filesystem corruption from these shutdowns, but after I brought the system back online the RSView32 application will still not start properly. The errors are as follows:
Code:
Unable to synchronize tag 'XX0X_XXXXX_XX'.
Cause: Node 'XXXX_PLC' not found.
Cause: Record not found.
If I'm reading this correctly the startup fault is ultimately due to the "record not found" and thus that leads me to believe that this is a database issue. Anyone able to confirm or correct my assumption here based on this message (and many repeated identical messages)?
Ultimately I'm guessing that Watcom TagServer is the problem with a database corruption. Is there a way to check/correct the consistency of this database server that would then in turn resolve this record error?
This is operating with Watcom SQL Database Engine Version 4.0e. If this sounds reasonable, is there a way to check and restore consistency to the database .db file?
Unfortunately there's no one around that understands this system any longer and the original developers are no longer available, thus I'm left trying to resolve this issue alone.
Last edited: