FATAL ERROR - invalid opcode 254 in token table

Kenneth Brody kenbrody at spamcop.net
Mon Mar 24 10:15:15 PDT 2014


On 3/23/2014 2:21 PM, tob at b-e-s-t.com wrote:
>
> Never saw this type of error before.  Running dclerk fp 4.8 on centos 5 with -t 600000
> I realized that you would need more specific data but any quick thoughts?
> Is there something in debug that could point me in the right direction?
>
> FATAL ERROR
> Invalid optcode 254 in token table
> Line 5874, offset 1.

Usually that's a sign of a corrupted .tok file, or one using new features 
and compiled on a version later than your rclerk/rreport.  (For example, if 
you were to use the ENCRYPT function and compile it using a 5.6 or later 
rcabe, and run it with a 5.0 rclerk.)

However, since that can't be the case in dclerk, perhaps you've run into 
something that's corrupting memory?

Version 4.8 is no longer supported, but if it's repeatable in a current 
version of filePro, contact fpsupport and arrange to send files to demonstrate.

-- 
Kenneth Brody


More information about the Filepro-list mailing list