erver Error in '/wholesalexrp' 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: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +49 DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2332 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

---

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1

That error is evidence of one of three or four issues introduced with the addition of the auto-portal alias mapping feature introduced in DotNetNuke 05.06.00. I believe that you will find you can browse to the newly created site by appending /Default.aspx to the url address. While it is possible to modify the code of the URLRewriteModule project or to create a new url rewrite rule which redirects (for example, www.example.com to www.example.com/default.aspx) to a url with /default.aspx appended, my recommendation is to install 5.05.01 at this time. The Gemini support forum shows that this and other related issues have already been checked in for DotNetNuke v 5.06.01 which should be available sometime next month. Fortunately, these issues with the URLRewriteModule affect only a small percentage of new installs and upgrades - I haven't yet figured out why only some installs are affected. ASP.Net 4.0 seems to be a common factor but not in all cases.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner