Event 1000, Application Error, Windows 7, Visual Studio 2008

I've got an application we use at our company.

All of our Windows XP PCs and Windows 7 PCs use it.

I can run it in the debugger under Visual Studio 2008 and build the Installer that all of the other PCs use to install it with, but I can not get it to run after installing on my PC (the installation shows no errors).

Under Event Viewer > Windows Logs > Application, two (2) events are fired:

1. The Error thrown when I try to run the installed application:

   Faulting application name: Suite.exe, version: 2.2.21.0, time stamp: 0x4d389f32

   Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802

   Exception code: 0xc00000fd

   Fault offset: 0x00000000000076cf

   Faulting process id: 0x1424

   Faulting application start time: 0x01cbb8f485a2a9d8

   Faulting application path: C:\Program Files\Aaon Coil Products, Inc\ACP Software Suite\Suite.exe

   Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

   Report Id: c58bd590-24e7-11e0-b398-00248103a942

2. An Informational message fires up immediately after with Windows Error Reporting:

   Fault bucket 28268826, type 4

   Event Name: APPCRASH

   Response: Not availab开发者_JAVA技巧le

   Cab Id: 0

   Problem signature:

   P1: Suite.exe

   P2: 2.2.21.0

   P3: 4d389f32

   P4: ntdll.dll

   P5: 6.1.7600.16559

   P6: 4ba9b802

   P7: c00000fd

   P8: 00000000000076cf

   P9:

   P10:

   Attached files:

   C:\Users\cp-jpool\AppData\Local\Temp\WER492A.tmp.WERInternalMetadata.xml

   These files may be available here:

   C:\Users\cp-jpool\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Suite.exe_e131a0d577e0788f7db9b54fd53b35e27d8860e2_11df4dea

   Analysis symbol:

   Rechecking for solution: 0

   Report Id: c58bd590-24e7-11e0-b398-00248103a942

   Report Status: 0

This repeats every time I try to run the application I made with this PC ...on this PC, but no where else.

Could someone give me some idea of what's going on and how to fix it?

---

Do you get prompted to elevate Visual Studio when you run it?

If so, try running the app elevated.

Basically, isolate what's different between the two:

1. Can you run it in Visual Studio without debugging? Including when you set it to "Release"?

2. How about if you build and install it as "Debug" then start it and try to attach to it as it crashes? (You can set the JIT debugger via the registry here: http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx)

Good luck!

---

It turned out that my application uses a control that does not run on 64-bit environments.

Apparently, the debugger in VS2008 will not throw an error whenever one of these old style DLLs fails.