OS: Windows Server 2003 R2 SP2. One of our program received error from "Dr Watson". In the Application event log, the error was, Reporting queued error: faulting application apclient.bin.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x000417df How should I proceed to find out the cause of the problem.

Hello,start with searching for apclient.bin.exe on the machine and see to which installed software it belongs. Then go on with the vendors website.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hi There, Thank you for posting in windows server forums As a quick check please follow meinolf suggestion as you are able to get the faulting module the issue might be related to the 3rd party application dll / exe which got exceptioned either because of accessing invalid memory address or page , or there might be buffer overflow .If you want to know the root cause of the crash issue , we need to analyze the crash dump file. I would suggest that you contact Microsoft Customer Support service to troubleshoot this issue efficiently. They are the best resource for this kind of issues. You may obtain the phone numbers for specific technology request please take a look at the web site listed below: https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1 Hope the issue will be resolved soon.

Hi Luke,In addition to Sainath and Meinolf's suggestion, you may check the Drwtsn32.log file which is under drive:\Documents and Settings\All Users.WINNT\Application Data\Microsoft\Dr Watson.For more information about how to check Dr Watson logs, please refer to:Description of the Dr. Watson for Windows (Drwtsn32.exe) Toolhttp://support.microsoft.com/kb/308538How to disable Dr. Watson for Windowshttp://support.microsoft.com/kb/188296In addition, the apclient.bin.exe seems to be a file related to AlarmPoint. Has AlarmPiont agent been installed on the machine? If so, you may contact AlarmPoint support for better solution. http://www.alarmpoint.com http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1258613873805+28353475&threadId=1286282 Best Regards,Wilson Jia This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks guys.Sorry I didn't make it clear. The apclient.bin.exe is our program. It caused this problem.I'll start with the Drwtsn32.log.Thank you all.

Hi luke - ap ,make sure you configure drwtsn in interactive mode using the below command start --> run --> drwtsn32 -i and you will see a message " drwtsn32 is installed as default debugger " at this stage drwtsn will be waiting for any application crash and when there is any exception or a app crash you will see the corresponding dump generated automatically by drwtsn32 tool.after a crash you could just start drwtsn32 and check "application errors " for any user mode dump Note if your application is communicating with kernel and majority of the calls/ subroutines are made to the kernel then i would recommend you to configure complete memory dump .But if your application just does user mode access then either drwtsn32 or adplus will suffice your need.Please let us know if you need further information.