Last week I installed IXIA Endpoint on my PC for the sake of some network benchmark test done by our network support contractor. A couple of days later I noticed weird behavior accessing shared files from one of our server. Only my workstation has sporadic problems accessing files (SMB as well as RDP protocol) on single server. IXIA endpoint was my first suspect because I allowed IXIA install program to change my TCP/IP settings. De-installing IXIA endpoint didn’t help and neither updating Windows XP with the latest hot fixes. Partly due to the time pressure I gave up with troubleshooting and decided to simply reset TCP/IP settings according to Microsoft support Article 299357.

Simple netsh command followed by reboot did the trick:

cmd> netsh int ip reset resetlog.txt


The problem seemed to go away. In resetlog.txt netsh writes every registry key or value that was either reset, added or deleted. Another Microsoft article worth having among bookmarks when you need to troubleshoot network connections is How to troubleshoot TCP/IP connectivity with Windows XP.

During some tests done with ORION (10.2.0.1) on IBM x3950 server attached to IBM DS80000, I manage to repeatedly crash the server. It usually crashed at the end of 14h long test with ORION running in advanced mode. I decided to run Windows Update and install all fixes on top of Windows 2003 x64 SP2, plus update IBM Subsystem Device Driver Device Specific Module (SDDDSM) from version 2.1.3.0-1 to 2.4.1.2-2. Without a machine type number it’s close to mission impossible to find the driver on IBM web site. I guess they rearrange the site to be worse than it was a year ago when I needed SDDDSM. That’s the reason why I wrote down this note with the link to download section.

I was experimenting with sqlplus -prelim option, trying to “bypass” connect / as sysdba part from command sequence by launching sqlplus under System account (the same account Oracle service is running under). The problem was that I was working remotely within Remote Desktop session, so an old trick:


cmd> at 12:00 /interactive cmd.exe


didn’t work. You have to seat at console to see the command prompt interactively.

A quick search on net revealed a quick fix for the problem:


cmd> psexec -i -s cmd.exe


Resulting in command prompt that runs under System account:

PsExec v1.72 - Execute processes remotely
Copyright (C) 2001-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

C:\WINDOWS\system32>


You can download the latest psexec version from:
http://live.sysinternals.com/

In the Late August 2009 issue of the newsletter Mark Minasi recommended free ISO mounting utility for Windows x86 and x64, freeware by SlySoft, Virtual CloneDrive. Until now I was using Microsoft Virtual CD-ROM. I can’t say I was disappointed by Virtual CD-ROM but on the other hand I didn’t use it on Windows x64 where (according to Mark Minasi) it doesn’t work reliably. Anyway, Slysoft freeware looks more polished and will likely replace Microsoft Virtual CD-ROM on my desktop.

DebugDiag is Microsoft diagnostic tool for troubleshooting process crashes, hangs and high memory usage.

See introduction article, written by Michael Morales (a senior escalation engineer for Microsoft’s Global Escalation Services team) in December 2008 issue of Windows IT Pro magazine, InstantDocID# 100577, for details on how to use this tool.

At the moment I’m investigating “weird” Oracle service crash on Windows 2003 x64 (hopefully non-production server) that occurs more or less at the same time every day. What makes troubleshooting this case interesting is a complete lack of any trace files by Oracle. Nothing in alert.log, bdum, udump etc.
I knew that using some OS debug tool is my only hope to narrow down the cause for the service crash.

As a longtime subscriber on Windows IT Pro Magazine, I was well aware of the great articles written by Mr. Morales, so it was not hard to find one with DebugDiag description.

The only version that I found on Microsoft site was Debug Diagnostic Tool v1.1, which unfortunately supports only Windows x86. Somehow discouraged I sent an email to Mr. Morales asking if there is any plans to port this tool to Windows x64. He made my day by promptly replying the link to IIS Diagnostic Toolkit 1.0, part of which is also DebugDiag. At the time of writing this note this is the latest release for Windows x64 and documentation can be found here.