I was wondering if anybody knows how to  set correct read write permissions for a DNN istallation.

My web host provider I guess expects me to do this.  

What tools do you have that you'll be using to do this?

In cases of shared hosting, your hosting provider will not give you access to set the permissions required for DotNetNuke. - Generally all you have to do is send a support ticket to them after you have uploaded the DNN installation files and request they set the correct permissions before you initiate the installation. - If they are a DNN hosting provider they will do this for you no problems.

I have an account with lunar pages.  I am using plesk control panel, I have access to my MS sql data bases and can restore them back them up etc.

I have a web directories tool where I can creat virtual directories , I have mylittle sql tool .  here's the link for the web host i   lunarpages.com

Thnaks
 if you can help

I have worked on a site that is hosted at lunarpages.  I have run into a number of problems, but persistence with their support staff has paid off.

Doing a backup/restore using the available tools has cause problems.  On one  occasion, the restore didn't restore the right user access.  On another account, a backup/restore with the Plesk tool left the domain disabled.  There was even one occasion where the site somehow got reverted to ASP.NET 1.x even though the Plesk tool "thought" it was ASP.NET 2.x.

Eventually, though, and after a lot of exchanges with the support staff, things got fixed.

So, this is probably a longwinded way of saying that some level of diagnosis and persistence on your part is going to be necessary.  First, try to figure out if the problem is file permissions, or database issues. 

If you put a file called app_offline.htm in your web site's root directory, then browsing to the site should display that html page.  The file can be as simple as containing  only "We're not home!"  But, if you see this, you know that the web site is likely working.  (Though there could still be some permission problems)

Why not try that and let us know what happens ...

Thanks joe for the response.

I know the main domain website is working (not the dnnportal )which is located in a in folder called httpdocs which is where lunar looks for its mainwebsite pages

I Have set up a an html file to test in httpdocs and it works fine

My DNN installation was in the httpdocs folder as a subdomain and it worked fine.

I installed it (dnn 3.2) using lunars automatical istallations.  dnn 3.2 is all they had.

Again it worked fine.


I am in the process of trying to install dn 4.5.3 on my own.  I've deleted all previos installations and wiped the slate`clean.


I set up a new data base with MSSQL  , then I created a vitual directory, edited web.cofig,
set read and write permissions

I'm still getting error when I browse to the website to initiate the install. 


I must be doing something wrong.  I'll keep tryning

thanks

What is the error message you get when you browse to the site?

Jim,

I did not save the exact error , but i think it said dotnet nuke installation error, and then it gave some code to add to my files if i want to make custom errors

I can't  bring up the error page again, because I've deted all the folders etc associated with the installation .

I will attempt another install when i have a chance.

I'm trying to get a better understanding about asp.net, iis, mssql , and dnn and how thet all work together.  t seems fairly complex. 

If you know of any reading that might might make more clear this .  let me know.


Thanks
paul

My first suggestion is that you start by reviewing the DNN Creative Tutorials, particularly those related to installing DNN.  Start with the first one, "An Introduction to the Principles of DotNetNuke" and work through all of them.

Secondly, it might actually be easier to get a copy of DNN working on your local computer.  You'll have to install the MSSQL Express Edition, but you won't have to deal with the complexities of a hosting situation, and other configuration tools right out of the gate.  Once you have DNN running locally, you can consider moving to the hosted site.

And, if you create another installation on your hosted site, make copies of every error message, and document everything that you do.  To capture error messages, screen captures are great!

And ... don't give up too easily.  There are a few hoops through which to jump, but it's not too bad.