Richard Marr's Blog

Winhttp Tracing Options for Troubleshooting with Application Request Routing

richma — Fri, 24 Aug 2012 22:59:00 GMT

In my earlier blog “ 502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR) “ I referenced links for gathering Winhttp tracing for troubleshooting 502.3 issues.

Since there are multiple ways to gather this in the Windows 2008 and 2008R2 I thought this might be helpful to outline this for the different platforms and how to gather this for fellow ARR troubleshooters.

Windows 2008

1. Start the Tracing . From a command prompt run the following command:

netsh winhttp set tracing trace-file-prefix="C:\TEMP\WinHttpLog" level=verbose format=hex state=enabled max-trace-file-size=1048576000

2.Recycle the IIS Application Pool.

3. Reproduce the issue.

4. Stop the Tracing. From a command prompt run the following command:

netsh winhttp set tracing state=disabled

5. Review the trace with Notepad or any Text editor.

NOTE: The Identity of the IIS application pool will require write access to the log location c:\Temp in this example:

This type of tracing is process bitness specific, so if you are looking at a 32 bit process running from 64 bit OS, you need to use: c:\windows\syswow64\cmd.exe, rather than using the regular 64 bit cmd.exe (start a run a cmd.exe)

Windows 2008 R2

Method 1

This method will output the Winhttp API calls , but not raw data for network communication. From a command prompt run the following command:

1. Start the tracing

netsh winhttp set tracing trace-file-prefix="C:\Temp\Test3" level=verbose format=hex

netsh winhttp set tracing output=file max-trace-file-size=512000 state=enabled

2.Recycle the IIS Application Pool.

3. Reproduce the issue.

4. Stop the Tracing. From a command prompt run the following command:

netsh winhttp set tracing state=disabled

5. Review the trace with Notepad or any Text editor.

NOTE: The Identity of the IIS application pool will require write access to the log location c:\Temp in this example:

Method 2

To get the raw data communication at network layer and the Winhttp Api calls.

1. Start the tracing: From a command prompt run the following command:

netsh trace start scenario=InternetClient capture=yes report=yes

Note the etl file location for example:

Trace File: C:\Users\<your user name>\AppData\Local\Temp\NetTraces\NetTrace.etl

2.Recycle the IIS Application Pool.

3. Reproduce the issue.

4. Stop the tracing: From a command prompt run the following command:

netsh trace stop

5. Read the Trace by opening it in Netmon 3.4.

Method 3

The ETW format for winhttp API is available on windows 2008 R2 and win7 via the Event Viewer

1. Open event viewer. Go to “View” menu --> make sure “Show Analytic and debug logs” is checked.

2. Open “Applications and Services logs” -- > Open “Microsoft” -- > Open “Windows –> Winhttp –> Diagnostic.

3. Highlight “Diagnostic” under Winhttp tree and right click mouse, then click “enable log”.

4. Reproduce the issue then you can review the logs.

References

Netsh Commands for Network Trace in Windows Server 2008 R2 and Windows 7

http://technet.microsoft.com/en-us/library/dd878517(v=WS.10).aspx

Overview of Application Request Routing’s Health Check features

richma — Tue, 14 Dec 2010 05:14:00 GMT

I had a recent question about the ARR health check features which resulted in this overview. Hopefully this is helpful to those of you setting up new ARR deployments.

URL TEST Feature

The URL Test feature tests against a specified URL for the following conditions. If any of the conditions fail the server that failed the test will be taken offline.

A response was received within the configured timeout period
The HTTP status meets the configured acceptable status codes
The body of the response contains the specified text configured in the response match.

If the URL is set to the FQDN of the ARR server then the tests will be performed against all servers configured in the farm.

Servers can be either brought online manually or when the URL test determines the server is healthy again after then next successful test run.

As this feature is limited to only one URL it is recommended to create a smoke test page that is a representation of overall health of the server. ARR can be further configured to look for specific words in the response entity body, so that the results of the smoke test can be taken into the consideration for determining the health.

The feature is disabled if there is no URL present in the dialog.

UI Settings	Configuration Attribute	Description
URL	<attribute name="url" type="string"/>	URL of content you want to perform the check against. Since the test is designed to read the contents of the response, a text file is sufficient. i.e. http://(server/ name or FQDN of ARR server)/healthCheck.txt
Interval	<attribute name="interval" type="timeSpan" defaultValue="00:00:30" validationType="timeSpanRange" validationParameter="0,86400,1"/>	How often the test is performed
Time-out(seconds)	<attribute name="timeout" type="timeSpan" defaultValue="00:00:30" validationType="timeSpanRange" validationParameter="1,86400,1"/>	Configurable timeout period to receive a valid response.
Acceptable status codes	<attribute name="statusCodeMatch" type="string" defaultValue="200-399"/>	Range of acceptable HTTP status codes that signify success.
Response Match	<attribute name=”responseMatch” type=”string” caseSensitive=”true”/>	String that will be contained in the body of the successfully response. If the string “Healthy” was entered here the response body must contain this string.

Live Traffic Test (enabled by default)

Will mark a server unhealthy if the following conditions are met.

If the HTTP response matches the configured failure code range as configured by liveTrafficFailureCodes
And If there are X # of failures as configured by maxLiveTrafficFailures
And if the # of failures occur during the configured time per liveTrafficFailurePeriod.

To disable the feature set the Failover period to 0.

UI Settings	Configuration Attribute	Description
Failure Codes	<attribute name="liveTrafficFailureCodes" type="string" defaultValue="500-"/>	Range of Http status codes that signify failure.
Maximum Live Traffic Failures:	<attribute name="maxLiveTrafficFailures" type="uint" defaultValue="10" validationType="integerRange" validationParameter="1,4294967295"/>	Specifies the maximum number of failures that are allowed during the failover period.
Failover period (seconds)	<attribute name="liveTrafficFailurePeriod" type="timeSpan" defaultValue="00:00:00" validationType="timeSpanRange" validationParameter="0,86400,1"/>	Specifies the failover period in seconds. To disable the Live Traffic test, set this value to 0.
Minimum Servers	<attribute name="minServers" type="uint" defaultValue="0"/>	Set as a percentage of Healthy servers. When the number of healthy servers drops below this number the following takes place. An Event is raised and logged to the event viewer Requests are route to all servers regardless of their status except for servers that were taken offline manually.

What happens if all Servers are offline?

The user will receive the following error in the browser:

Failed Request Tracing logs will log the error and reason below.

Summary

When setting up your environment its important to note that the URL Test feature can be used to both mark a server to unhealthy as well as healthy ,while the Live Traffic test is only used to mark a server as unhealthy.

The reason for this is that the URL test has no user impact and there is no risk to the user experience. If you experience transient outages where you want to recover via health checking features it would be recommended to use a combination of both the Live Traffic and the URL test. If you want to failed servers to stay offline until some administrator action then just use the Live Traffic test.

References

ARR Health Test Page

Verify URL Test Dialog Box

Monitoring and Management Page

502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR)

richma — Sat, 03 Jul 2010 16:38:00 GMT

When working with ARR deployments one of the errors you might see is 502.3 Bad Gateway. The 502.3 means while acting as a proxy ARR was unable to complete the request to the upstream server and subsequently send a response back to the client. This can happen for multiple reasons including , failure to connect to the server , no response from the server, or server took too long to respond (time out).

For the purposes of this post we are going to look at a timeout error and the data that can be gathered to help isolate the cause.

If you are looking at this post then you probably have already seen this error or something similar. This is shown in the browser when detailed errors are enabled in IIS.

Another way to identify the source of the 502.3 is with Failed Request Tracing logs in IIS configured to capture Status code 502.

From the message the key details are the ErrorCode which you can use to map to to the Winhttp error message, which in this case is ERROR_WINHTTP_TIMEOUT ( Reference WinHttp Error Codes). You will also see in the next line that this is translated to “The operation timed out”. Note that both the 0x80072ee2 and 2147954402 map to the same error ERROR_WINHTTP_TIMEOUT.

Now that we know its a timeout we need to determine what type of timeout occurred. Here is a list of the timeouts that can occur in Winhttp ( which if you haven't guessed already is what ARR uses to proxy requests)

ResolveTimeout : This occurs if name resolution takes longer than the specified timeout period.
ConnectTimeout : This occurs if it takes longer than the specified timeout period to connect to the server after the name resolved.
SendTimeout : If sending a request takes longer than this time-out value, the send is canceled.
ReceiveTimeout : If a response takes longer than this time-out value, the request is canceled.

To identify what type of timeout we can use Winhttp’s built in logging,These can be enabled from the command line on the ARR server using NETSH.

Winhttp Traces:

Following the example below you can search your log for WinHttpOpenRequest to find your request. The calls to WinHttpSetTimeouts are setting the 4 timeout values based on your ARR time settings found in the Proxy Configuration page of your ARR Server Farm or in the Server Proxy settings. Next we find WinHttpSendRequest then WinHttpReceiveResponse , so we know we are now in the receive stage. Finally we see that the error in is in RecvResponse so we know this is a ReceiveTimeout. For a different failure such as ResolveTimeout we would not see the log make it to WinHttpReceiveResponse and the failure would be logged earlier.

10:23:45.100 ::WinHttpOpenRequest(0x35a970, "GET", "/sleep/default.aspx", "HTTP/1.0", "", 0x0, 0x00000080)
 …………
10:23:45.100 ::WinHttpSetTimeouts(0x2e42d80, 30000, 30000, 30000, 30000)
10:23:45.100 ::WinHttpSetTimeouts() returning TRUE
…………

10:23:45.100 ::WinHttpSendRequest(0x2e42d80, "Accept: */*\r\nAccept-Encoding: gzip, deflate\r\nAccept-Language: en-CA\r\nHost: contoso.com", 479, 0x0, 0, 0, 24794c0)
…………

10:24:15.397 ::Completing WinHttpSendRequest() with success; Request Handle = 02E42D80, Context = 024794C0, Buffer = 00000000 (0x0), Buffer Length = 0
10:24:15.397 ::WinHttpReceiveResponse(0x2e42d80, 0x0)
………… 
10:24:15.397 ::sys-recver failed to receive headers; error = ? (1460)
10:24:15.397 ::ERROR_WINHTTP_FROM_WIN32 mapped (?) 1460 to (ERROR_WINHTTP_TIMEOUT) 12002
10:24:15.397 ::sys-recver returning ERROR_WINHTTP_TIMEOUT (12002) from RecvResponse()
10:24:15.397 ::sys-req completes recv-headers inline (sync); error = ERROR_WINHTTP_TIMEOUT (12002)

Now that we know this is receive timeout we can look at the content server and see how long the request took.

IIS logs on the Content Server:

Examine the IIS logs on the content server and check the sc-status and sc-win32-status and time-taken fields. This will give you an idea of whether the request processed successfully ( sc-status = 200) and the time-taken to see if this exceeds your ARR timeout and if this is the expected execution time for your web page . You can determine from this whether you need to troubleshoot a long running application or simply increase the ARR timeout settings. Checking the Win32 field for errors such as 1236 (ERROR_CONNECTION_ABORTED) or 64 (ERROR_NETNAME_DELETED) indicate that something happened on the network layer such as a connection reset.

Using our example the IIS logs here show that the Request took ~35 seconds (time-taken=35615) , the request was processed successfully on the server (sc-status=200) , but there was a problem sending the request (sc-win32-status=64) which means the connection was gone when the content server tried to send the request. This was because the client (ARR) has already timed-out and closed the TCP connection.

#Software: Microsoft Internet Information Services 7.0
#Version: 1.0
#Date: 2010-06-23 20:11:33
#Fields: 
date time            cs-method cs-uri-stem         s-port  sc-status sc-substatus sc-win32-status time-taken
2010-06-23 20:11:33  GET       /sleep/default.aspx 80      200       0            64               35615

Summary

So in this case we can see that the request took >35 seconds which is longer than the default timeout in ARR. When this occurs ARR ( or Winhttp underlying ARR) will close the connection to the content server which is what cause the Win32 error 64.

Now its up to you to determine whether its acceptable that your page is running for 35 seconds and you just need to increase time outs in ARR.

Since the application issues are beyond the scope of this blog I’ll leave you with two command lines for setting ARR timeouts for either a Server Proxy configuration or Server Farms.

Server Proxy : appcmd.exe set config -section:system.webServer/proxy /timeout:"00:00:45" /commit:apphost

Server Farm : appcmd.exe set config -section:webFarms /[name='ArrFarm'].applicationRequestRouting.protocol.timeout:"00:00:45" /commit:apphost

References

WinHttpSetTimeouts Function

Netsh Commands for Windows Hypertext Transfer Protocol (WINHTTP)

Failed Request Tracing in IIS (FREB)

UPDATE : New Post for Winhttp Tracing Methods

ARR on IIS.NET

Deleting IIS Web Sites, Applications and their Content with Web Deploy

richma — Sat, 03 Jul 2010 16:06:42 GMT

While supporting customers on the Web Platform Installer forums, a frequent question is “How do I uninstall or remove Web App Gallery applications?”. Since there is no MSI or installer package these are not added to the Windows Programs menu so how can we achieve this ?

The answer comes in the same tool used to install the package, the Web Deployment Tool ( Web Deploy).

When installed on IIS 7.0 or later Web Deploy adds a context menu item to IIS manager called Deploy.

There are multiple actions available here one of which is the Delete action. There are two options depending on what node you have selected in IIS manager:

Web site : Deploy >> Delete Web Site and Content
Application: Deploy >> Delete Application and Content

Once you have made the selection you will be warned that there is no recovery so make sure you BACK UP if you want to restore the information at another time.

And that’s all there is to it, the web site / application and associated content are now deleted. I hope you find this helpful!

Missing Failed Request Tracing (FREB) trace Areas ?

richma — Wed, 26 May 2010 15:24:33 GMT

I was recently working with a colleague to troubleshoot an issue using Application Request Routing (ARR) and wanted to use the trace areas provided by ARR to see the events this logged.

However, when we checked the FREB trace nothing for ARR was logged. How could this be if ARR is installed and all of the FREB selections were selected ?

After some research we found the problem lies in the installation order of the IIS Trace Feature and the IIS Extensions that extend the built in Trace areas. If the IIS Trace feature is installed after the extensions that extend the trace areas, the new areas are not added. This is because there is currently no detection or way to tell the Trace feature there are new items to add to the default list.

At the time of this post the only extensions that extend the trace areas are Application Request Routing and URL Rewrite but this could apply to future releases as well.

To verify if your are setup correctly, simply create a new or edit an existing FREB rule and check the WWW Server provider and you should see RequestRouting and Rewrite listed under the Areas as shown here.

You can also verify this in the Applicationhost.config file ( %windir%\System32\inetsrv\config\administration.config) where the trace providers and areas are defined.

<traceProviderDefinitions>
                <add name="WWW Server" guid="{3a2a4e84-4c21-4981-ae10-3fda0d9b0f83}">
                    <areas>
                        <clear />
                        <add name="Authentication" value="2" />
                        <add name="Security" value="4" />
                        <add name="Filter" value="8" />
                        <add name="StaticFile" value="16" />
                        <add name="CGI" value="32" />
                        <add name="Compression" value="64" />
                        <add name="Cache" value="128" />
                        <add name="RequestNotifications" value="256" />
                        <add name="Module" value="512" />
                        <add name="FastCGI" value="4096" />
                        <add name="Rewrite" value="1024" />
                        <add name="RequestRouting" value="2048" />
                    </areas>
                </add>
               ------------------------ Truncated for readability ----------------

            </traceProviderDefinitions>

Resolution

Either of the following options can be used to fix the issue.

a) Using Programs and Features find the Extension that is missing trace areas, right click select REPAIR.

