I am currently trying to install DNN 3.2.2 on to a package hosted by 1&1.

Now before everybody tells me to drop 1&1 and go with Tom, Dick or Harry, unless they can better the package I am currently getting.

5 x .co.uk domains
200 external domains
1500 sub domains
unlimited email aliases
connection speed of 18,000 Mbit
6GB webspace
1500 1GB POP3/IMAP accounts
50GB monthly traffic
2 x SQL Server databases

for £16/month I am not interested.

I agree with the numerous postings I have already read that the support 1&1 gives is useless, when ever I ask about DotNetNuke they point me to a webpage that is both missing all of its images, and is obviously well out of date. Also 1&1 refuse to ask their customers who already have DNN running on their packages, to contact me and possibly provide me with some assistance.

So if there is anybodu out there who has successfully installed DNN onto 1&1 could they please drop a reply on this thread. I have fully documented the steps I have already taken, a document that 1&1 appear to refuse to read, and would willingly send it through.

The current state of play is the following message.

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>