Epicor vista 4.4
whether I’m trying to find a previous job or adding a part numbers or any task I have to do: it’ll give me this error code (C0000005) and then asks me to restart the program, after restarting it lets me continue for a bit until I have to create a new job and then crashes again. [vista error 1-12-2026]
2 Likes
Wish I could help but I came in at Vantage 8.0 days so never experienced Vista.
1 Like
I can’t help either, but Vista 4ish was released around 2005-2006.. Congratulations! Your System can now go to college! Hopefully its getting a full ride. 
Wow Visual Fox Pro… those were the days! Cloud? WHOSE CLOUD!
Does this happen at every work-station? or just yours. Check on a different machine, if it doesn’t happen there… Visual Fox Pro used to be a … real pain when your user resource file got corrupted. Since it doesn’t appear to be related to specific data it may be that you need to clean up your FOXUSER.FPT / FOXUSER.DBF files (rename them)
(I googled this I don’t actually know much about Fox Pro) but it might be a hail mary
2 Likes
I think there’s only one guy here that may be able to help @timshuwy
4 Likes
So how do i send this post to timshuwy (Tim Shoemaker)
2 Likes
The bat signal has already gone up.
3 Likes
Sorry… my bat cave has no information in the bat computers about this old of a legacy product. Actually, my earliest version of Vista/Vantage that I ever actually ran was Vantage 8.0 and Vista 8.0… I did help with a couple of conversions from Vantage 6.7, but never actually even logged into one.
I did a search, and it seems that this is more of a “memory” error and could be one of many causes… when I did a google of Fox Pro and C0000005, I got multiple possible things. Here is one thread I found: C0000005 error and troubleshoot - Visual FoxPro | Microsoft Learn
anyway, best of luck… that version is too old for me. If you contact support, they might have someone around who used that version, but it is a long shot.
2 Likes
What operating system is it running on? If it’s Windows 10 or later, you may have to turn off Memory Integrity in the Core Isolation settings.