Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The APPNAME stopped working
Message
From
20/04/2022 13:08:10
 
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
01684195
Message ID:
01684200
Views:
37
>>>Hi,
>>>
>>>I got a message from a customer that the feature that always worked, now, for all users gives the error message:
>>>
>>>
>>>AppName has stopped working
>>>A problem caused the program to stop working correctly.
>>>Windows will close the program and notify you if the solution is available
>>>
>>>
>>>It appears that the message comes from Windows, not for the application. I don't get this error.
>>>
>>>Where would you suggest I ask the customer to look? He wrote, all user, this is puzzling.
>>>
>>>TIA
>>
>>I got something like this when a .NET program of mine ran a long time with no user interaction.
>>Windows thinks it's in a loop and stops it.
>>I solved it by using a background helper.
>
>This is a VFP 9 application, not .NET. From the message of the user, the problem happened immediately when he clicked on the button. It could be that the problem has the same bases though.
>I wrote to him to shutdown the PC and restart. Hopefully he will let me know of the result.
>And since the problem is with all their users and they all use the app from their desktops, I suspect that the SQL Server had a glitch.

The error is Windows' "kinder, gentler" way of saying a 0xC0000005 ("C5") error occurred in your app and Windows killed it dead before it could spread i.e. affect other running processes on your computer.

If all the users are getting that message, in some ways it makes it easier to troubleshoot as it must be something common to them all:

- An issue with SQL Server is a possibility. That said, ODBC clients are designed to be fault-tolerant and to not crash hard if there's an issue talking to a SQL server. I've never personally seen a C5 error caused by an issue with an ODBC connection to a remote DBMS

- If everyone loads your app from a server share, a connectivity issue with that server might cause what you're seeing

- If everyone is using the same antivirus app, maybe a bad update is flagging part of your app

- If they have a managed environment, maybe some sort of Windows or other update was rolled out recently to all their computers
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform