Products

Solutions

Resources

Partners

Community

About

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving DNN 9 from 1 Server to AnotherMoving DNN 9 from 1 Server to Another
Previous
 
Next
New Post
9/24/2017 3:32 AM
 
Dear Colleagues,

I have attempted to copy a perfectly working dnn9 (latest version) install from Server 1 to Server 2;

However I now am faced with the dreaded;

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

I have spent over 24 hours trying to figure this out, everything I can tell is correct in web.config, SQL services are running the way they should, Network Service has full permissions to the directory path. I am beginning to lose sleep over this as I have a deadline and can't migrate to the new server as nothing seems to work.

I have tried deleting / re-adding the Network Service mapping on the restored db but it fails to delete it with an error in reference to the user owning a role on the DB.

Please help me out. I'm at my wits end.

 

Thank you

 
New Post
9/24/2017 3:35 AM
 
PS; I am using SQL Server 2008 R2 Standard on both servers. IIS 7.5 (latest version of DNN 9).

I backed up DB, copied to new server, created empty DB then restored to empty DB. Copied DNN directory from old server to new server, I did not need to edit web.config as new server has same name and instance as old server.
 
New Post
9/24/2017 5:03 AM
 
Turn on Failed Request Tracing https://docs.microsoft.com/en-us/iis/... it may give you a clue about where the request goes wrong.

Look in the database for the view vw_EventLog. Take a look at the last few entries (sort by LogCreateDate descending). Even though the request ended up as a 500 you may find that DNN was able to write a clue in there.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
9/24/2017 11:06 AM
 
Richard Howells wrote:
Turn on Failed Request Tracing https://docs.microsoft.com/en-us/iis/... it may give you a clue about where the request goes wrong.

Look in the database for the view vw_EventLog. Take a look at the last few entries (sort by LogCreateDate descending). Even though the request ended up as a 500 you may find that DNN was able to write a clue in there.

 

Thanks for the recommendation but I'm having no joy with that. I tried setting up a completley new install of dnn using Web Platform and even that doesn't work. I'm suspecting there's something amiss with this server, so I think I will wipe it and start again.
 
New Post
9/25/2017 12:27 AM
 
I mananaged to see through my flaw, the issue was due to using a named pipe! I had to use dynamic rule on the firewall to allow passthrough... Which I never did in the production server and DNN works somehow... on the new dev server it didnt. So I basically wasted a lot of time scratching my head and trying different things haha. That's life. Thanks for your reply Richard
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving DNN 9 from 1 Server to AnotherMoving DNN 9 from 1 Server to Another


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