b) Manually add the trace areas to the Applicationhost.config file as shown above.

PS . If you don't already use FREB its a great tool for analyzing general IIS issues along with ARR and URL Rewrite, and highly recommended. See the following for examples tracing ARR and URL Rewrite.

Using Failed Request Tracing to Trace Rewrite Rules

Using Failed Request Tracing Rules to Troubleshoot Application Request Routing (ARR)

Troubleshooting SQL Server 2008 Express installations with WebPI

richma — Thu, 29 Apr 2010 23:00:53 GMT

One of the challenges of troubleshooting SQL installations with WebPI is that sometimes the details passed back to Webpi do not provide enough information to tell you how to resolve the issue. This is not the fault of WebPi or the SQL installer, but due to the fact that not all of the errors are exposed to the external process(WebPI) therefore all we can report is that something failed. When this occurs you need to examine the SQL logs manually to find the details for the installation failure. In this blog we will help identify some of the common failures and provide the resolutions for each.

Where to find the Logs

When the installation fails you will be presented with the following error page.

The first “View log here” will point to the SQL Summary.txt log that provides a summary of the installation and results. At the top of the log there you will see Final result: Passed/Failed to indicate if there were a failure at this level. If the result is Passed then click on the “View log here” link for the Web Platform Installer log . If no error messages are found in either link then review SQL Logs manually.

