Wednesday, October 10, 2012

Getting the correct versions of .Net Framework for WinDbg

To debug a minidump of a .Net application created by Windows Error Reporting, it is essential that you have the correct version of the following 3 dll's
The correct version being the version of the .Net framework that the user was running at the time the minidump was generated. For example, if the minidump was created using the framework 2.0.50727.4971, then you need the 2.0.50727.4971 version of the dll's mentioned above to debug this. Chances are this is NOT the version you currently have on your machine, it may not even be a valid version for your OS (XP, Vista, 7, 8) or architecture (x86, x64). As far as I'm aware, there is no central repository where you can go an grab the correct version of these libraries from, so one has to attempt to find them the hard way.
The .Net framework is initially deployed with our application, however, it is regularly updated, once installed, by Windows Update, to ensure that security vulnerabilities and major defects are patched. If your application is only installed on a single server (or server farm), this is not really a challenge, however, if your application is installed as a desktop application on nearly quater of a million PC's world wide, finding the correct version of the framework requires some sleuthing skills, and a bit of luck. The first step is to try and find the Microsoft support knowledge base article that describes the update. To do this I've found the following query typed into google, usually gets the result you want.

.Net framework 2.0.50727.4971

It is usually the first hit, but it may be further down. Validate this by searching the resulting page (Ctrl+F) for the framework version (e.g. 2.0.50727.4971) and make sure SOS.dll one of the binaries with this version number.
Go to the download information section of this website and click on the provided link. This should take you to the Download Center page where you should see the following options
Click to download the architecture you require. This will download the .msu file for the update. You can use the command-line Expand utility to extract the files in this update package.
expand.exe -D .\Windows6.1-KB2604114-x86.msu
Will list all the files in the package, in this case there are 4,
.\windows6.1-kb2604114-x86.msu: Windows6.1-KB2604114-x86-pkgProperties.txt
.\windows6.1-kb2604114-x86.msu: Windows6.1-KB2604114-x86.xml
You want to extract the file to do this use
expand.exe .\Windows6.1-KB2604114-x86.msu .\
You can then use expand.exe to interrogate and extract the contents of this .cab file.
To extract the files you want use
expand.exe -F:sos.dll .\ .\
expand.exe -F:mscorwks.dll .\ .\
expand.exe -F:mscordacwks.dll .\ .\
Each of these statements will usually result in 2 folders named something like the following
You'll need to check both dll's and make sure you get the version you are after.
Simply copy these into a common folder, and you can then use the following windbg commands to set the exepath and load the correct sos.dll
.exepath+ C:\MyFrameworkFolder\fwx86_2.0.50727.4927
.load C:\MyFrameworkFolder\fwx86_2.0.50727.4927\sos.dll
Happy debugging.

Monday, September 17, 2012

Telstra’s Transparent Proxying

I am finding Telstras Transparent proxying a nightmare at the moment. I am trying to configure a Windows Azure SQL DB instance I have set up on a trial account I got from TechEd. Azure SQL database security is tied to your IP address. You can click “Manage” from the portal window to add your current IP address to the firewall rules, but then thanks to Telstra’s transparent proxying, when you connect with SQL Server Management Studio, you get a different IP address, and consequently can’t access SQL Server.

Anyone know of a solution to this, short of getting a fixed IP address and opening up the firewall to the world?

Friday, September 07, 2012

Thoughts on Gina’s $2 a day comment

I think there is a point where the ruling class become so arrogant and full of their own self importance that the “plebs” see their only logical course of action is full scale revolution. I don’t think we’re there yet, and as history has taught us, revolutions rarely succeed in doing more than replacing the head on the coin, but with Gina Rinehart’s latest comments, I feel we have inched one step closer to it. Indeed there are people in West Africa who will work for $2 a day. Many West African nations are struggling economically, and desperate people will do desperate things. Perhaps the global economy does need some re-adjustment, and maybe just, the “invisible hand” of the market can do something to address the great injustices of the world, but for Gina Rinehart to make the inference that Australians need to take severe pay-cuts just because her precious mining business is in danger of slowing down, makes it clear just how detached from reality she has become. You can almost hear “let them eat cake”. It is not the responsibility of the working class to fund the ruling classes lifestyle. If you can’t make your business profitable while being ethical to your workers and paying them a liveable wage that takes into account cultural and social standards, then you don’t deserve to be running a business. Perhaps if Gina was to spend time in West Africa working for $2 a day, she may have a little more sympathy. Even if she was forced for a few months to exist on an Australian un-skilled labourers wage, she may get the picture.