Graham, It means a process is trying to access memory outside its process space: ususally an uninitialized pointer or an object reference to an object that has been destroyed.
This generally points to an incompatibility with system DLLs, COM sub-system or some equally painful-to-find problem ... You might be *very* lucky and locate the issue using a tool like Dependency Walker (available free - just google for 'Dependency Walker') if it is a clear mismatch. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Graham Hansen > Sent: 04 February 2005 15:22 > To: u2-users@listserver.u2ug.org > Subject: [U2] Memory cannot be written to > > Anyone seen a message on Windows 2003 servers when the > services are started :- > > > > "The instruction at 0x00144590d referenced memory at > 0x00000246. The memory > > could not be written to. > > > > thanks > > Graham Hansen > ------- > 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/