Here are the log locations for manual inspection.

WebPI Logs

Windows Vista / 2008 : %localappdata%\Microsoft\Web Platform Installer\logs\webpi
Windows XP, W2K3: %USERPROFILE%\Local Settings\Application Data\Microsoft\Web Platform Installer\logs\webpi

SQL Installation Logs

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\

Resources

ERROR : Attributes do not match. Present attributes..

This can occur when you try to install SQL on a Drive with either Compression, Encryption or the Archive bit set.

This error will be found in the SQL log Summary.txt .

Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.

Exit code (Decimal): -2068578304

Exit facility code: 1204

Exit error code: 0

Exit message: Attributes do not match. Present attributes (Directory, Compressed) , included attributes (0), excluded attributes (Compressed, Encrypted).

Resolution

The work around for this error is documented in KB957453 which describes this problem when the archive bit is set on the installation directory. This can also occur when Compression or or Encryption is enabled on the drive , which will be C:\ if using WebPI to install SQL.

Following the workaround section of KB957453 disable the following settings on the drive.

- Folder is ready for archiving

- Compress contents to save disk space

- Encrypt contents to save disk space

ERROR: Unrecognized configuration section system.serviceModel

During the installation the installer tries to read the configuration file (Machine.Config) . If this is invalid the installation will fail. Below is one example of such a failure.

This error will be found in the SQL log Detail_GlobalRules.text

2010-03-29 16:17:24 Slp: Inner exception type: System.Configuration.ConfigurationErrorsException

2010-03-29 16:17:24 Slp: Message:

2010-03-29 16:17:24 Slp: Unrecognized configuration section system.serviceModel. (c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 134)

Resolution

This error occurs when there is a reference to the system.serviceModel section but it is not defined in the <configSections> area of the configuration file.

If you have access to a working Machine.Config file you can manually add the missing configuration declarations to the <configSections> area of he configuration file. The section groups may vary but if the error message is referring to system.ServiceModel you can add the following sections.

<sectionGroup name="system.serviceModel" type="System.ServiceModel.Configuration.ServiceModelSectionGroup, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="behaviors" type="System.ServiceModel.Configuration.BehaviorsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="bindings" type="System.ServiceModel.Configuration.BindingsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="client" type="System.ServiceModel.Configuration.ClientSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="comContracts" type="System.ServiceModel.Configuration.ComContractsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="commonBehaviors" type="System.ServiceModel.Configuration.CommonBehaviorsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly"/>
            <section name="diagnostics" type="System.ServiceModel.Configuration.DiagnosticSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="extensions" type="System.ServiceModel.Configuration.ExtensionsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="machineSettings" type="System.ServiceModel.Configuration.MachineSettingsSection, SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly"/>
            <section name="serviceHostingEnvironment" type="System.ServiceModel.Configuration.ServiceHostingEnvironmentSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="services" type="System.ServiceModel.Configuration.ServicesSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        </sectionGroup>

        <sectionGroup name="system.serviceModel.activation" type="System.ServiceModel.Activation.Configuration.ServiceModelActivationSectionGroup, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="diagnostics" type="System.ServiceModel.Activation.Configuration.DiagnosticSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="net.pipe" type="System.ServiceModel.Activation.Configuration.NetPipeSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
            <section name="net.tcp" type="System.ServiceModel.Activation.Configuration.NetTcpSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
        </sectionGroup>

Error: Performance counter registry hive consistency check "The performance counter registry hive is corrupted

I have seen two causes for the following error, either the performance counter libraries are corrupted and need to be repaired or an issue where the localized version of the performance counters are not present.

This error will be found in the SQL log Summary.txt .

Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal):           -2067922940
Exit facility code:            1214
Exit error code:               4
Exit message:                  The performance counter registry hive is corrupted. To continue, you must repair the performance counter registry hive. For more information, see http://support.microsoft.com/kb/300956.

Resolution

a) If you are running Windows Vista or later the following steps can be used to rebuild the counters.

Click Start>All Programs > Accessories.
Right-click Command Prompt, and then click Run as administrator.
At the command prompt, type lodctr /r, and then press ENTER.
Assuming the message was that this was successful , retry the SQL installation.
Reference : http://technet.microsoft.com/en-us/library/cc774958.aspx

