JSI Tip 9075. How can I use DCOM error logging to troubleshoot DCOM problem in Windows Server 2003?

Windows Server 2003 supports enabling and disabling DCOM error logging.

I have scripted DCOMErr.bat to enable or disable DCOM error logging.

The syntax for using DCOMErr.bat is:

DCOMErr ON|OFF

Where ON specifies that you want to enable DCOM error logging, and OFF specifies that you want to disable DCOM error logging.

NOTE: After running DCOMErr.bat, you must restart the DCOM process that you want to effect. The DCOM process determines whether you have to restart the server.

DCOMErr.bat contains:

@echo off
setlocal
If \{%1\}==\{\} goto :err
if /i "%1" EQU "ON" set data=1&goto doit
if /i "%1" EQU "OFF" set data=0&goto doit
:err
@echo Syntax: DCOMErr ON^|OFF
endlocal
goto :EOF
:doit
set key="HKLM\SOFTWARE\Microsoft\Ole"
call :quiet>nul 2>&1
endlocal
goto :EOF
:quiet
reg add %key% /V ActivationFailureLoggingLevel /T REG_DWORD /F /D %data%
reg add %key% /V CallFailureLoggingLevel /T REG_DWORD /F /D %data%



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish