Question

I host my fogbugz application on IIS 6.0, Windows Server 2003. And I want to host another ASP.NET application ( more specifically, it's ASP.NET MVC) application on the same machine.

So I open up my IIS Manager, click on the default website, new a virtual directory and point the path to my ASP.NET MVC application, and setup everything.

The name of my ASP.NET MVC application is OhMyMVC. And this is a snapshot of my IIS configuration:

The problem is that when I want to test my site ( by typing in http://localhost/ohmymvc), I will get a "could not load file or assembly 'fogbugz' or one of its dependencies" at the web.config, line 47:

Server Error in '/OhMyMVC'

Application.

Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'FogBugz' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 45: Line 46: Line 47: Line 48: Line 49:

Source File: C:\Program Files\FogBugz\website\web.config
Line: 47

Assembly Load Trace: The following information can be helpful to determine why the assembly 'FogBugz' could not be loaded.

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

-------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082

It seems that all of the requests to the Windows Server 2003 are intercepted by fogbugz web.config, any idea on how to solve this issue?

Edit: I tried to set the Application Pool to PBSAppPool and DefaultAppPool, and yet the same problem persists. Restarting the machine didn't help

Answer 1

Try changing the Application pool to something other than the FogBugz one (you could pick the default pool, for example).

See also How Application Pools Work (IIS 6.0) and Creating Application Pools in IIS 6.0.