Lee and Joe,

First of all a huge thank you for your site. Through your videos, i was able to learn DNN and after some months, build my first website and host it at PowerDNN (again, because of your recommendation!).

The migration from my home network to PowerDNN was an absolutely smooth process and all my worrying was for naught.

I am only experiencing one outstanding issue with the move.

For some reason, the Documents module that i'm using, all are publicly available - no sign in, is kicking out a 404 error:

Description: HTTP 404.
Requested URL: /LinkClick.aspx

It works fine on my localhost; it was the only thing that didn't work when i put it up on PowerDNN.

I am using DNN 5.5 (i know, i should upgrade, but it was the version i developed on).

I know i have a dead link on Sitemap, but if you want to see what i was able to build using your videos, the URL is:

http://www.waterstreetgalleryltd.com

Any help you can give me i would certainly appreciate!!

My first guess would be that the "filetickets" somehow did not survive the move from your local site to PowerDNN. Why this happened is probably dependent on HOW to moved things. Can you describe how you did that?

At this point, your choices would be to either rebuild the links on the PowerDNN site or make another attempt at moving the site in a way that will preserve the filetickets. For the latter, I don't know enough about the Documents module to know what do suggest. Perhaps asking this question on the forum for the Documents module at DotNetNuke.com will provide a better answer.

Hi Robbit,
Thanks for joining the PowerDNN family! We're glad to have you on board.

Sometimes we see those types of problems on sites that were migrated because of missing entries in the web.config . DNN needs different settings depending on what OS you're on. We use Windows 2008 R2 x64.

If you go ahead and open a support ticket, our team will be able to get that taken care of for you. You also might want to reference this KB article when you open a ticket:
https://support.powerdnn.com/index.php?/Knowledgebase/Article/View/41/112/http-error-50021---internal-server-error--captcha-errors

I think you have a different cause, but I'm pretty sure it will be the same solution.

Tony, your guys fixed the problem (Chris and Jon).

Thanks for all your help.