|
Windows 2003 Web Edition with SP1 and Transaction=required page directive issue.
by Steve Schofield
This article covers an issue I worked on when ASP and ASP.NET web pages use
the Transaction=required page directive. Here is a brief article that describes this The problem occurs if you
have the following setup. The machine has Windows 2003 Web Edition
installed with service pack 1 and the application pool is running as a custom
user not 'NETWORK SERVICE'. The 'NETWORK SERVICE' is the default
Application pool identity. It doesn't matter if the 'custom' user is in
the IIS_WPG group. This does work if the 'custom' user is in the local
Administrators and IIS_WPG groups. The problem had many parts. Web edition
SKU, DTC, the missing registry key and SP1. All I needed to do to resolve the
issue was add these two registry entries .
*Registry Entry 1
C:\>reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Cluster
Server"
*Registry Entry 2
C:\>reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Cluster
Server" /v ClusterInstallationState /d 1 /t REG_DWORD
Here is a brief summary of the process. The start of the problem in SP1
the 'sc manager' (services.exe) that spawsns processes was locked down for
security causing a non-admin user not being able to query services (network
service has rights). The second problem on the web edition build
clustering services code is not run when add/remove programs is run preventing
the registry keys from running. The third part was a transaction invokes
DTC to query the 'sc manager', if this does not have permission, it would try to
check to see if it was a clustered DTC instance and how it checks is the
registry key. Because of both errors, this is why it did not work
. This is a very unique situtaion but took working with PSS for a
few weeks to identify the root cause.
|
|