b) For earlier operating systems follow the steps in Kb300956 listed in the error message.

c) If neither of the above resolve the issue and your and running a non-English version of Windows you may be running into the localization issue. The following steps outline the steps to resolve this on a German system that was encountering the issue.

To identify what key you need to alter on your system run Process Monitor while running the SQL installer. When the SQL installation fails check the Process Monitor logs for entries like the following where SomeNumber will represent the country code of the system that SQL is trying use for the performance counter. Use this number in place of 007 in the steps below.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\<SomeNumber>\Counter (NAME NOT FOUND)
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\<SomeNumber>\Help (NAME NOT FOUND)

Open RegEdit.exe and navigate to the following key. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib
Under this you will see the 009 and 007 keys . The 009 key is for English and the 007 is for German . ( In the case I encountered there were no values under 007)
Right Click on the 009 key and there will be an export option . Save that anywhere on your system
Go to the location of the file you saved which will have a .REG extension. Right Click on the file and select Edit.
In the first line you will see HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 . Change this too HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\007 so we can migrate these settings to the 007 key. Save the file.
Now right click on the file and select Merge.
Check the registry and you should see settings under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib\007
Try the SQL setup again

Here are some different country codes you may see when troubleshooting this.

Perflib\009 -- English
Perflib\01F -- Turkish
Perflib\013 -- Dutch
Perflib\007 – German

Perflib\014 -- Norwegian

Error: is not a valid login or you do not have permission

This error can occur when you the username that you are using to install SQL is the same as the name of the machine.

This error will be found in the SQL log Summary.txt .

Configuration error code: 0x12C2466D

Configuration error description: '' is not a valid login or you do not have permission.

Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100329_130529\Detail.txt

Resolution

Install SQL using another User account this is not the same as the machine name or rename you machine.

ERROR: Downloaded file failed signature verification and may have been tampered with.

This is typically a transient error that can occur when the download is corrupted.

The error will be found in the WebPI log WebPI.txt

DownloadManager Error: 0 : Signature verification failed on downloaded file. URL: http://download.microsoft.com/download/e/9/b/e9bcf5d7-2421-464f-94dc-0c694ba1b5a4/SQLEXPRADV_x86_ENU.exe.

Resolution

By default WebPI stores a copy of the installers for installation retries. In this case you will want to delete the cached copy and try downloading a new one.

The cache location of the installers can be found here : %LocalAppData%\Microsoft\Web Platform Installer\installers

If the problem persists using WebPI try downloading the installer directly from the link below then running the MSI directly.

http://blogs.msdn.com/sqlexpress/archive/2009/06/15/installing-sql-server-2008-guidance.aspx

ERROR: Wait on the Database Engine recovery handle failed

This error will be found in the SQL log Summary.txt .

Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

Per the error message further investigation of the SQLServer Error Log_<DateTimeStamp>.txt led to the following error.

2009-11-19 20:35:15.85 spid7s      Starting up database 'mssqlsystemresource'.
2009-11-19 20:35:16.59 spid7s      Error: 15209, Severity: 16, State: 1.
2009-11-19 20:35:16.59 spid7s      An error occurred during encryption.

Resolution

In this case the resolution was found in the following article:

The SQL Server service failed to start

http://support.microsoft.com/kb/920114

Here is another article that pertains the original error.

960781 Error message when you try to upgrade to SQL Server 2008: "Wait on the Database Engine recovery handle failed"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960781

Summary

I hope this was helpful in providing shortcut to any of your SQL Express installation issues with WebPI. If you have other issues or need assistance you can post your questions to the WEBPI support forum.

Installing Acquia Drupal on IIS using the Web Platform Installer

richma — Wed, 03 Mar 2010 17:57:47 GMT

Introduction

In the following walkthrough we will step through the installation of Acquia Drupal using the Web Platform Installer.

Installation

1. Launch the Web Platform Installer either from IIS Manager or Start > All Programs > Microsoft Web Platform Installer.

2. Click the Web Applications tab and the select Acquia Drupal . Click Install.

3. On the license Screen the following dependencies will be picked up , or omitted if you already have the feature installed. . The versions listed are current for the time the blog was drafted and are subject to change.

Dependencies.

Url Rewrite 1.1
MySQL Connector/Net 5.2
Php 5.2.12

