Anyone have any idea what sub-error 711 is? Maybe it'll be helpful to me to find out why the function execution failed.
Error 51: p4ExecTask: EXEC 'TK_TR_DOCUMENT_UPDATE' returned non-zero kernel stat
us -1, reason 107, sub-error 711
Click the link below to see the new game I'm developing!
B&T Error codes
Started by
Rick Young
, Mar 24 2006 04:45 PM
3 replies to this topic
#2
Rick Young
-
- Members
-
- 266 posts
ProIV Guru
- Gender:Male
- Location:Guelph, Canada
Posted 28 March 2006 - 08:24 PM
Have not tested this to break it on purpose....
I suspect it was because some idiot
did DEFINE $$CMD(,400)....and then referenced it a 1/2 dozen times.
This sub-error 711 is apparently some form of buffer size error.
-Rick
I suspect it was because some idiot
did DEFINE $$CMD(,400)....and then referenced it a 1/2 dozen times.This sub-error 711 is apparently some form of buffer size error.
-Rick
#4
Rick Young
-
- Members
-
- 266 posts
ProIV Guru
- Gender:Male
- Location:Guelph, Canada
Posted 30 March 2006 - 01:35 PM
Credit where credit's due - ProIV Support gave the answer as to the meaning of 711. Theoretically only, I proved the issue, but Support confirmed an error contained within Traces.
The specific issue was related to the SYSTEM command in conjunction with the DEFINE.
SYSTEM can only carry 250bytes, whereas alphanumeric max DEFINE is 2000.
-Rick
P.S. It seemed to work ok with a DEFINE 300, however, I'll be changing this anyway.
The specific issue was related to the SYSTEM command in conjunction with the DEFINE.
SYSTEM can only carry 250bytes, whereas alphanumeric max DEFINE is 2000.
-Rick
P.S. It seemed to work ok with a DEFINE 300, however, I'll be changing this anyway.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
