1

Looking for suggestions for a method of capturing a memory dump while a user is running under terminal services. I have tried using "AdPlus" with WinDbg but the application runs under terminal services and it doesn't seem to like that combination.

This is a VB.NET application.

My question is similar to Tool for analyzing .NET app memory dumps but needs to allow the application to run under terminal services with no external dialogs. I tried WinDbg in quiet mode, but it crashes the session.

Community
  • 1
  • 1
user62572
  • 1,388
  • 2
  • 15
  • 24
  • Is the application crashing, hanging or in normal state at the time you want the memory dump? – Thomas Weller Nov 05 '13 at 14:55
  • Possible duplicate of [How do I take a good crash dump for .NET?](http://stackoverflow.com/questions/24874027/how-do-i-take-a-good-crash-dump-for-net) – Thomas Weller Mar 21 '17 at 18:37

2 Answers2

3

adplus should work fine under terminal services -- we use it that way frequently. How exactly are you trying to use it.

One thing to watch out for with terminal service sessions is if the session itself has an idle timeout. We often had customer attached adplus to our service via a terminal services section and then wonder why the service died an hour later. The solution to this was to force the terminal service connection to use the console session (/console on the command line for mstsc).

Rob Walker
  • 46,588
  • 15
  • 99
  • 136
  • Nothing out of the ordinary. In a batch file started on logon - 'adplus -crash -quiet -dbg windbg.exe -sc XXXXXX.exe' Perhaps it's windbg that it doesn't like. – user62572 Feb 09 '09 at 01:45
0

Because adplus runs from the command line, if you logout or a terminal services session times-out the script will stop.

One possibility to consider is using DebugDiag, it runs as a service as “Local System” so it’s not dependent on the logged on interactive user session.

You can configure the service to schedule memory dumps periodically and view/analyse the results later in another component of DebugDiag, all customizable via scripts.

Helpful links and download:

http://blogs.msdn.com/sukeshak/pages/ddintro.aspx

http://blogs.msdn.com/tess/archive/2009/01/23/net-hang-analyzing-debug-diag-output.aspx

http://www.microsoft.com/downloadS/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en

Peter McG
  • 18,857
  • 8
  • 45
  • 53