Welcome to the Community Exchange, a place where community members can exchange questions and answers related to DotNetNuke. If you would like more info about the Community Exchange, please visit this page in our Wiki.
I am in the process of moving my dnn site to another server and I am running into some permissions issues. I am moving from a dedicated server to a shared server at 1&1.com. Pasted below is a link to there windows shared hosting permission settings, Can someone look at it and tell me if DNN will even work in this environment.
http://faq.1and1.com/scripting_languages_supported/asp_net/2.html
In general, most hosts should be able to support an instance of DotNetNuke. I don't see anything here from a permissions standpoint that would get in your way.
However... I dug around a little more on the 1&1 website and saw that they specify the .Net version available as 3.5. DNN 7.0 and above actually require .Net 4.0 (version 6.x will run on .Net 3.5). I know that 1&1 is reputable, so I wonder if this is either a misprint o the website or something they are in the process of upgrading. You might want to inquire specifically about that.
http://www.1and1.com/FeatureSite-buildingNet?__lf=Static
Hi Scott. I have one more question. I get this error "Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed" I have researched it and the only way to correct it is to allow the aspnet user write permissions to the folder that DNN is going to. Is that correct? I have asked 1&1 to grant the permissions but since it is on a shared windows server they will not do it, they said we have to upgrade to a dedicated server to change the permissions. - sean williams 3 months ago
Thank You Scott. I really appreciate it. - sean williams 3 months ago
You have already flagged this post. Clicking "Remove Flag" below will remove your flag, thus reducing the count by one as well.