Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...DNN Migration from XP - IIS6 to Server 2008 - IIS7DNN Migration from XP - IIS6 to Server 2008 - IIS7
Previous
 
Next
New Post
1/23/2009 10:35 AM
 
whichedge

Joined: 12/20/2007
Posts: 13

Please help this driving me mad!

What I am trying to do is move a developement site from an XP (IIS6) box to a 2008 Server (IIS7) - now I know the server is configured correctly because I have Installed DNN 4.8 on it! I have copied the site lock stock and barrel over made a couple of changes to the web.config file to account form changing SQL servers, now before when I copied the site from the 2003 Server on to my XP box this was all I have to do to get the site to run (apart from changing the portal alias). However it seems that the web.config file needs some additions to account for IIS7. So I got the web.config files (one for the copied site and one for the fresh installed site) and made the changes that seemed different, which seems to be just <system.webServer><modules><handlers>. Now when I try and load the site I keep getting the following error.

 

Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x8007000d
Config Error The configuration section 'Modules' cannot be read because it is missing a section declaration
Config File \\?\D:\inetpub\vhosts\xxxxxxxx.co.uk\httpdocs\web.config
Requested URL http://www.xxxxxxxx.co.uk:80/
Physical Path D:\inetpub\vhosts\xxxxxxxx.co.uk\httpdocs
Logon Method Not yet determined
Logon User Not yet determined
Config Source 
  108:  <system.webServer>
  109:   <Modules>
  110:     <!--SSL redirect Settings -->

Can anyone point me in the right direction please, everything that I have found on Google about this refers to application config files and not site config files.

 

Cheers

Chris
 
New Post
1/23/2009 1:49 PM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

The modules node must be in lowercase.  Try using this snippet:

    <!-- The system.webServer section is required for IIS7 compatability It is ignored by IIS6-->
    <system.webServer>
        <Modules>
            <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="managedHandler" />
            <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
            <add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" preCondition="managedHandler" />
        </modules>
        <handlers>
            <add name="AJAX_ScriptResourceHandler" path="ScriptResource.axd" verb="GET,HEAD" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="AJAX_AppServiceHandler" path="*_AppService.axd" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="AJAX_WebServiceHandler" path="*.asmx" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="LogoffHandler*" path="Logoff.aspx" verb="*" type="DotNetNuke.Services.Authentication.LogOffHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="RSSJandler" path="RSS.aspx" verb="*" type="DotNetNuke.Services.Syndication.RssHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="LinkClickHandler" path="LinkClick.aspx" verb="*" type="DotNetNuke.Services.FileSystem.FileServerHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" />
            <add name="CaptchaHandler" path="*.captcha.aspx" verb="*" type="DotNetNuke.UI.WebControls.CaptchaHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" />
        </handlers>
        <validation validateIntegratedModeConfiguration="false" />
    </system.webServer>

Hope it helps,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/23/2009 3:11 PM
 
Oliver Hine


Oliver Hine's Avatar

Oliver Hine's Avatar

Oliver Hine's Avatar

www.nbrane.com
Joined: 7/2/2003
Posts: 559

If your site was running under IIS6 without any problems, and you have a tested backup... I'd run this from the command prompt..

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "DNN5 - Development/"

Replace the "DNN5 - Development/" with your IIS site name, if running under a virtual directory you can use "Default Website/DNN5" or something similar...

I'm pretty sure that's how I upgraded my sites to windows 2008 about a year ago...

 
New Post
1/26/2009 7:58 AM
 
whichedge

Joined: 12/20/2007
Posts: 13

Hi Oliver thanks for this, I ran the command line and got the message that the migration was sucessful. However....

Now when I go to the site I get this:

Server Error in '/' Application.

Request is not available in this context

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request is not available in this context

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace: 

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpContext.get_Request() +3465893
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +54

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +3385130
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +125
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +182
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +259
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +245

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465475
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +675

I am very new to all this, so this really doesn't mean much to me, all I do know is that this is a DDN error not a server error so I am guessing this is a forward?

Any help at all on this would great.

 

Cheers

Chris

 
 
New Post
1/26/2009 10:48 AM
 
Oliver Hine


Oliver Hine's Avatar

Oliver Hine's Avatar

Oliver Hine's Avatar

www.nbrane.com
Joined: 7/2/2003
Posts: 559

Hi Chris,

Sorry about the problems you're having trying to upgrade your site to IIS7. Can you modify the web.config so we can hopefully get a little more more details from .net. Can you update the follow sections under the system.web node.

<customErrors mode="Off" />

<compilation debug="true" />

Which version of DNN are you trying to run on IIS7? I'll start up my DNN VMware machine and test one of these as well...
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Migration from XP - IIS6 to Server 2008 - IIS7DNN Migration from XP - IIS6 to Server 2008 - IIS7


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