Hi,
I am trying to debug an application hang using adplus.exe to create a dump file and then using windbg to read the dump file. However, everytime I try to read the dump file using windbg, windbg fails to read the dump file, saying that the "dump file
may be corrupt or in a format not understood by the debugger, unspecified error". Does anyone have any suggestions on how to troubleshoot why adplus is creating corrupt dump files or why windbg thinks the dump file is corrupt?
I am running on Windows Server 2003 Service Pack 2, Adplus version 6.1, WinDbg version 6.12

Thanks.

Need to support users over the internet? click here try our remote control online beta

Hello,

Before analyzing the memory dump file, you will need to install the symbol files for the version of Windows that generated the dump file. This means, if the dump file is generated on a Windows 2008 x64 system and you would like to analyze it on a Windows
Server 2003 system, you have to install the symbol file for Windows 2008 x64.

Analyzing a User-Mode Dump File with WinDbg

http://msdn.microsoft.com/en-us/library/windows/hardware/ff538058(v=vs.85).aspx


If you have any further questions regarding the dump file debugging, please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Debugging is beyond what we can do in the forum.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:

http://support.microsoft.com/contactus

If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.

http://support.microsoft.com/contactus


Thanks
Zhang

There is an amazing pack of free network admin tools. click here to download it