Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...System.Web.Util.UrlPath.ReduceVirtualPathSystem.Web.Util.UrlPath.ReduceVirtualPath
Previous
 
Next
New Post
6/24/2006 6:34 PM
 

What happened when you tried it?

So far, it seems to be working for us.  The error usually appears about twenty times per hour for us, and it hasn't occurred at all since we made this change an hour ago.  However, I know we haven't been hit by googlebot since making the change.  Also, I hope the change doesn't break something else.



Shane Miller
Call Centers 24x7
 
New Post
6/24/2006 7:08 PM
 

Many times I thought I found the solution but after time I was disappointed it did not work. I have spend months trying to find what the cause was and I found it was Google and MSN bot. Blocking those two in my Firewall did the trick, it stopped the errors completely. I don't want to block any search engine but I decided to block all of them exept for Google, that seems to important for my site.

There is another error that seems to be related to this. It is at least caused by cached pages in Google. If you search something in Google it also shows you a link to cached content of that page. As soon as you click that link (assuming it is your page that is cached by Google) it will throw the following error:

ModuleId: 366
ModuleDefId: 106
FriendlyName: Smallbizserver.Net Forum
ModuleControlSource: DesktopModules/NTForums/NTForums.ascx
AssemblyVersion: 04.03.01
Method: System.Web.Caching.CacheEntry..ctor
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: Smallbizserver.Net
UserID: -1
UserName:
ActiveTabID: 53
ActiveTabName: Forum
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
ExceptionGUID: 7bead622-a707-4c6e-88eb-157b284b360b
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Value cannot be null. Parameter name: value
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null. Parameter name: value ---> System.ArgumentNullException: Value cannot be null. Parameter name: value at System.Web.Caching.CacheEntry..ctor(String key, Object value, CacheDependency dependency, CacheItemRemovedCallback onRemovedHandler, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, Boolean isPublic) at System.Web.Caching.CacheInternal.DoInsert(Boolean isPublic, String key, Object value, CacheDependency dependencies, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, CacheItemRemovedCallback onRemoveCallback, Boolean replace) at System.Web.Caching.Cache.Insert(String key, Object value, CacheDependency dependencies) at NetTech.NTForums.ForumBase.get_ForumInfo() at NetTech.NTForums.toolbar.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
StackTrace:
Source:
Server Name: WEBSERVER

The above error is not exactly the one you would get if you view such a cached page on Google, the referrer will show you the exact URL to that cached page. If I further analyze my Firefwall logs I can see a call is made for all the stuff you see on that cached page. If you look in the source of that cached page on Google you will also see a Viewstate value and I bet this van never be valid causing probably the 'slidingExpiration' error. Maybe Google caches the httponly cookies that are new .Net 2.0 but I also tried setting that to 'false' in the web.config, did not fix it either. As long as no user complains about errors on the site I am not stressed to find a solution but it would be nice to have clean logs. I have never seen clean logs with .Net 2.0 and Dotnetnuke. With .Net 1.1 that was different. My server could run for weeks, months without errors. It all started with 3.2.2 and .Net 2.0. As soon as I switched back to .Net 1.1 the errors were gone...

I have limited knowledge about all of this but I am trying to find a reason for those errors using my common sense and never ending search for solutions.

 
New Post
6/24/2006 7:38 PM
 

I just viewed a cached page in Google, and even clicked on it to get to the site, and it didn't result in any errors.  I wonder if something is different about my setup...however, the real test will be when we're hit by the googlebot.  I'll keep scanning the IIS logs periodically to keep an eye out for the googlebot and let's see what happens then.  Sometimes a couple of days pass between Google's crawling on our sites, on this particular dnn installation (the others aren't having any problems) so it might be a couple of days till we know.

Like you, it was only when we switched this installation over to 3.2.2 and asp.net 2 that the problems began.  I didn't make troubleshooting it a very high priority because I thought it was merely an annoyance filling our log files, but now realizing it is inhibiting the search engine spiders, makes it a much higher priority.



Shane Miller
Call Centers 24x7
 
New Post
6/24/2006 7:49 PM
 

Another issue I have is this:

Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1315
Date:  6/24/2006
Time:  11:33:07 PM
User:  N/A
Computer: WEBSERVER
Description:
Event code: 4005
Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired.
Event time: 6/24/2006 11:33:07 PM
Event time (UTC): 6/24/2006 9:33:07 PM
Event ID: 0868a33c66854e648568136vvde98a1956
Event sequence: 608
Event occurrence: 6
Event detail code: 50202
 
Application information:
    Application domain: /LM/W3SVC/178108102/Root-1-12795644553800312500
    Trust level: Full
    Application Virtual Path: /
    Application Path: F:\Smallbizserver.Net\
    Machine name: WEBSERVER
 
Process information:
    Process ID: 588
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Request information:
    Request URL: http://www.smallbizserver.net/Default.aspx?tabid=53&ctl=Login
    Request path: /Default.aspx
    User host address: my IP address
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Name to authenticate: 
 
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Cathal looked at this and we dit not find an answer. This also started after going to .Net 2.0. I think we need a big service pack

 
New Post
6/25/2006 12:50 AM
 

Great news...my fix worked!!  I can confirm now that Google has definitely crawled many pages with the googlebot and the error no longer appears.

Woohoo!

Now Mariette if you try making that exact same change to your web.config and you still get the error, would you like to compare our configurations and see why the fix doesn't work for you?



Shane Miller
Call Centers 24x7
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...System.Web.Util.UrlPath.ReduceVirtualPathSystem.Web.Util.UrlPath.ReduceVirtualPath


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out