ERROR: Access Denied when using the Repository Module

DNN > Troubleshooting
Access Denied Error when Using the Repository Module in DotNetNuke (DNN) Cause and Resolution.

Issue:

When you browse to a page that has the repository module on it, you get an error like:
 
Access to path C:\Inetpub\vhosts\MySite.com\httpdocs\Portals\0\Repository Denied

Cause:
This is caused because the repository module "hard-codes" the storage location of the files in the file system.  This issue commonly occurs after a site migration, clone, or rename.

Resolution:
In order to resolve this issue, you need to make a change in your database.

Using file manager in your control panel or DNN instance open your web.config file and copy the connection string it should look like this 
 
<add name="SiteSQLServer" connectionString="(local);database=databasename;uid=username;pwd=SftWri489ccm;pooling=true;connection lifetime=120;max pool size=25;" />

 Using Microsoft SQL Server Management Studio
 Microsoft SQL Server Mangement Studio Express 2008 is available for free from Microsoft, and can be downloaded through this link: http://www.microsoft.com/download/en/details.aspx?id=22985

Match the connection string this information with the data requested by the SSMS login window

The hostname in the example above is mssql.yourdomain.com.
The username is username.
The password is SftWri489ccm.

Once logged into the database:

Open the ModuleSettings table in the DotNetNuke database.
  1. Browse through all the module settings until you come to one that looks like:
    E:\WebSites\Site.com\wwwroot\portals\0\repository Note:  This setting will look different for each hosting provider out there.  What you need to be focused on is changing everything to the left of the \portals\ to be the correct path for our servers.
  2. Continue scrolling through the module settings for any more repository path settings.  Change them as well.
  3. Browse to the httpdocs folder of your website, right click on it and click on Properties, go to Security, and make every user with a Plesk in front of it have full access.
  4. Restart the website's application pool.

Add Feedback