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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...moving DNN to production - The AppDomain shut down because of a change to the application level ..moving DNN to production - The AppDomain shut down because of a change to the application level ..
Previous
 
Next
New Post
2/7/2011 12:05 PM
 
Hi Everybody,


I've developed a DNN5 site for customer locally on my laptop and I am having problem moving it to a production server. Server is running Windows 2008 R2 (IIS 7.5). I've copied all the files, copied db, modified web.config to see the new db, checked to make sure dnn can see the db via connection string, made sure the directory permissions are correct (appdomain user has RW access to whole virtual directory) .. and it's failing me with following error message taken out of the portals/_default/logs directory:


    <log LogGUID="a3f8aab9-36b6-4d95-a605-53b4b0b02c34" LogFileID="" LogTypeKey="APPLICATION_SHUTTING_DOWN" LogUserID="-1" LogUserName="" LogPortalID="-1" LogPortalName="" LogCreateDate="2/4/2011 11:52:57 AM" LogCreateDateNum="0" BypassBuffering="True" LogServerName="SERVER01" LogConfigID="">
        <LogProperties>
            <LogProperty>
                <PropertyName>Shutdown Details</PropertyName>
                <PropertyValue>The AppDomain shut down because of a change to the application level configuration.</PropertyValue>
            </LogProperty>
        </LogProperties>
    </log>


I've been stuck on this for the last 3h .. so any hint's or advice is very appreciated.


Thanks!


Filip

PS. I've also posted the Q and stackoverflow.com (http://stackoverflow.com/questions/49...) just in case.
 
New Post
2/7/2011 7:02 PM
 
If you are setting up a system on 2008 - I would first suggest NOT running in a virtual directory.

Create a separate "add web site" for the dnn install - and assign it to a separate application pool.
This gives you much greater control over the dnn hosting than a virtual directory.

Also make sure you check which user has control of the application pool - by default its a virtual user create by IIS that is rather messy to work with.
Most people tend to create a new use and grant it permissions to the folder structure.

Westa
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...moving DNN to production - The AppDomain shut down because of a change to the application level ..moving DNN to production - The AppDomain shut down because of a change to the application level ..


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