Optional

Windows Cache Extension for Php 5.2
MySQL Windows Essential 5.1

4. Step 1 of 2: Enter your site Information.The next screen “Enter your site information” is where you will enter information about how you want to set up Acquia Drupal in IIS.

In the first option Web Site: you can choose any existing website such as “Default Web Site” or New Web Site.Depending on which option is chosen the following options will be available.

Choose an existing Website

Acquia Drupal application name: This can be left at the default “acquia-drupal” or enter a new name.

New Web Site

Acquia Drupal application name: Default “/” : The slash indicates the root of the website you are about to create.This can be left at default here since the application is already isolated by a different website.
Web Site Name: Accept the Default “acquia-drupal” or enter a new name .
Physical Path : Defines the physical Path of the web site in IIS and which is where the acquia-drupal application files are installed.

NOTE : The following 3 parameters make up the bindings for the IIS site. When creating additional sites one of these three parameters needs to be different than the default web site( or other existing sites). For example the Default Web Site is configured for All Unassigned IP’s and the default Port 80. In this configuration you would need to either change the Port or create a host header.

IP Address: Choose an IP address from the list or leave at all unassigned if you are going to use a unique port or Host name for the site..
Port: Default 80. Leave at default or changed to desired port.
Host Name : Enter a host name if you are differentiating by host headers.

5.On the Enter Application information screen you will enter application information for Acquia Drupal including Database information, application passwords .

Database : Choose your database : This cannot be changed and is set to MYSQL.
Create New database /Use an Existing database: If installing Acquia Drupal for the first time you will leave this at Create New Database. If using an existing database you will need to provide the Database User name and password that was created in previous installation.
Database Administrator : This defaults to “root” which is the default Admin account for MySQL. If you configured MySQL with another Admin account name, enter that here.
Database Administrator Password: Password for the account configured in the previous field.
Database User Name : Default “drupaluser” This can be configured to any name you wish. If you are connecting to an Existing Database you will use the name you configured in the first installation.
Database Password + Confirm: This is the password you will create for the account named in the previous field( i.e. drupaluser)
Database Server : Use Localhost for local MySQL installations.
Database Name : Default Drupal . This is the database name that will be added to your mySQL instance, you can accept the default or enter a new name.

6.When the installation is complete the following will be presented . Click on Launch Acquia Drupal to test the installation.

7. When you launch the site it will use the following address if you installed under the default web site: http://localhost/acquia-drupal/install.php . Then after completing some initialization task the browser will have this address: http://localhost/acquia-drupal/install.php?locale=&profile=acquia and you should see the following page. You are now ready to work with your Acquia Drupal application. For information regarding the application, documentation can be found here. http://acquia.com/documentation.

Support and other links

Acquia Support

IIS.Net Forums

Installing WordPress on IIS using the Web Platform Installer

richma — Wed, 30 Dec 2009 20:13:12 GMT

Introduction

In the following walkthrough we will step through the installation of WordPress using the Web Platform Installer (WebPi).

Installation

1. Launch the Web Platform Installer either from IIS Manager or Start > All Programs > Microsoft Web Platform Installer.

2. Click the Web Applications tab and the select WordPress. Click Install.

3. On the next screen you will be prompted to accept the license for the products you wish to install. This includes your WordPress selection along with associated dependencies. Optional items such as “Windows Cache Extensions 1.0 for PHP 5.2” can be removed by clicking the X icon next to the product name. For this example I will leave all of the items in place. Click I Accept to continue.

4. On the next dialog you will be prompted to provide a password for the MySQL administrator account “Root” . Enter a password of your choice and click Continue. This will be needed later when you install the database for Wordpress.

5. The next screen “Enter your site information” is where you will enter information about how you want to set up WordPress in IIS.

Choose an existing Website

Wordpress application name: This can be left at the default “wordpress” or enter a new name.

New Web Site

Wordpress application name: Default “/” : The slash indicates the root of the website you are about to create.This can be left at default here since the application is already isolated by a different website.
Web Site Name: Accept the Default “wordpress” or enter a new name .
Physical Path : Defines the physicalPath of the web site in IIS and will be where the WordPress application files are installed.
IP Address: Choose an IP address from the list or leave at all unassigned if you are going to use a unique port or Host name for the site..
Port: Default 80. Leave at default or changed to desired port.
Host Name : Enter a host name if you are differentiating by host headers.

