Service (written in C#) that insists on crashing when launched at system
boot time (see below on how to get this dump - I couldn't find any info
on how to do this).
Here's the stack trace from cordbg:
[thread 0x220] Unhandled exception generated: (0x04719c94)
<System.Runtime .Remoting.Remot ingException>
_className=<nul l>
_exceptionMetho d=<null>
_exceptionMetho dString=<null>
_message=(0x047 1b380) ".Config file
C:\WINNT\Micros oft.NET\Framewo rk\v1.1.4322\co nfig\machine.co nfig can not
be read successfully due to exception System.OutOfMem oryException:
Exception of type System.OutOfMem oryException was thrown.."
_innerException =<null>
_helpURL=<null>
_stackTrace=(0x 0471b6a0) array with dims=[48]
_stackTraceStri ng=<null>
_remoteStackTra ceString=<null>
_remoteStackInd ex=0x00000000
_HResult=0x8013 150b
_source=<null>
_xptrs=0x000000 00
_xcode=0xe0434f 4d
[007e] pop ebx
(cordbg) w
Thread 0x220 Current State:Normal
0)*
mscorlib!System .Runtime.Remoti ng.RemotingConf igHandler::Load ConfigurationFr omXmlFile
+007e [no source information available]
1)
mscorlib!System .Runtime.Remoti ng.RemotingConf igHandler::Load MachineConfigIf Necessary
+0091 [no source information available]
2) mscorlib!System .Runtime.Remoti ng.RemotingConf iguration::Conf igure
+0009 [no source information available]
3) (my application)
I've had problems with starting remoting from system services before and
I've actually stopped using it because I couldn't get it to start up
successfully, but I must have left a call to
RemotingConfigu ration.Configur e somewhere in my code. Is this a case of
my service actually depending on another service. If so, which one would
that be and why is it causing an OutOfMemoryExce ption when loading
machine.config? ??
Per Bergland
Carmenta AB
PS. Here's how to get a postmortem log from a .NET app. Should be in the
faq somewhere
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACH INE\SOFTWARE\Mi crosoft\.NETFra mework]
"DbgJITDebugLau nchSetting"=dwo rd:00000002
"DbgManagedDebu gger"="cmd /c \"C:\\Progra m Files\\Microsof t Visual
Studio .NET 2003\\SDK\\v1.1 \\Bin\\cordbg.e xe\" !a 0x%x !w !ex
c:\\temp\\cor dbg.log"
In my case I just installed the .NET 1.1 SDK, so the path to cordbg is
was actually something like
C:\\Program Files\\Microsof t .NET SDK 1.1 Bin\\Bin\\cordb g.exe