Vault on an IIS 5.0 Web Garden

Grant Henderson · Post by **Grant Henderson** » Thu Sep 30, 2004 7:16 pm

Hi,

I recently enabled a Web Garden on our multiprocessor development server using the machine.config <processModel> section. I also changed the Vault web.config file session state property to use a StateServer.

All of our ASP.NET applications work except Vault which is hosted on the same development machine. I receive an "encryption" error when I try to access vault using an SSL connection (sorry, don't have the exact error handy). I haven't tried non-SSL as most of our Vault access is remote and requires SSL.

We are running IIS 5.0 - switching to Win2003 and IIS 6.0 is not an option at this time.

Can anyone provide any insight into this problem? Any solutions / workarounds would be appreciated.

Regards,

Grant Henderson.

lbauer · Post by **lbauer** » Fri Oct 01, 2004 1:16 pm

From a Google search:

When you implement web gardens, each of the asp.net processes has its
processor affinity assigned to a specific processor. This can result in
sessions values appearing lost, or empty.

Perhaps this is causing a problem for Vault. We haven't tested it on a web farm or garden.

Try connecting on the LAN without SSL so we know it's not an SSL issue.
If you can't connect, what is the exact error message?

gph · Post by **gph** » Sun Oct 03, 2004 5:16 am

Hi Linda,

I re-enabled the web garden and connected to it with the Vault Client on the same machine. The error I receive is a dialogue box with the message:

Encryption failure(FailEncryption).

Clicking OK returns me to the Vault Client "Connect to Server" dialogue. This error occurs regardless of whether SSL is enabled or not.

A web garden essentially runs an aspnet_wp.exe process on each CPU. (4 CPU's = 4 aspnet_wp.exe processes). Therefore, it's a requirement that StateServer or SQL StateServer be used to share session info between applications. This is the same configuration as found in a web farm of clustered web servers - simply on a single machine.

I set the vault web.config file to use StateServer but this doesn't fix the problem. I'm guessing that Vault server initialises some kind of Application variable for encryption that can't be shared between multiple server instances - just a hunch.

lbauer · Post by **lbauer** » Sun Oct 03, 2004 7:37 pm

You could see if the standard troubleshooting for this type of error might work for you:

http://support.sourcegear.com/viewtopic.php?t=1449

gph · Post by **gph** » Tue Oct 05, 2004 6:28 am

I tried the various crypto fixes/suggestions without luck.

Below is a dump of the server log file. Take note of the "Object reference not set to an instance of an object" error. "SSL Disabled" seems to appear regardless of whether I enable or disable SSL when connecting from the client - very odd.

----2004-10-05 10:12:35 PM sgvaultsystem--()--
System Started
Version 2.0.5.2210
Cache Level = 1
DataBase Buffer Size = 256
LogFile Path = C:\WINNT\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINNT\Temp
----2004-10-05 10:12:37 PM grant--redcone-001(10.0.200.4)--SSL Disabled
Object reference not set to an instance of an object.
----2004-10-05 10:12:37 PM grant--redcone-001(10.0.200.4)--SSL Disabled
Login failed: FailEncryption