iis-6

How to set ASP.NET version to 3.5 in the IIS 6 Default Web site properties (ASP.NET tab)? From what I can see was version 2 (even though I have install version .NET 3.5) You cannot specify this in IIS. For websites earlier than Framework 4.0 and greater than 2.0 you need to specify version 2.0 in IIS. However there are configurations in web.config to restrict a website to run or compile under framework version 3.5. Visual Studio by default make these setting in web.config To be sure here are some parts of the web.config There isn't a true "ASP.NET 3.5". "ASP.NET 3.5" is really "ASP.NET 2.0"

I have custom errors configured in my web.config, but IIS 6.0 is returning the custom error specified in the Custom Errors tab of the website configuration. <system.web> <customErrors> <error statusCode="404" redirect="UrlRedirect.aspx" /> </customErrors> </system.web> What can I be missing? Bear in mind that the 404 handler specified in the web.config only kicks in for files handled by the ASP.NET runtime - .htm, images, css, javascript will all be handled by the 404 page specified in your hosts IIS settings. If you want these file types to be handled by your custom error, you'll need to set

I want to list all virtual directories that belong to a web site with a certain name using WMI and PowerShell. I know I can list all virtual directories on a server using the code below, but how can I filter out only those that belong to a specific site? Get-WmiObject IIsWebVirtualDir -namespace "ROOT\MicrosoftIISv2" Well, taking the simplest approach here and filtering based on the properties returned from your given example, I would probably opt to use the site identifier portion in the Name property: Get-WmiObject IIsWebVirtualDir -namespace "ROOT\MicrosoftIISv2" | ` Where-Object { $_.name

Getting this error on an intranet application we have running in our development environment, and I'm not sure where to go/look for a solution. The application used to work fine, however it is run on a shared server with another team of developers and we're having trouble tracking down the error (no updates were made to the application by my team, it suddenly stopped working). We're running Windows Server 2003 and IIS 6.0. If I open the solution on my machine, however, I receive an error in Visual Studio solution points to this line in the web.config, however I believe this is a relatively

Creating a WCF Service Library in Visual Studio 2008 on Vista x64 is troublesome when referencing an x86 DLL. A service that calls a 32-bit DLL is required to have a platform target of x86 to run on a 64-bit OS. When you do this, the WcfSvcHost throws a BadImageFormatException when you attempt to debug the service. There is a bug report on MS connect. The workaround I used was to coreflag WcfSvcHost as 32-bit . Manifest Problem The main issue I've run in to is this third-party native 32-bit DLL fails to load using certain WCF hosts. I receive the following error when a service operation is

I'm seeing the following errors in my PHP error logs: PHP Fatal error: Maximum execution time of 60 seconds exceeded in D:\sites\s105504\www\index.php on line 3 PHP Fatal error: Maximum execution time of 60 seconds exceeded in D:\sites\s105504\www\search.php on line 4 The lines in question are: index.php: 01 <?php 02 session_start(); 03 ob_start(); 04 error_reporting(E_All); 05 $_SESSION['nav'] = "range"; // <-- Error generated here search.php 01 <?php 02 03 session_start(); 04 $_SESSION['nav'] = "range"; 05 $_SESSION['navselected'] = 21; // <-- Error generated here Would it really take as

I can't seem to receive HTTP OPTIONS requests in my IIS6 hosted ASP.NET application. I'm testing it using a debug breakpoint (and file-log) in my Global.asax 's Application_BeginRequest method. The breakpoint is never hit and the client gets a HTTP 403 Forbidden, I'm assuming from IIS6 directly ( GET s and POST s work fine btw). I've tried several things in the web.config , including adding the following line to either and both the <system.webServer><handlers> and <system.web><httpHandlers> sections. <add name="OptionsHandler" verb="OPTIONS" path="*" type="System.Web.DefaultHttpHandler"/> I've

I'm deploying an ASP.NET MVC site to a IIS6 webserver, so I'm using a default.aspx/{controller}/{action} style routing strategy. However, for some reason it doesn't really work when using the default.aspx part. No matter the url, it always gets the default action (Index) on the default controller (Public). I've been using the excellent Routing Debugger to see what's going on. route fail http://img169.yfrog.com/img169/7532/routefail.gif As you can see I'm requesting default.aspx/contact , which should match the 3rd route in the table. Actually ANYTHING I write after default.aspx/ matches the