Thread: [FAD] Access Violation
July 17th, 2003, 12:50 PM #1
[FAD] Access Violation
Anyone seen this before...
I had a box pop up saying Access Violation, The instruction at adress 00000000 attempted to read from location 00000000.
I then have three options, Save As, Details and Close.
If I click on Details, I get another popup saying:
Salford exception handler
Fail to register registers dialog procedure.
Information will appear in a simple message box.
The trouble is that it snoozes FAD and will only restart after my intervention, the really anhoying thing is that it did it 5 mins after I went to bed last night and therefore did absolutely nothing all night
I have tried holding that particular wu, but it did it to another, so I doubt that it is just that job.
Any ideas how to cure it? (no pun intended )
Last edited by win2kuser; July 17th, 2003 at 12:53 PM.
July 17th, 2003, 12:59 PM #2
Not sure exactly what causes it. It usally happens to me right after a new version is released or after a month or so of use. May me think it doesn't like some data somewhere. Whenever I get it, I just restart FaD.
July 17th, 2003, 07:16 PM #3
Are you running off a Queue server? I used to get overflow errors and found copying the SALFLIBC.DLL to the WINNT directory of each machine (or the root directory of your OS installation) then removed the copy that's in the shared FaD folder, but That doesn't sound like the issue.
Perhaps Keith could add more to this and possible causes, however all 0's for address and location.
I'll let him know.
July 18th, 2003, 01:50 AM #4
- Join Date
- Apr 2003
It is not apparent to me what the problem might be. I agree that if it happens with different jobs then it is not likely to be anything to do with the job but some other software or hardware. As the message is broken it is unlikely to be a simple THINK programming error.
We will investigate changing THINK so that it will restart automatically for all exceptions.
July 18th, 2003, 02:09 AM #5mickwishGuest
I had this happen to me before I put the extra line in think.env to stop it hogging the CPU on my queue server. Seemed to happen every now and again when a client cow tried to log into queue server.
Since I added the line into think.env it hasn't done it again. So thought it might have been that. COuld be coincidence, though
July 18th, 2003, 04:59 PM #6
OK, thanks for the replies guys.
I have restrarted the pc since this, and it all seems ok now. I have had this happen a few times in the past on some of the other cows, but I was always about at the time to restart it. This time though, I lost a full night production which is why I became a bit more concerned.
Keith, having Think restart after any exception sounds like a great idea, I know a lot of people run remotes, or like me just dumb boxes without monitors. It really would be a 'plug in and forget' client then
BTW, this has always happened on boxes running Win2K, I used to have a couple of cows running win98 and it never happened. hmmn
Still the best client out there though IMO
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)