Hi,

After much hassle I finally got DNN installed although not in the way it should be for our environment.

We run 2 Load Balanced Intranet servers for redundancy purposes - the intranet is used to access our ERP system so we cannot afford to have it go down without there being a backup. Out current intranet, which is asp based, is installed on a data server with both Intranet servers pointing to the virtual directusing using a hidden share.

It appears that this does not work with DNN, or more specifically, .NET! The virtual directory was pointing to \\BMDATA\BMGINTRANET$ and the system just would not work. As soon as I installed the system on the local server it worked!

Does anyone have any idea how to get around this problem?  I do not want to have DNN physically installed on both servers - it must be installed on a data server with both web servers pointing to the same path.

TIA

Campbell

I'm still having no joy in getting DNN 4.8.2 setup in a web farm environment. Essentially I have a directory share setup on our file server and will have 2 load balanced servers pointing to the share.

I have installed the DNN code on the file server and only setup the virtual directories on the 2 web servers. I have changed the webconfig to have webfarmsupport enabled as well as persistent cache. What confuses me is the MachineValidationKey setting which is set to

AutoGenerate,IsolateApp

but the config file clearly states that it should NOT be set to this if using web farms! So what do I set it to. The documentation is even more confusing as it says in Step 3 that all servers must have the same machinevalidationkey and machinedecryptionkey - how do I do that when the site is installed on a file sever and not on the local servers? There is only a single web.config file.

Confused!!! I am sure this is what is causing my problem as I cannot even get to the install page

when you first install dotnetnuke as part of the installation process we generate unique machinekey and validationkey for your site instance. For webfarms to work you need to ensure that these values are common across all your installs, typically you just do a simple copy of the first installation folder to your alternative nodes.

Cathal