I've had such a crush on DotNetNuke's architecture! To test and tangle, I've downloaded and installed version 3.0.13 as described in the book "Professional DotNetNuke ASP.NET Portals" by its authors. Within 10 minutes, it installed without a glitch (clean install).
When I tried to "boot" it for the first time, it somehow, "turned me down" with the following message.
I tried to reinstall ASP.NET, refresh MS SQL Server, clean temporary ASP files, but no way. Is it just dark magic that puts this DNN to work? Please let me be of more help with the situation, and kindly ask me to post further log files.
Thanks.
Object reference not set to an instance of an object.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +127
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +93
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3554
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87
I've just had the same happen on a clean install of DNN 3.1.1 to shared host (SeekDotNet). Upon first browsing to the newly uploaded site, DNN appeared to install correctly without error. Clicking on the link at the bottom of the install summary to go to the
site resulted in the error. Permissions were properly granted to the ASPNET, IWAM_SKNET69, and IUSR_SKNET69 users, for both read and write in the application root folder (public_html).
Examination of the MS SQL Server 2000 database shows that the various DNN related tables were created and most were populated with initial data. So, we know that the database connection is successful. HOWEVER, a number of tables relating to Host and Portal
Settings, users, users in roles, user profiles, etc. are EMPTY of all data.
I have requested that the corrupted database be deleted (have to wait 12 hours for actual deletion??) and will try again.
I've seen several references to this same error on the forum, but no clear solution.
I had the same problem but i thing it was bad configuration of the web.config.
Renamed the release.config to web.config and changed the settings to the database but used the administrator login (sa). It worked!
After that changed again to the normal login and it had been working.
Member
3 Points
17 Posts
Error on first run: "Object reference not set to an instance of an object."
Sep 15, 2005 09:22 AM|ASPMatters|LINK
I've had such a crush on DotNetNuke's architecture! To test and tangle, I've downloaded and installed version 3.0.13 as described in the book "Professional DotNetNuke ASP.NET Portals" by its authors. Within 10 minutes, it installed without a glitch (clean install).
When I tried to "boot" it for the first time, it somehow, "turned me down" with the following message.
I tried to reinstall ASP.NET, refresh MS SQL Server, clean temporary ASP files, but no way. Is it just dark magic that puts this DNN to work? Please let me be of more help with the situation, and kindly ask me to post further log files.
Thanks.
Object reference not set to an instance of an object.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +127
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +93
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3554
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87
None
0 Points
1 Post
Re: Error on first run: "Object reference not set to an instance of an object."
Sep 18, 2005 12:36 AM|VisualDave|LINK
Some people said it was a permission issue. I have set the ASPNET user and IUSER to maximum.
Please help!!
Member
81 Points
466 Posts
Re: Error on first run: "Object reference not set to an instance of an object."
Sep 20, 2005 12:49 PM|imagemaker|LINK
Examination of the MS SQL Server 2000 database shows that the various DNN related tables were created and most were populated with initial data. So, we know that the database connection is successful. HOWEVER, a number of tables relating to Host and Portal Settings, users, users in roles, user profiles, etc. are EMPTY of all data.
I have requested that the corrupted database be deleted (have to wait 12 hours for actual deletion??) and will try again.
I've seen several references to this same error on the forum, but no clear solution.
Member
1 Points
11 Posts
Re: Error on first run: "Object reference not set to an instance of an object."
Sep 20, 2005 01:28 PM|afas|LINK
I had the same problem but i thing it was bad configuration of the web.config.
Renamed the release.config to web.config and changed the settings to the database but used the administrator login (sa). It worked!
After that changed again to the normal login and it had been working.
Frank
Member
10 Points
564 Posts
Re: Error on first run: "Object reference not set to an instance of an object."
Sep 20, 2005 03:24 PM|ecktwo|LINK
See specific permission settings for disk drive root (in additional to application root):
http://forums.asp.net/916304/ShowPost.aspx