I've seen similar errors in UniData with invalid keys (both length and characters). Usually it only happens on the write....
Hth Colin Alfke Calgary, Canada -----Original Message----- Dan Fitzgerald Attempting to write to an invalid memory address can come from a few issues. I've seen it come from having control characters in an item id, but with windows 2003, it's likely to come from a 32-bit limitiation, or perhaps a physical RAM problem. An other possibility is a corrupted file. Can you run ANALYZE.FILE against the file in question? Or, better yet, fixtool? (does 10.1.3 have fixtool, or is it uvfixfile on that platform?). > From: go_mnvikings > > I get this error everyonce in in a while... > > This time, I wrote a simple "bash" program to update records. It is a single > program with 5 file opens, a couple of reads, no calls to other programs, (You > get the point - it is basic). Anyways, I am running this and keep getting > kicked out of Universe (completely drops my session). So I go to the Computer > Management console on the server and look at the Application Error logs. I have > run it 3 times and here are the 3 errors... > > "UniVerse error: Unhandled Exception raised at address 0x10083DFA : Access > violation. Attempted to write to address 0x00000000. Binary data is processor > CONTEXT structure.." > > "UniVerse error: Unhandled Exception raised at address 0x7C82CAC2 : Access > violation. Attempted to read from address 0x54524150. Binary data is processor > CONTEXT structure.." > > "UniVerse error: Unhandled Exception raised at address 0x7C82A774 : Access > violation. Attempted to read from address 0x00000000. Binary data is processor > CONTEXT structure.." > > We run Universe 10.1.3 on a Windows 2003 server SP2. Any thoughts? _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
