Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Copying a Full DNN Install to Another DomainCopying a Full DNN Install to Another Domain
Previous
 
Next
New Post
3/13/2008 10:52 AM
 

I have a DNN v 4.5.5 install such as subdomain1.mydomain.com and I wanted to create a duplicate copy of the site as it is now for testing on testsubdomain.mydomain.com.

So I used my control panel (DotNetPanel) to create a new website on my dedi server. Then I created a new database and then restored a copy of the existing db .bak file. So the new db looks good now. I changed the portalalias table to reflect the new domain testsubdomain.mydomain.com. I also changed the HostURL to that as well.

I copied the entire wwwroot folder for the existing site to the new site's wwwroot folder and updated the permissions for Network Service user.

I updated the web.config file on the new site to use the new db and new db user.

I kept getting the... The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist and I thought it must be a connection issue. So I checked the connection settings multiple times. I also changed the connection to use the user that existed in the original db and I tried to do the sp_change_users_login 'auto-fix' sproc to ensure that it was working.

But I cannot get the site to come up. At one time last night I got Invalid Hostname or something like that.

Is there something simple that I am forgetting to do?


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
3/13/2008 1:56 PM
 

OK, so I'm stupid. I guess you coudl say that I am depriving some village of their very own personal idiot.  

I named the subdomain something other than what I was typing into my browser. Not a good start.

Once I went back into the control panel to double check things, I saw that. Now when I hit the Home page it just hangs forever. I CAN get to a file using http://subdomaintest.domain.com/logo.gif.

So I know IIS is serving it up. Apparently there is some other issue now.

On further inspection of the db properties, I see that while I did make sure that it restored to the correct New db, I did not go in and manually change the Logical Name from the old db to the new one.

Once I did that, it all worked out. I don't remember having to do that in the past. Is there a setting or something on the original restore that I did from the old .bak file to the new database that should have taken care of renaming the logical names?

Anyway, maybe this post will benefit someone in the future.


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
3/26/2008 5:01 PM
 

Hi,

I had to create a copy of my website as i had to test it on the development server. So i created a new directory on my local machine and unzipped the dotnetnuke package. I created a new database and installed another instance as per the installation guide. Once I had my existing database, I restored it with a backup of my original website.  However all the data and tables were not copied. Also, it threw an error during the loading of the website's skins and container. It does not allow me to upload any skin or even containers and throws an error saying 'the access path has been denied'.

Kindly help.

Melrine

 

 

 
New Post
3/26/2008 9:58 PM
 

Hi Melrine,

Sounds like a permissions problem.  If you go to the directory that DNN is in, which is probably wwwroot or httpdocs, you need to make sure that folder gives read, write, and execute to the IIS user and the IIS WP user.  I don't know a whole lot about your environment but I think that might do it.  I hope I was helpful:-)

 
New Post
3/27/2008 10:49 AM
 

Hi John,

Thanks for the help. I checked the folder. It has all the required permissions.

This is the error I get when I try to install a new skin package

 

Error: Install Skin Package is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Access to the path 'C:\TestDotNetNuke\Website\Portals\_default\Skins\Classic-Semantic_Brown' is denied. ---> System.UnauthorizedAccessException: Access to the path 'C:\TestDotNetNuke\Website\Portals\_default\Skins\Classic-Semantic_Brown' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity) at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at DotNetNuke.UI.Skins.SkinController.UploadSkin(String RootPath, String SkinRoot, String SkinName, Stream objInputStream) at DotNetNuke.Modules.Admin.FileSystem.WebUpload.cmdAdd_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

TestDotNetNuke is my directory that contains all the files and folders related to the backup site. Even if a folder for a package is not found, when you install a new one it should create a folder automatically to store the new files.

Any help will be appreciated.

Thanks

Melrine

 

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Copying a Full DNN Install to Another DomainCopying a Full DNN Install to Another Domain


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out