Geeks With Blogs

Tim Huffam Dotting the I and crossing the T of I.T. IIS
Error: Failed to access IIS metabase. Hosting WCF Service in IIS
This error ("Failed to access IIS metabase") can occur when you try to access your WCF when you have added for hosting within IIS. To solve this problem do this: Reregister ASP.NET for IIS: Open an Visual Studio Command Prompt (or a regular command prompt and cd into the .Net dir - usually: C:\WINNT\Microsoft.NET\Fram... then type: aspnet_regiis -i When complete, from the same command prompt run: iisreset Verify your IIS virtual/app dir is setup correctly (uses .Net 2). If you don't ......

Posted On Thursday, May 14, 2009 3:13 PM

php mysql extension not loading/Quick Install of a WIMP stack (PHP, MySQL, PHPMyAdmin on Windows XP and IIS)
On a fresh php installation (on WinXP using IIS 5) the mysql extension did not load. This turned out to be because php could not find the libmysql.dll library - to resolve just put the php dir (eg "c:\xampp\php) and the ext dir (c:\xampp\php\ext) into the PATH environment variable (and restart iis). To verify your php configuration, create a php file with the following content: <?php phpinfo(); ?> Save this as something like info.php into your web root dir and navigate to it with a browser ......

Posted On Wednesday, February 4, 2009 12:47 PM

ASP.NET error: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level
The following error occured because a web.config file existed, in a directory beneath my main app root dir, should not have been there: It is an error to use a section registered as allowDefinition='MachineToA... beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. C:\Dev\SVN\authenticationse... It is actually valid to have a web.config in a dir beneath your app ......

Posted On Tuesday, September 5, 2006 12:07 PM

Remote debugging with ASP.NET 2.0 - finding the process id (PID) of the worker process.
To start remote debugging an ASP.NET 2.0 app (assuming the app is up and running on the remote server): On the remote server start the Visual Studio 2005 Remote Debugger. For this you need to have the VS2005 Tools installed (not necessarily the full VS2005). On your local machine, within VS2005 select Debug - Attach to Process... In the Qualifier field (in the Attach to Process screen) enter the name of the remote server and press ENTER. Select the IIS worker process (w3wp.exe) that is running your ......

Posted On Tuesday, August 8, 2006 10:56 AM

Manually configure a web app dir for a specific version of the .NET framework
In some cases you may want or need to change the version of .NET that a particular web application directory uses. Normally this is done via the ASP.NET tab on the IIS properties page for the web app, however it can also be done manually at the command line... CD into the dir containing the version of .NET that you require eg: C:\WINDOWS\Microsoft.NET\Fr... Run aspnet_regiis.exe specifying the name of the dir you want this set against. eg aspnet_regiis.exe -s W3SVC/nnn/ROOT/xxx (where ......

Posted On Friday, August 4, 2006 12:24 PM

Error using client certs: The page requires a valid client certificate (403.13). How to turn off CRL checks in IIS.
The following error may occur when trying to use a client cert for the first time (this error is from IIS 5): The page requires a valid client certificate The page you are trying to view requires the use of a valid client certificate. Your client certificate was revoked, or the revocation status could not be determined. The certificate is used for authenticating you as a valid user of the resource. HTTP 403.13 - Forbidden: Client certificate revoked The cause of this is usually "the revocation status ......

Posted On Monday, June 12, 2006 9:57 AM

Error (m_safeCertContext is an invalid handle.) when accessing a client certificate using .NET 2.0/VS2005
This error (m_safeCertContext is an invalid handle.) occurs when you try to access a client cert (or a member of the cert) from a ASP.NET 2.0 application developed using VS2005 eg: X509Certificate cert = new X509Certificate(Request.Cli... certSerial = cert.GetSerialNumberString(); The error is thrown because no valid certificate is found. This can be caused by either: A problem with the cert. A common reason for this in a development environment is one of the cert properties ......

Posted On Tuesday, April 18, 2006 1:58 PM

Error: The underlying connection was closed: The remote name could not be resolved. When doing HttpRequest from ASP.NET.
The following error occured when trying to open a web page (ASP.NET) that was doing an HttpRequest. "The underlying connection was closed: The remote name could not be resolved." This is usually caused because the ASP.NET app is on a network that is using a proxy server - and as ASP.NET does not run as a user account, it does not have access to the proxy settings in the registry. To resolve add the following section to your web.config file. <defaultProxy> <proxy usesystemdefault = "false" ......

Posted On Thursday, February 9, 2006 9:20 AM

IE bug: HTTP POST with zero content-length (content-length = 0) (even though there is data in the post request)
This little gem comes to us courtesy of MS's IE, whereby it resets the connection and sets content-length to 0 (zero), even though there is data in the post request, when the keep-alive timeout expires. Fortunately this only occurs when using HTTPS, and apparently it's limited to a particular version of IE (although I'm not 100% convinced about this). This bug is documented very well here and by ibm here, and an typically difficult to understand MS solution here. Another solution I think may work ......

Posted On Thursday, January 26, 2006 2:35 PM

IIS error: The parameter is incorrect

This error occurs within IIS 6 when you try to start your web site and it has not been assigned to a valid application pool.

This usually happens when the default app pool has been deleted.





Posted On Friday, November 18, 2005 1:20 PM

Uninstall IE 7
Those of you wanting to know how to remove this annoying version on IE - click here. However, if you are as unfortunate as myself, and have had another user has install it (IE 7 beta) on your PC, then you will get this error: "Internet Explorer 7 Beta 1 cannot be uninstalled from this user account. Please log on to the same user account from which it was installed and try again." Even if you belong to the local administrators group. Brilliant! *** Update: For those of you wanting a far superior browser ......

Posted On Friday, September 16, 2005 12:14 PM

Copyright © Tim Huffam | Powered by: