MFC Application has stopped working, Server 2008 R2
-
This application is working fine on 2003 R2 and 2000 Servers and even our other 2008 R2 server but I keep getting the error on this new server. I could have sworn I had to do some tweak to get it working on 2008 R2 but I can't remember what it was. Basically what is happening is the application is doing a DB "query" that is taking a fair amount of time and as a result the UI is no longer "responding" even though the applicaion is working away and in fact not frozen/locked/in an infinite loop. The application is written in VS 6 and as you can see in both the description and below using MFC.
Problem signature:
Problem Event Name: APPCRASH
Application Name: qexectest.exe
Application Version: 1.0.0.1
Application Timestamp: 46b1e781
Fault Module Name: MFC42D.DLL
Fault Module Version: 6.0.8168.0
Fault Module Timestamp: 358870e1
Exception Code: c0000005
Exception Offset: 0002b4af
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional Information 1: d67f
Additional Information 2: d67fe74012b2fff2bcc60d9e40d9bbd3
Additional Information 3: 7b8d
Additional Information 4: 7b8d5be233f423bf0e8bf92697c74b98 -
This application is working fine on 2003 R2 and 2000 Servers and even our other 2008 R2 server but I keep getting the error on this new server. I could have sworn I had to do some tweak to get it working on 2008 R2 but I can't remember what it was. Basically what is happening is the application is doing a DB "query" that is taking a fair amount of time and as a result the UI is no longer "responding" even though the applicaion is working away and in fact not frozen/locked/in an infinite loop. The application is written in VS 6 and as you can see in both the description and below using MFC.
Problem signature:
Problem Event Name: APPCRASH
Application Name: qexectest.exe
Application Version: 1.0.0.1
Application Timestamp: 46b1e781
Fault Module Name: MFC42D.DLL
Fault Module Version: 6.0.8168.0
Fault Module Timestamp: 358870e1
Exception Code: c0000005
Exception Offset: 0002b4af
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional Information 1: d67f
Additional Information 2: d67fe74012b2fff2bcc60d9e40d9bbd3
Additional Information 3: 7b8d
Additional Information 4: 7b8d5be233f423bf0e8bf92697c74b98MacRaider4 wrote:
...the UI is no longer "responding"...
This is usually related to the main thread processing something and the UI cannot respond to the
WM_NULLmessage."One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
MacRaider4 wrote:
...the UI is no longer "responding"...
This is usually related to the main thread processing something and the UI cannot respond to the
WM_NULLmessage."One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
That is correct, it is however working "fine" on the other 2008 R2 Server. The window grays out and has "not responding" in the ribbon, but it still carries on and completes. However on this server it quits.
-
That is correct, it is however working "fine" on the other 2008 R2 Server. The window grays out and has "not responding" in the ribbon, but it still carries on and completes. However on this server it quits.
I recommend that you use the remote debugging tools in Visual Studio to find where it is hanging up. Remote Debugging[^]
The difficult we do right away... ...the impossible takes slightly longer.
