Hi,

I have been developing a sample website for a while now in DNN 4.4.1.  I would now like to transfer it to another machine so someone else can continue development of the site.

Looking at the articles both here and elsewhere this would appear to be a fairly simple operation, but it also seems to be beyong me at the moment!

What I have done so far is:

Added the new machine as a Portal alias.

Copied the entries DotNetNuke directory under my localhost IIS installation to the other machine.

Backed up my database and restored it to the other machine.

Created a virtual directory on the other machine for dotnetnuke and set it to ASP.net 2.0

Modified web.config so the new database is used.

However, when I try to log into the site on the new machine I just get an error:

 

Server Error in '/DotNetNuke' Application.

---

Access to the path 'C:\Inetpub\wwwroot\DotNetNuke\Install\UnderConstruction.htm' is denied.

Whatever I try I see to end up with this same message. 

From everything I read it would appear to be fairly simple to transfer an existing dnn site from one machine to another, although most of the articles do discuss moving a site to a production server, which is not yet what I want to do.

My initial Install of dnn was using the Starter Kit, but the machine I am moving to does not have Visual Studio on it so I am just trying to move the dnn site itself.

Does anyone have any ideas what I have done wrong, or am not doing here>

David Penny

 OK - answered my own question!

I had not set up correct access rights to the ASP directory (ASP.Net was not a User on the other machine).

All OK now.

Hello,

Glad to hear you got it sorted, if you have any further questions, please feel free to ask,

Cheers,

Lee

Hi there,

I am moving a dotnetnuke solution from one server to another. One of the steps is to change the portal alias. I have just changed this in the dnn_portalAlias table after i have copied the database and source code to the new location. I dont believe this should cause an issue.

I am getting the error:  Login Failed for user 'xxx'.

Quite a descriptive error,  and one which i have resolved before. I have checked the credentials...



...Which are all correct.

Does anyone have any suggestions as to where to go next with this?

Any help would be much appreciated.

Thanks,

Kev

Check that you can access your transferred database with the username and password that you have specified in the connection string. - you can test this using SQL server.

You will want to double check that the username has access to the transferred database

Double check the connection string in your web.config file, make sure it is pointing to the new server, with the correct database name and username.

Thanks for the speedy response. Who needs DBA'a eh. They hadnt set the password up correclty!

great!

Hi, im hoping someone can help me.

I had problems installing the AD provider in my DNN solution (4.9.0). Was getting an client side error 'FCKeditor is undefined'. After a while of searching i found this thread which sorted my issue:

http://www.dotnetnuke.com/Community...fault.aspx

I have since had to copy the DNN solution from a test environment to a live environment following the same steps i took last time (which worked fine). As before when i have come to install the AD provide i got the error mentioned above, so i followed the same steps. However, instead of it working, i now get a totally different error!!!!

Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified

Which i believe is something to do with AJAX? The server config hasnt changed, and i really dont know why i would be getting this.

Can anybody please help?

Thanks,

Kev

It seems that it would work, provided that the actual configuration settings for the Active Directory provider are the same for both installations. 

So ... I don't have a good solution.

Thanks for the reply. I have managed to sort this issue, though to be honest im mot 100% how i did it which is never good. Anyway i have been documenting all the things i have been doing with DNN (as im a newbie!) so ill just post my comments. Some of it is only relevant to me but it might be useful to someone if they are also having similar difficulties......

There had been changes made to the DNN solution on the DNNhost server. I needed to copy the solution over again. To do this I needed to.

 

1.      Copy the database over again

2.      copy the source code over again

3.      configure the webconfig file for the correct SQL DB

4.      Change the portal alias to the new address.

5.      Re-install the ad provider.

a.       Don’t forget to tick the top 3 options

b.      Username: svc_intranetdnn, Password: 1ntr4n3tDNN

c.       We shouldn’t need to use impersonation in the config file.

 

I initially had an issue with step 4. After completing this step it gave me an error about not being able to find the host. I closed any browser with it open previoulsy, deleted my cache/cookies, restarted IIS again, then browsed to the DotNetNuke folder through IIS which worked.  Im not sure if it just needed a bit of time to sort itself out!

 

I then had more severe problems when installing the AD provider again.  I new I would encounter the ‘FCKeditorAPI is undefined’ error – which I did. I follwed the same steps as before, but then got a different error:

 

Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified

 

I have no idea why I got this error. I checked and double checked the steps I had taken and couldn’t see anything wrong. I did line by line comparissons on the web config I had backed up, restarted IIS etc, but no joy.

 

The only thing I think I did different when installing the provider was when I got the initial error ‘FCKeditorAPI is undefined’ I clicked ‘previous’ on the installer wizard, whereas before I just closed the session. Not sure why/if this made any difference.

 

I then decided to roll the web.config file back and do the process again. It is very important to follow the steps in the install.txt file to the letter. Read it very carefully. I checked the config file again when I rolled it back to see what state the FckHtmlEditorProvider was in before I follwed the steps on install.txt again. I also noticed that there was a provider in there already – im pretty sure there wasn’t one when I first did it. I left the provider in, and just copied a new one in, it had the same name so I knew it might fail, but that’s what the instructions said to do. It failed again. I then commented out the old provider line, restarted IIS, cleared cache/cookies, and tried it again which worked. And installed the AD provider.

 

I have just checked the htmlEditor section again, and the one I commented out is exactly the same as the one I added in!!!

Anyway this is now working!