[quote user="e7h"]
The application, C:\MERCURY\mercury.exe, generated an application error
The error occurred on 11/18/2008 @ 10:45:58.729 The exception generated
was c0000005 at address 00462DDA (mercury!fplsw_write)
[/quote]
I suspect this is a nonsense error. "fplsw_write" is a Mercury symbol - it's the message write routine for the foldering layer module that handles system-wide folders. Now, system-wide folders are not supported by Mercury, so there's no way this code can ever actually be called. The fact that the post-mortem debugger is reporting this symbol as the crash address indicates either that it's got the symbol name wrong, or that something has gone madly wrong on the stack resulting in a random jump into a piece of code: neither of these scenarios is amenable to any kind of practical solution.
If you start seeing this frequently (i.e, more than once or twice a month), please note down what seems to be happening in the system at the time, paying particular attention to any error messages in the console windows. You might also want to consider using the Mercury loader, since it will allow automated recovery from anything like this (the fact that you see the exception means that you're not using the loader).
Cheers!
-- David --
[quote user="e7h"]<p>The application, C:\MERCURY\mercury.exe, generated an application error
The error occurred on 11/18/2008 @ 10:45:58.729 The exception generated
was c0000005 at address 00462DDA (mercury!fplsw_write)</p>[/quote]
I suspect this is a nonsense error. "fplsw_write" is a Mercury symbol - it's the message write routine for the foldering layer module that handles system-wide folders. Now, system-wide folders are not supported by Mercury, so there's no way this code can ever actually be called. The fact that the post-mortem debugger is reporting this symbol as the crash address indicates either that it's got the symbol name wrong, or that something has gone madly wrong on the stack resulting in a random jump into a piece of code: neither of these scenarios is amenable to any kind of practical solution.
If you start seeing this frequently (i.e, more than once or twice a month), please note down what seems to be happening in the system at the time, paying particular attention to any error messages in the console windows. You might also want to consider using the Mercury loader, since it will allow automated recovery from anything like this (the fact that you see the exception means that you're not using the loader).
Cheers!
-- David --
