I am using a remote provider (Godaddy) to host my site.
All of the files for DNN 4.02 were uploaded to the \portal directory off of my host root. I modified the web.config as per the instructions and don't seem to be having a problem connecting to the database. However, now when I attempt to run the install process at the server level, I get the following error:
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error:
Line 56: </system.codedom>
Line 57: <system.web>
Line 58: <machineKey
Line 59: validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"
Line 60: decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" |
Since its a remote host, I don't have access to the IIS config on it to flag that directory as an application.
This install originally started off as a Starter Kit install, but I had put it in the root directory. Because you can't change permissions on the root on GoDaddy, I moved everything to the portals directory, set the custom config, and thats when this started happening.
Any help would be appreciated. I looked around quite a bit, but all of the solutions I found for DNN and other ASP applications that were getting this error referred to modifying the IIS settings, which I cannot do. I suppose maybe if I started from scratch again with the starter kit and pointed to a different directory that might work. But it takes about 2 hours on my machine to initialize a new project onto GoDaddy using the starter kit, so if that can be avoided that would be great.
Thanks in advance,
Eric