Hi Eric,
Unfortunately I'm still getting the access violation on Debian x64 (I thought it had gone but it hadn't)
Anything we can go through to try and look at this?
Thanks again
I'm sorry about this. Can you give any more information about what the program is doing when the access violation occurs? It's quite safe to press the OK button ("Press OK and risk losing data") when you get the error message, then you can check the event log to see if anything is recorded there.
Hi Eric,
I've checked the program log and all it says is that it's unable to retrieve stats. When I log back in and see the violation error, it's just like the program has frozen, and hasn't done anything since the violation. I click okay, and must restart the program before it'll start working again.
I'm using this on Debian Squeeze x64.
Thanks again for your help.
P.S I thought this had solved itself in 3.2, but when the server was restarted after updates, it happened again. It's still happening in 3.5.