I have created a couple of aspx web pages that I want in a directory under a portal. This was working fine until I upgraded to 5.6 of the community edition. Error is below. Is there a work around?

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

I'm having the same problem and that link seems to address something different. I updated to v. 5.6 and most of my pages still work, but there are a few aspx pages on my site that I've created separate from the DNN hierarchy. Those pages throw the error below. Also, I have some DNN pages that use AJAX to call an ascx server control to inject content which get the same error. I don't know how this is related, but the error is the same.

The DNN event viewer displays the following:
AssemblyVersion: 5.6.0
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /centers/cusli/niagara/test2.aspx
AbsoluteURL: /centers/cusli/niagara/test2.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618; .NET4.0C)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 4553d0d0-462e-44c1-9aab-4acbef00a645
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Entities.Portals.PortalSettings..ctor
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: LAXXXXX

It seems that DNN isn't able to access portal info for these pages?

Windows event viewer reports it this way as an asp.net error with event id 1309:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/23/2010 11:24:50 AM
Event time (UTC): 11/23/2010 4:24:50 PM
Event ID: 490f244f7c5446999e77351966ac0b65
Event sequence: 2
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/XXXXX/Root-2-129350030851374183
Trust level: Full
Application Virtual Path: /
Application Path: E:\xxxxxxxx\Website\
Machine name: LAXXXX
Process information:
Process ID: 3060
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.

Request information:
Request URL: http://xxxxx/centers/cusli/niagara/te...
Request path: /centers/cusli/niagara/test2.aspx
User host address: xxx.xx.xx.xx
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo)
at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

does anyone have any suggestions?

Bill,

Thanks for the reply, which sounds like a reasonable explanation. 

I'm running IIS 6, so I don't think #1 applies to me, so that leaves me with #2.

I tried passing portalid=0 on the querystring but it didn't change anything. The DNN log viewer still showed PortalID: -1. I'm not sure if that's due to inheritance or not. I tried inheriting from PortalModuleBase originally, then tried Pagebase and CDefault at your suggestion, but those didn't change the outcom. I could mis-type the inherited class or the using statement and it still wouldn't matter. It doesn't seem like .net ever gets to those lines of code.

I think I'm going to have to wait for 5.06.01