I already searched and didn't find anything that would help me, so leads me to post here.  After 2nd clean install of DNN 3.0.13 and DB, I am still getting "An unhandled error has occurred."  when I hit the site. The url is http://localhost/dotnetnuke/Default.aspx?error=Object+reference+not+set+to+an+instance+of+an+object.&content=0

Hitting http://localhost or http://localhost/dotnetnuke gets the same error.

I don't have VS.NET, so I can't compile it here at work.

Any suggestions would be great.  Windows 2K Server, SQL 2K, MS .Net Framework 1.1 hotfix.

thanks

mjc

Post the full error message.

The only thing displayed on the web browser is

 An unhandled error has occurred.

and the url now says http://localhost/Default.aspx?error=Object+reference+not+set+to+an+instance+of+an+object.&content=0

but I typed in http://localhost , I get the same response if I do http://localhost/dotnetnuke

Any suggestions

thanks

How did you mapped both //localhost and //localhost/dotnetnuke?  Do you have two instances installed?

If you have one set of files in //localhost, and another at //localhost/dotnetnuke, remove the //localhost instance..

I am getting the same error after updating 2.1.2 to 3.0.13. All it says on the page is "An unhandled error has occured" with the link that the original poster put in.

Now, I complied it on my VS.Net and got no errors there. Any ideas?

Need more information?

I have the exact same problem on a complet fresh install of DNN 3.0.13 on Windows 2003 Small Business Server using SQLServer.
Installation went smooth, but when I click the "Click here to access your portal", I get "An error has occurred" (written twice actually)

What options do I have to try to locate this error? Can I get any useful info by enabling debug in the web.config?

Cheers,
Lars

I am still having this error when I do a fresh install of DB and DNN.  I can't be the only one having this type of problem?  I also tried this on my laptop and it worked.. I odd thing, I got DNN 3.0.12 working on my dev server and that worked 100%, then I did an upgrade to DNN 3.0.13, and was hit with the same error.  Have been trying to get DNN 3.0.12 back working and now I am getting that error now.  So both of my DNN 3.0.12 and 3.0.13 installs won't work.. It says in the install page that everything was ok, and when you click to see your portal.. http://localhost/dotnetnuke/Default.aspx?error=Object+reference+not+set+to+an+instance+of+an+object.&content=0

An unhandled error has occurred.

I even watched the video to install and got the same error.

thanks

netrunner

Same problem here too.

I ugraded my local DNN 3.1.2 to 3.1.3 Upgrade went smoothly and everything worked. I then uploaded the files and database to my production server. On my first visit the install ran without any errors. I clicked on click here to view your portal and now I am getting the same error as netrunner.

Does anybody have a suggestion as to how to correct this or even what might be causing it?

thanx

Update:

I actually got an error message on one of my attempts to browse the portal.

Server Error in '/' Application.

---

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:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Services.Localization.Localization.GetString(String name, String ResourceFileRoot, PortalSettings objPortalSettings) +130
   DotNetNuke.Services.Localization.Localization.GetString(String name, String ResourceFileRoot) +60
   DotNetNuke.Services.Localization.Localization.LocalizeTabStripDetails(ArrayList arrTabStripDetails) +152
   DotNetNuke.Services.Localization.Localization.LocalizePortalSettings() +56
   DotNetNuke.Framework.PageBase.OnInit(EventArgs e) +220
   System.Web.UI.Control.InitRecursive(Control namingContainer) +241
   System.Web.UI.Page.ProcessRequestMain() +197

[PageLoadException: Object reference not set to an instance of an object.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +350
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +366
   System.Web.UI.TemplateControl.OnError(EventArgs e) +109
   System.Web.UI.Page.HandleError(Exception e) +68
   System.Web.UI.Page.ProcessRequestMain() +2100
   System.Web.UI.Page.ProcessRequest() +218
   System.Web.UI.Page.ProcessRequest(HttpContext context) +18
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +179
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

*bump*

I'm having this same issue with a clean install of 3.0.13 over at Interland...

Chris

As you know, DNN has an 'admin' directory on its root directory. My host's (Interland) control panel is set to be accessible via a virtual alias named "admin" off the web root. I believe there's a direct conflict between the two.

So, every time DNN tries to hit the DNN admin directory (http://xxx.xxx.xxx.xxx/admin/), it gets redirected over to the control panel.

Last night, I sent Interland a support email requesting they resolve this somehow and suggested they might change the control panel alias to something that wouldn't conflict with DNN, like (http://xxx.xxx.xxx.xxx/cp/). In part, here was their response:

"Since you are in the shared servers, the URL: http://xxx.xxx.xxx.xxx/admin has already been set in the servers as the URL to access your admin page. We cannot do the changes that you have requested. We apologize for any inconvenience this may have caused. Please contact us should you have additional issues or questions."

In the first case, I can't believe a host as big as Interland hasn't run up on this before... second, I can't believe anyone would put up with "We cannot do the changes that you have requested" as a legitimate response to this issue. Give me a break - I would have expected this kind of response out of a host that charges $2.95/month; not from a leading provider that I just siged a 24 month contract with.

Thanks to IcthusTech for pointing this solution out: http://forums.asp.net/562020/ShowPost.aspx.

Now if I can just reach someone at Interland that understands a thing or two about customer service...

Chris

Object reference not set to an instance of an object.

What happened to me was that i had upgraded my Web site to 3.2.2 by unzipping the the new version 3.2.2 over the top of version 3.1.1 on the production server and everything went great.

and then i changed my web.config on my development server and uploaded it to the production server and I got Object reference not set to an instance of an object.

I never transfered the upgraded web.config file to development before I made my edits.

I fixed it by transfering my release.config to my development machine copy and pasted my settings (see below) from web.config to the release.config and renamed the release.config to web.config uploaded it and everything is back to normal.

 <add key="SiteSqlServer" value="Server=***;Database=***;uid=***;pwd=***;" />
    <add key="MachineValidationKey" value="4F55CB7D0186E80C025E0CEFF5FF8B353936FCE7" />
    <add key="MachineDecryptionKey" value="53AA0D039422AEE9E93EAB06BC9B46051DC7E39F32A18989" />

I also needed to get my FCK Editor changes put back into my web.config

Hope this helps.