UniVerse 10.1.15 and late:
7883 In certain circumstances, UniVerse may have incorrectly written
information from the SYS.MESSAGE file into other files. This may
have caused the header or a primary group of the file to be
overwritten, resulting in file corruption. This problem has
been fixed.
Hope this helps.
Regards
JayJay
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Kent
Sent: 07 February 2006 22:58
To: u2-users@listserver.u2ug.org
Subject: [U2] SYS.MESSAGE file being corrupted
Has anyone experienced the above and have an explanation
I have seen some postings at indexinfocus but no resolution.
There doesnt appear to be any 3rd part software involved and the application
software doesnt ever reference this file but its occurred 3 times in the
last
3 months.
The quick fix was to make the file read only.
A few days later i start getting errors messages from an edi update program
initiated via a script complaining that...
Program "*SOE.SCHAGE": Line 382, WRITE attempt on read-only file.
Program "*SOE.SCHAGE": Line 317, WRITE attempt on read-only file.
Program "*SOE.SCHAGE": Line 317, WRITE failure.
program executes ON.ABORT
I cant reproduce this error and the same update can be run from the menu
immediatiatly after the error without a problem.
I have started adding in ON ERROR and LOCKED options on the file writes to
capture a STATUS() but no results as yet.
Have also physically moved the file but made no difference.
Plus there was mention of problems of high pid numbers but i dont think this
is likely
Any suggestions appreciated
jak
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
