Still trying to install dotnetnuke 4.09.01 on a remote server.
I'm currently getting this error.
Line 87: <system.web>
Line 88: <!-- Ensure validationkey is not set to AutoGenerate,IsolateApps so it correctly supports webfarms -->
Line 89: <machineKey
Line 90: validationKey="AutoGenerate,IsolateApps"
Line 91: decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"
I've tried my best to search and came across this thread which is very similar to my situation: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/230823/scope/posts/Default.aspx
My intention was to install it in a hidden directory, configure it, then upload it to the root folder replacing the current site. There is currently a live site with an asp store running that cannot be taken offline. I don't have IIS or VS2008 and would prefer to do all the file tweaking on the remote server.
The folder structure on the server is like this:
D:\WWWRoot\mysite.com\www\test\dotnetnuke\web.config
From what I understand, the web.config inherits from any other web.config files above. There is another web.config file in the www folder, but it consists solely of:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
I've tried replacing that one with the dotnetnuke web.config, and I've also tried placing the dotnetnuke web.config in the WWWRoot, mysite.com, and www folders, one at a time. If the web.config file is in any other folder than dotnetnuke it won't find the modules, if it is in the dotnetnuke folder it gives the machinekey error. Similar to the link I posted above, I have no access to the server's IIS, what am I missing?