For the purposes of this example I am choosing the “Default Web Site” and leaving the applicaiton name as “wordpress”. Click Continue

6. On the Enter Application information screen you will enter application information for Wordpress including Database information and application passwords .

Since this is a large dialog I have broken the screen shot in 2 pieces . Hopefully this makes it easier to follow.

Database : Choose your database : This cannot be changed and is set to MYSQL.
Create New database /Use an Existing database: If installing Wordpress for the first time you will leave this at Create New Database. If using an existing database you will need to provide the Database User name and password that was created during a previous installation.
Database Administrator : This defaults to “root” which the default Administrator account for MySQL which we configured earlier.
Database Administrator Password: Password for the account configured in the previous field. In a default setup this will be the password for the account “root”.
Database User Name : Default “wordpressuser” This can be configured to any name you wish.
Database Password + Confirm: This is the password you will create for the account named in the previous field.
Database Server : Use Localhost for local MySQL installations.
Database Name : Default wordpress . This is the database name that will be added to your MySQL instance, you can accept the default or enter a new name.

7. Unique Key Section of Dialog

The keys are used to strengthen each of the elements and are not something you need to remember. A reference to these settings can be found on the WordPress site under the Security section, See Security Keys .

The mappings to the Field name in the installer are as follows.

Unique Key for Passwords :AUTH_KEY
Unique Key for Secure Passwords: SECURE_AUTH_KEY&
Unique Key for Authentication : LOGGED_IN_KEY
Second Unique Key for Authentication : NONCE_KEY

To populate these I used the online Generator from Wordpress that will create 4 unique keys that can be used here. Note that if you use this just copy the Key value between the single quotes and shown in red below.

define('AUTH_KEY', 'fZIgr9W-p3eE&]Qdmb@N8 HW%6bfPW!a1aT{C%fAKeH+;_@K=4:}ip1Q[V+tD)+P');

Once this is completed click Continue.

8. When the installation is complete the following will be presented . Click on Launch WordPress to test the installation.

The URL this will use based on the settings above will be Http://localhost/wordpress/

9. If you see this the WordPress is up and running. For usage of WordPress I recommend visiting the Wordpress.org site .

Known Issues

MY SQL Connector/Net version conflicts

Currently we install MySQL Connector/Net version 5.2. If there is a later version the installation will fail with the following error.

Error

'MySQL Connector/Net 5.2' is Failure (Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.)

Resolution

Side by Side installations of the connections are not supported. To resolve this issue the Later version is the only workaround if using Web Platform Installer to install Wordpress. Alternatively you could install WordPress manually.

Url Rewrite Version conflicts

If UrlRewrite V2.0 is installed the installation will fail with the following error.

Error

'URL Rewrite 1.1' is Failure (A newer version of Microsoft URL Rewrite Module 1.1 for IIS 7 was found on this machine.)

Resolution

Uninstall UrlRewrite 2.0 and Reinstall WordPress.

Support and other links

WordPress.org Support

WordPress Installation FAQ

Web Platform Installer Forums

http://ruslany.net/tag/wordpress/

Richard Marr's Blog

Winhttp Tracing Options for Troubleshooting with Application Request Routing

Windows 2008

Windows 2008 R2

Method 1

Method 2

Method 3

References

Overview of Application Request Routing’s Health Check features

URL TEST Feature

UI Settings

Configuration Attribute

Description

Live Traffic Test (enabled by default)

UI Settings

Configuration Attribute

Description

Summary

References

502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR)

Deleting IIS Web Sites, Applications and their Content with Web Deploy

Missing Failed Request Tracing (FREB) trace Areas ?

Resolution

Troubleshooting SQL Server 2008 Express installations with WebPI

ERROR : Attributes do not match. Present attributes..

ERROR: Unrecognized configuration section system.serviceModel

Error: Performance counter registry hive consistency check "The performance counter registry hive is corrupted

Error: is not a valid login or you do not have permission

ERROR: Downloaded file failed signature verification and may have been tampered with.

ERROR: Wait on the Database Engine recovery handle failed

Summary

Installing Acquia Drupal on IIS using the Web Platform Installer

Introduction

Installation

Support and other links

Installing WordPress on IIS using the Web Platform Installer

Introduction

Installation

Known Issues

Support and other links