Products » Support Forums 

Support Forums

HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl MasterURL Master and Active Social IssueURL Master and Active Social Issue
Previous
 
Next
New Post
12/8/2009 4:56 PM
 

Hi Bruce,

I have brought this to you attention before. In AS to get vanity url in IIS it reuires us to use a custom 404.aspx that is placed in the root of the site. When AS 404.aspx is there and URL master is turned on the event logs get full with errors. The error message is:

AssemblyVersion: 5.1.4
PortalID: -1
PortalName
UserID: -1
UserName
ActiveTabID: -1
ActiveTabName
RawURL: /404.aspx?404;http://www.weezkids.com:80/favicon.ico
AbsoluteURL: /404.aspx
AbsoluteURLReferrer
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.27 Safari/532.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3fc16924-2411-49a0-bf07-fb723e1da096
InnerException: Object reference not set to an instance of an object.
FileName
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Framework.PageBase.get_PageCulture
StackTrace
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.at DotNetNuke.Framework.PageBase.get_PageCulture()at DotNetNuke.Framework.PageBase.OnInit(EventArgs e)at System.Web.UI.Control.InitRecursive(Control namingContainer)at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)--- End of inner exception stack trace ---
[ ]
 11/8/2009 9:43:52 AM  Page Load Exception      AssemblyVersion: 5.1.4; PortalID: -1; PortalName ...
AssemblyVersion: 5.1.4
PortalID: -1
PortalName
UserID: -1
UserName
ActiveTabID: -1
ActiveTabName
RawURL: /404.aspx?404;http://www.weezkids.com:80/Portals/_default/Skins/weezkids_new/dnnmodules.css
AbsoluteURL: /404.aspx

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.27 Safari/532.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: dcf6404c-212f-4972-bb4e-ca26f6abc8bf
InnerException: Object reference not set to an instance of an object.
FileName
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Framework.PageBase.get_PageCulture
StackTrace
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.at DotNetNuke.Framework.PageBase.get_PageCulture()at DotNetNuke.Framework.PageBase.OnInit(EventArgs e)at System.Web.UI.Control.InitRecursive(Control namingContainer)at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)--- End of inner exception stack trace ---
 

Can you please suggest a work around on how to get this issue fixed? Thanks

 
New Post
12/9/2009 9:19 AM
 

I wasn't aware that's how it worked for the vanity urls.  It's a pretty ugly way of handling things but probably the only way they could do it without writing their own Url Rewriting module.  The problem with going down this route (as you've found out) is that it solves one set of problems but can create a whole other set if the web server isn't configured exactly the same way as the developers might have expected.

The problem will be that you have (I assume?) switched on extensionless URls and mapped all requests (wildcard mapped) to the asp.net runtime.   I'm also guessing that what this does is send all 404 errors to the 404.aspx handler provided with AS, and this is causing the above exceptions.

The first thing to do is to check why these particular requests are resulting in 404 errors : does the /portals/default/skins/weezkids_new/dnnmodules.css file exist?  You could either create the file or remove the reference to it in your skin.

I would also assume that you have the standard 'ignoreRegex' filter in place for Url Master, and that it ignores both .css and .ico files.  The problem being is that even if the rewriter ignores them, perhaps the AS 404 handler is not expecting that.  I'm not really sure, I'm only guessing and so I need some more information.

Can you:

a) check to see if those files really don't exist

b) see if deactivating the AS 404 handler changes/removes the error (I'm not suggesting to remove it permanently, I just want to see how it affects things)

 
New Post
12/9/2009 5:26 PM
 

All your assumptions are correct.

Removing custom 404.aspx removes all errors.

I am using extensionless.

I did not mess with the ignore regex as I not familiar with it.

I am not expecting you to rewrite your module to solve this just looking if you have any easy workaround such adding some regular expression or some rules.

Thanks,

Tareq

 
New Post
12/10/2009 12:17 PM
 

Well, the error seems as though it is running the dnn page base for those 404 errors, which doesn't make any sense to me.  What does the 404.aspx page look like?  Is it a file you copy onto your system?  If so, what is the location, is it in the site root?

You can try adding |404\.aspx into your 'ignoreRegex' field, but this is a wild guess and probably not correct.  I'm thinking that these 404 requests want to have the portalAlias set for that portal, which would satisfy the request for the page culture when the 404 page is run.  But that doesn't make any sense to me.

So:

1) try adding |404.aspx into the 'ignoreRegex' field in you 'Advanced Regex Settings'

2) try and locate the 404.aspx file on your machine (or entry in your web.config) and let me know where it is.  Or tell me what the instructions that come with AS are.

 
New Post
12/10/2009 3:49 PM
 

The 404 looks like this:

 

<%@ Page Language="vb" Inherits="DotNetNuke.Framework.PageBase" %> <html> <head> <title>Page Not Found</title> </head> <body> Page Not Found </body> </html>

It is in the root of the site.

 
Previous
 
Next
HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl MasterURL Master and Active Social IssueURL Master and Active Social Issue


Support Guidelines.. Please read before posting

To get support on iFinity products and services, please search the forums for the the answer to the problem you are seeking. If you cannot find a solution, post a question in the relevant forum.   Ensure that you specify the relevant versions of the problem, and the actual error message or a detailed description of the problem.    You will need to register with this site to post on the forum.  If you have a Microsoft Live (Hotmail/Passport) account you can use that.  If you have a Open Id account you can use that.  If you neither of these, you will need to register a user Id and password.

Please note : If you are posting a new thread for the Url Master module, please include the following information where applicable:

- Url Master version

- DotNetNuke version

- Example Url where possible

- If there is an error, please post the full error text and/or stack trace (from the DotNetNuke event log).