Hello Steve,

I know its almost impossible to recover a broken DNN site like yours, without a backup, but if you provide us the file system and database, (which ever you have) we will do our best to recover your website.

Feel free to email me for any question.

---

Rashid KAZI
Rashid.KAZI @ DNN4Less.com

Fast & most affordable DotNetNuke Hosting.
Shared Hosting - Resellers Hosting - Cloud Servers - Dedicated Servers

Steve . . .

I'm sorry to hear that you will have to completely re-build the website but that approach will most likely be the best in the long run.

I placed a new client's DNN site on DNN4Less shared hosting (Silver plan) last fall and have been very pleased with both their performance and support. In late December I purchased their Reseller hosting plan (RS75) and have started migrating existing DNN sites from several other hosting providers. They were happy to move my already hosted site at DNN4Less into the reseller plan and give me a pro-rata credit for the unused portion of the shared hosting plan. When migrating a site from another host all you have to do is obtain backups of the filesystem and database from the previous host and place the backups (via ftp) into a folder of the new DNN4Less account. Their support will take it from there restoring the files and database and making the necessary connection string changes in web.config. The only issues that I've found so far are:

1) you must request support to set filesystem permissions for the ASP.Net worker process account on the root folder of the DNN install as any change to the website configuration (such as adding an FTP user) will reset permissions on the root folder. That is not a DNN4Less problem but rather a problem for any hosting provider using Plesk for its hosting control panel.

2) they restrict remote access to the database (via SQL Server Management Studio, etc.) by remote IP address. Once you provide support with the IP address that you will be using when connecting remotely to the database and as long as that address doesn't change, all will be well. If it does change, a call or email to support should take promptly restore access. A good security measure, I'm sure but a bit of a pain.

In one support case I had neglected to let DNN4Less support know that a fix they had made for me had resolved the problem. I received an email the next day following up and asking if the problem was resolved or if I needed further assistance.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner