Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Dreaded C0005 error for one user on same machine
Message
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01136555
Message ID:
01136574
Views:
14
>>We have a VFP app that resides on a windows 2003 server. The users that run the app log into the server via Terminal Server to run it - and basicly there are just a handfull of users for this app.
>>
>>Here is my problem...
>>USER A - everything works fine.
>>
>>USER B - gets this problem:
>>Fatal error: Exception code=C0000005 @ 07/14/06 03:58:24 PM. Error log file: C:\Program Files\Common Files\Microsoft Shared\VFP\vfp8rerr.log
>> Called from - main line 117 {C:\Momwin\Victor\MOM_Plugins\programs\main.prg c:\momwin\victor\mom_plugins\mom_plugins.exe}
>>
>>
>>This is really quite upsetting. I don't see how I could get such a fatal error with one user and not the next, considering they're on the same machine running the same program. FYI that line 117 has a "DO FORM" command in it.
>>
>>Does ANYONE have ANY ideas how I can fix this? I've recompiled, deleted foxuser.dbf - I'm out of ideas.
>
>- Does B see the problem only if A is already in the app, or does s/he get it independently? (i.e. multi-user issue)

Doesn't seem to matter if anyone else is in it or not - still have the same problem.

>- Any difference in permissions between A and B?

Just checked - and nope...same permissions.

>- Temp files left over from previous crashes in B's tempfiles folder?

Deleted all the temp files - still same issue.


I've had this problem here before with this app. In the past it's acutally usually just been the shortcut - deleteing the shortcut and then recreating and identical one usually fixed it. (or just clicking on the .exe directly and not using the shortcut at all). Other times when that failed I copied a backup of foxuser.* files over and that fixed it. This time though, nothing seems to be getting me out of this issue.
I HATE the evil c000005 error! arrrhhh!
ICQ 10556 (ya), 254117
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform