You are currently browsing the category archive for the ‘bug’ category.

I ran in to an interesting issue yesterday.  In an IIS 6 web server we have a website set to run ASP.NET 4.0.  I was configuring a virtual directory to run under ASP.NET 2.0 to run ScrewTurn Wiki. Our standard config has the DefaultAppPool configured with ASP.NET 2.0 applications which don’t require their own pool.  The wiki was running without issue.  I decided to put the wiki in it’s own pool for various other reasons.

So I proceeded to configure a new application pool templated from DefaultAppPool.  Once the new application pool was assigned to the virtual web I started noticing some strange behavior.  Anytime I requested a URL which didn’t include  a page name my get request would include the file eurl.axd.  For ScrewTurn this means everytime you request the main url, it says it cant find the page named eurl, very annoying.

I wrestled for a while trying to figure out why this was happening.  At first I didn’t realize it had to do with the new app pool.  After a some googling time I cam across a Microsoft article of .NET 4 breaking changes which contained the issue I ran into.  (Very strange, is down right now with an error screen…). To test this further I changed another running web application to this app pool (which was running under DefaultAppPool) and it did the same thing, looked for eurl.axd on the request.

The article can be found here: and explains why this is happening.  In a nutshell it has to do with the website running ASP.NET 4.0 and virtual webs running ASP.NET 2.0.

What I find very strange about this bug is that as long as I use the DefaultAppPool I don’t have this issue (and yes, the website itself has it’s own app pool).  I only experience the bug when a new app pool is created for the virtual web which is running ASP.NET 2.0.

keys: eurl, eurl.axd,

A new installation of VS2008 Team Edition said it was missing a dll.  Other methods I found to add the dll failed as the whole directory under c:\windows\WinSxS where the dll should be, was missing.  Perhaps I forgot something during the install; I went to Add/Remove programs and clicked the VS2008 installation.  After the installer, did this and that a dialog box poped up reading:

A problem has been encountered while loading the setup components

After clicking OK on the dialog the installer just closed.  This isn’t good, I thought to myself.

I found this post through google which fixed my issue

There is a critical hotfix (kb952241) which is creating this issue with Visual Studio 2008.  Removing this hotfix and rebooting my computer allowed me to successfully run the installer again.

For reference I have included the entry in Windows update for this hotfix.

Visual Studio 2008 Security Update for Microsoft Visual Studio 2008 (KB952241) Succeeded Saturday, November 01, 2008 Microsoft Update

Not sure if I will be prompted again to load the hot fix (I am sure I will) or how sever the security hole is that this is suppose to fix.

As always, I hope this helps one other out there.  If you have any further information about this issue, please put in the comments and I may add it to the post.

Update: Now of course Windows Update wants to load the hotfix every day I boot up.  I an not sure if I want to load it again for obvious reasons.

4/1/2010: I am loading my new Windows 7 computer and much after loading VS2008 and SP1, I realized I failed to load unit test support (Doh!).  When I went to load the feature in VS2008, I received a similar error as before.  The difference this time, the hot fix isn’t on my system, its now incorporated into SP1.

To fix this issue and let me select new features in vs2008:

  1. I had to remove VS 2008 SP1
  2. Update the features using VS 2008 installer
  3. Reload SP1.

A pain in the ass, but it does work.

To remove VS2008 SP1, go to Programs and Feature (or Add/Remove Programs) and click View installed updates. You will find it listed in here, and uninstall it from here.

%d bloggers like this: