I suspect it has something to do with PortalSiteMapProvider. Does it happen more on larger sites?
Does it happen more when the machine is loaded? - Chris Hewitt ________________________________________ From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] On Behalf Of Jeremy Thake [jth...@made4the.net] Sent: Monday, 19 April 2010 2:03 PM To: ozMOSS Subject: RE: There is no web named.... I tend to block those errors subconsciously from ULS logs much like all the crappy Ads you get on web sites ;-) I tend to see this error most on Publishing Sites. I'd be interested to hear a way of reducing this noise! I'll ask a few contacts... -----Original Message----- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Shannon Carey Sent: Monday, 19 April 2010 12:00 PM To: ozmoss@ozmoss.com Subject: There is no web named.... I have a problem with SharePoint that I keep seeing popup in the logs. I have been trying to figure it out for some time now and have had no luck. I was wondering if anyone else has seen this. I have seen it a a few client sites so far In the SharePoint logs I see an error w3wp.exe (0x1838) 0x275C Windows SharePoint Services General 8kh7 High There is no Web named "/somesite/Library/Forms/AllItems.aspx" There is no Web named "/somesite/Lists/Calendar/AllItems.aspx" ...... and so on To me it looks like there is some code calling something like "SPSite.OpenWeb("/somesite/Library/Forms/AllItems.aspx")" however there is no custom code on some of these servers and it is strange that it is happenning on multiple environments set up be different companies It is also strange that when you deactivate the publishing feature in the Site the error goes away. To further that, When you customise the MasterPage and change the Dynamic Link Levels to display more sites, we start seeing the errors encountered on additional sites that now participate in the new link levels of the navigation. Some of the things I have read on the internet is a MS person saying to Change the logging so the errors do not show HAHAHA yeah that really fixes the problem. Another site suggests that publishing features are not declared on the page, however the sites are WSS sites and we do not want it declaired In my experience this is actually a real problem because if you have a few lot of sites in the navigation then it increases the page load time, as SharePoint is trying to hit alot of non existant sites. Has anyone come across anything similar before? I'm intrested to hear your thoughts. Thanks, Shannon Carey SharePoint Trainer and Consultant Breeze T (02) 9362 5181 F (02) 9362 4898 M 0422 598 914 P.O. Box 528, Edgecliff, Sydney, NSW, 2027 shann...@breeze.net | http://www.breeze.net http://blogs.breezetraining.com.au/scarey _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
