We have a 2 server NLB setup with Session State stored in SQL Server so that a failover can be transparent to the user. (1) Is it necessary to have identically named application pools on each node? I thought that was necessary, but I cannot find documentation
to confirm. What is the best practice for the naming convention? (2) Also, we set the application identity to be a Domain user. There was issue accessing C:\Inetpub\temp (We had DFS replication of Inetpub, and was wondering whether replication of C:\Inetpub\temp
caused locking issues. A remedy I tried was for each application pool was to set load user profile to true. Would this solve the problem? Below is the error we were seeing: The worker process for application pool 'ASP.Net v2.0 Integrated' encountered an error
'Cannot read configuration file' trying to read configuration data from file '\\?\C:\inetpub\temp\apppools\ASP.Net v2.0 Integrated\ASP.Net v2.0 Integrated.config', line number '0'. The data field contains the error code. Thank you very much!
This is a pretty detailed article I know off on IIS and Failover Clustering... http://support.microsoft.com/kb/970759 These might help as well: http://learn.iis.net/page.aspx/213/network-load-balancing http://learn.iis.net/page.aspx/511/achieving-high-availability-and-scalability---arr-and-nlb/
Marked as answer by Lloydz on Jan 23, 2012 01:59 AM
isitiis
1 Post
Setting up IIS 7.5 in NLB (SQL Server 2008 R2)
Jan 16, 2012 02:20 AM|LINK
NLB IIS 7 Cannot read configuration file Application Pools DFS Replication
ma_khan
869 Posts
MVP
Moderator
Re: Setting up IIS 7.5 in NLB (SQL Server 2008 R2)
Jan 17, 2012 08:57 AM|LINK