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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Dev. environment woes under VistaModule Dev. environment woes under Vista
Previous
 
Next
New Post
7/9/2007 6:25 PM
 

Thanks for all the help, folks.  I've been trying everyone's suggestions, and here's a progress report.  I'm not sure if I should edit the code from here.  It seems like another configuration problem....

  • Navigate from the DOS prompt to c:\windows\microsoft .net\framework\v2.0.50727\ then type aspnet_regiis -ir and it will install and associate the mime types.
    Looked under MIME types but found no .ASP(X) there.
  • Control Panel\Programs\Programs and Features\Turn Windows features on or off.  Under Internet Information Services, expanded "IIS 6 Management Compatibility" and checked each item under it.  Under "World Wide Web Services\Application Development Features" ASP.NET was already checked.
  • Browsed to localhost/dnn and got a long error message which I failed to copy.  It said I should set up the app to use the classic application pool and gave the following command, which I ran as Admin in a CMD shell. "C:\Windows\System32\inetsrv>%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/"  
    It responded with Successfully migrated section "system.web/httpHandlers"
  • Browsed to localhost/dnn and got the following error message.  (This is also the point where I started documenting my progress.)
    Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS." 
    I took this to mean I should convert the virtual directory to an application...
  • Started IIS Manager, right-clicked my dnn virtual directory and chose "Convert to Application" and pressed "OK"  (still no .ASP(X) under MIME types, btw)
  • Browsed to localhost/dnn.  Much disk churning, then, "Object reference not set to an instance of an object."  Turned debugging on in web.config.
  • Browsed to localhost/dnn.  "Object reference not set to an instance of an object."

    Object reference not set to an instance of an object.

    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.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    Line 84:                     If AutoUpgrade Then
    Line 85:                         If UseWizard Then
    Line 86:                             Response.Redirect("~/Install/InstallWizard.aspx")
    Line 87:                         Else
    Line 88:                             Response.Redirect("~/Install/Install.aspx?mode=install")

    Source File: c:\dnn\App_Code\Global.asax.vb    Line: 86

    Stack Trace:

    [NullReferenceException: Object reference not set to an instance of an object.]
       System.Web.HttpHeaderCollection.SetHeader(String name, String value, Boolean replace) +121
       System.Web.HttpHeaderCollection.Add(String name, String value) +49
       System.Web.HttpResponse.GenerateResponseHeadersForHandler() +162
       System.Web.HttpResponse.IntegratedFlush() +10
       System.Web.HttpResponse.Flush(Boolean finalFlush) +107
       System.Web.HttpResponse.Flush() +17
       System.Web.HttpResponse.End() +106
       System.Web.HttpResponse.Redirect(String url, Boolean endResponse) +498
       System.Web.HttpResponse.Redirect(String url) +6
       DotNetNuke.Common.Global.CheckVersion() in c:\dnn\App_Code\Global.asax.vb:86
       DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in c:\dnn\App_Code\Global.asax.vb:321
    
    [HttpException (0x80004005): Object reference not set to an instance of an object.]
       System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +3381770
       System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +167
       System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +270
       System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext, IntPtr& errorMessage) +260
    
    [HttpException (0x80004005): Object reference not set to an instance of an object.]
       System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3539851
       System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
       System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +669

 

The InstallWizard.aspx file is there in its proper location.

Time for supper.... Coolness!

 
New Post
7/17/2007 8:55 PM
 

It's been awhile since I installed it on my Vista Laptop and got it working, but I recall something like this happening and I think I just opened the install wizard page directly instead of going through default. Also, I remember somewhere in the install that it kept displaying a next button over and over again, but then I started all over from the start and it worked. I guess I should have documented it better, but I was having enough problems just trying to get it to work :)

 
New Post
9/19/2007 5:33 PM
 

I'm getting the same error. I tried opening the installwizard and the install pages directly, but I keep getting the same error. Has anybody figured this out?

 
New Post
9/19/2007 5:39 PM
 

I think I figured it out. I ended up going to the IIS and changed the Application Pool to Classic.NET

- Open IIS

- Right-click over DotNetNuke and select "Advanced Settings"

- Select Application pool and change from Default to Classic.

At least that fixed my problem on my computer... Hopefully that helps.

 
New Post
10/14/2007 7:43 AM
 

Thanks dpiccolo,

That worked for me too.  I had been trying everything I'd read about to date. Thanks again

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Dev. environment woes under VistaModule Dev. environment woes under Vista


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