locked
'There is no Web named' in logs RRS feed

  • Question

  • Hi,

    I was wondering if anybody could help me.  When i look at logs in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS i get a lot of errors saying 'There is no Web named'.

    For example:-
     
    09/08/2008 09:29:37.17  w3wp.exe (0x1BA0)                        0x296C Windows SharePoint Services    General                        8kh7 High     There is no Web named "/quality/Audit Reports/Forms/AllItems.aspx". 

    There are no errors in server application event log.  I was hoping to find out what this means and if i should worry about the errors. 

    Regards,

    Chris Rees.
    Monday, September 8, 2008 11:55 AM

Answers

  • Bingo!

    The site master page setting currently applied to this site is invalid. Please select a new master page and apply it

    But the masterpage hasn't been customized infact sites with this issue use standard out of the box templates (Wiki/Team/Blank)... others use custom site definitions.

    Setting:
    Specify a master page to be used by this site and all sites that inherit from it == default.master
    Select a system master page for this site and its subsites to inherit. == default.master

    Re-selected default.master...

    Restarted server

    Checked logs again and guess what  There is no Web named "/wiki/Lists/Questions/AllItems.aspx"

    Checked  Site Settings > Site Master Page Settings   >>> No warnings.

    So it hasn't made any difference.
    Wednesday, December 2, 2009 12:27 AM

All replies

  • Hello Chris,
    Sounds like you deleted library on your site and you still have some links to it.

    Cheers
    Ivan Bondy - MCPD, MCDBA, MCSA, MCTS - Sharepoint consultant
    Monday, September 8, 2008 3:13 PM
  • No, the message is repeating numerous times in MOSS log.

    Not sure if this has started since we upgraded to SP1.  When i upgraded to SP1 i had to detatch databases from MOSS, upgrade to SP1 and then add databases back in using "stsadm-o addcontentdb".  Our content databases are quite larger.

    I found out later that i should have run "stsadm -o preparetomove" before detatching.

    After upgrade i had errors in event log that i fixed using "stsadm -o sync -deleteolddatabases 5"

    Because of the problems i have been keeping an eye on the logs and I am a bit concerned about the errors.

    Regards,

    Chris Rees.
    Monday, September 8, 2008 3:40 PM
  • Hi Chris,

     

    I understand it is uncomfortable if there are repeated errors in the ULS logs.

     

    It is hard to say what the cause of the error message is.

     

    If there was not any abnormal functionality of your farm, please feel free it is just some noises in the ULS logs.

     

    If you found some abnormal functionalities of your farm, please let us know and we will try to help you.

     

    -lambert


    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 12, 2008 1:49 AM
  • Hi,

    Thanks for you reply.

    This doesnt fill me with confidence with sharepoint as a product.  I would like to know what these errors mean as they are filling my log file and are a concern.

    I dont think Lambert Qin has provided an answer.    I cant ignore these errors as it hinders troubleshooting other problems if the log is full of so called 'noises' in the ULS log.

    Would rebuilidng indexes help?  i can try this on the weekend.

    Regards,

    Chris.

    Tuesday, September 16, 2008 8:06 AM
  • Chris/All,

    I am seeing the exact same thing.  Many messages similar to:

    "There is no Web named "/Test Library/Forms/AllItems.aspx".

    And the libraries have not been deleted.  I'm willing to entertain the notion that these are "normal errors" since I do not see any ill-effects as yet.  But if you have discovered what was causing your errors, could you share your findings?

    Many Thanks,
    -Ryan
    Monday, December 15, 2008 6:11 PM
  • Anyone know how to correct this yet? I am seeing similar errors and have concerns. If nothing else, it makes finding real issues nearly impossible.
    Wednesday, February 25, 2009 11:33 PM
  • Hi,
     
    i am still getting these error messages.  havent found out what is causing errors.

    Chris.
    Thursday, February 26, 2009 4:32 PM
  • I've also got this issue, and I have been investigating on a front-end web server that is outside the load balance, so I am the only user hitting it. I noticed all the URLs being hit were in a particular site.


    1. I created a blank site as a child of the site with problem URLs

    2. I set top and quicklaunch navigation on the blank site to both only show child content

    3. I stopped the timer and search services to prevent log pollution

    4. When I browse to the default page of the blank site, this pair of errors occur between 0 and 19 times. Each refresh of the page seems to log a seemingly random subset of the problem URLs with no URL logged twice for one hit, although the first hit after a period of inactivity or editing navigation settings invariably lists all 19 pages:

    03/18/2009 19:08:52.25     w3wp.exe (0x12F4)                           0x1CC4    Windows SharePoint Services       General                           8kh7    High        There is no Web named "/Solutions/Project Initiation/Forms/AllItems.aspx".     
    03/18/2009 19:08:52.25     w3wp.exe (0x12F4)                           0x1CC4    Windows SharePoint Services       General                           8e2r    Medium      Possible mismatch between the reported error with code = 0x81070504 and message: "There is no Web named "/Solutions/Project Initiation/Forms/AllItems.aspx"." and the returned error with code 0x80070002.     



    5. All of the URLs that are logged are the default views of lists or document libraries in the parent site's quicklaunch menu. If I edit the list/document library settings and deselect 'display in quicklaunch', that list's default view no longer appears in the list of errors. Re-enable display in quick launch and its back. Bear in mind my child site I'm refreshing in the browser is not displaying the parent's quicklaunch or top menu when this happens.

    6. I created a new empty document library on the parent site with 'appear in quick launch' selected and it started appearing the error log when I refreshed the child site homepage.

    7. Whenever I submit the "Title, description & Navigation" settings page for any list/document library it logs the following 3-4 times, which may or may not be related:

    03/18/2009 19:03:42.08     w3wp.exe (0x12F4)                           0x2460    CMS                               Publishing                        8ztg    Medium      Got List Item Version, but item was null.    

    8. I created another new empty document library, this time in the child site, again with 'appear in quick launch' selected, and it did not appear in the error log. It also did not generate the above error when the "Title, description & Navigation" settings were edited.

    Does this provide any hints to the cause?

    • Edited by Paul__Hickman Wednesday, March 18, 2009 7:20 PM edited for grammar
    Wednesday, March 18, 2009 7:18 PM
  • I wish it did offer some additional hints to fix this issue. I don't like seeing these errors and when trying to review anything else these errors are in the way.  Oh yeah, we've been having this issue for quite awhile and it appears noone has found a "fix".
    Thursday, April 16, 2009 5:27 PM
  • Have you by any chance modified the master page?  I had the same issue and when I restored the masterpage they disappeared.

    Wednesday, May 6, 2009 6:08 AM
  • Hi Chris,

    I'm experiencing the same problem... I honestly don't think that these are real errors as I am receiving them for web's that do exist and that do have the name described in the log and that are working at 100%.
    The thing is that this is generating an annoying amount of garbage (+/- 10Mb/day)

    I agree with you, this cannot be ignored, as reporting fake errors is, in fact, a problem, specially when the level is marked as "high".
    How ever I haven't been able to find a cause/solution for it... I will keep investigating but in the meantime I have the installation of SP2 planned... perhaps it'll fix it.

    Cheers,
    Mario
    Friday, May 8, 2009 8:38 AM
  • I am also getting this error.  It is extremely frustrating as we are having several issues and it is hard to troubleshoot these other problems when the logs are full of these "There is no web named..." errors.

    Some of our logs are getting as big as 40MB (for 30 mins).

    Has anyone found a cause for these "errors" yet?
    Monday, May 11, 2009 5:50 AM
  • Hi,
    We are alos getting similar errors and I agree having noise in the logs will make the troubleshooting a pian.

    Any clue on how to avoid these errors?

    Ramana

    Thursday, July 16, 2009 5:58 AM
  •     Any news on fixes for this. It is happening now on a server farm at one of my clients. This farm has been up and running for more than a year with 1+ TB of content.  They are patched to SP2. This is a HIGH level log. It is filling up the logs and after the amount of money my client has spent converting to a MS platform, I have to tell you, they are not impressed and right now are considering halting future projects with BTS, SQL, and even Windows 7.

       MS' position that high level errors should be ignored as "junk" without any root cause analysis by MS does not look very good from their perspective. As a technical guy I understand WHY MS is saying this but come on guys, if you just spent a million or more on a piece of technology with a new platform and within it's first year of operation it is kicking out garbage errors...what are they gonna think? How can we trust the product at all or any log entry it throws out? How can people have any confidence in the stability of the platform itself? I mean I love MS software but help a brother out here, we cannot just sit back and accept junk log entries especially "High" level ones that give a message that indicated enterprise data is missing or damaged.
    Tuesday, September 1, 2009 12:17 PM
  • Hi,

    I still haven’t found a fix for this and have left it for now.  Still getting same errors in log.  It is very frustrating as I cant look at other issues when this is filling logs up.  I have been putting off installing SP2 as I am worried that I may get problems installing it.

    I would have thought Microsoft would have fixed this with an update by now.


    Chris.
    Wednesday, September 2, 2009 8:26 AM
  • Go to C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\_vti_pvt on your web frond end server.

    follow this instruction
    http://support.microsoft.com/kb/300246

    Aniket
    • Proposed as answer by Yannis Thursday, May 20, 2010 10:12 AM
    • Marked as answer by Mike Walsh FIN Thursday, May 20, 2010 10:48 AM
    • Unmarked as answer by Mike Walsh FIN Monday, January 17, 2011 7:35 AM
    • Unproposed as answer by Mike Walsh FIN Monday, January 17, 2011 7:35 AM
    Friday, September 4, 2009 3:40 PM
  • I've got to agree with Gouranga1.  I'm in Dallas trying to get a simple SPD workflow going and experiencing numerous problems.  Looking in the logs just has me more confused with all the "noise."  I have no idea whether these entries have anything to do with my problems or not.
    Tuesday, September 8, 2009 11:32 PM
  • Hello, I am facing same problem.

    BUT, I have connection with two other problems. One is check-in and check-out of files in "Shared Library" list. Unknown error on screen and not working this possibility (but reservation of same document in SPD is working). Secondly there is problem with customized workflows - tasks generated by this workflow cannot be "finished" by other users (aprove after check text of item). Both incidents generate in logs only this "possible mismatch" errors...

    09/12/2009 15:05:06.65     OWSTIMER.EXE (0x0134)                       0x0B40    Windows SharePoint Services       Topology                          0    Medium      Adding DOMAIN\user to local group 2.     
    09/12/2009 15:05:06.78     OWSTIMER.EXE (0x0134)                       0x0B40    Windows SharePoint Services       Topology                          0    Medium      Adding DOMAIN\user to local group 2.     
    09/12/2009 15:05:06.78     OWSTIMER.EXE (0x0134)                       0x0B40    Windows SharePoint Services       Topology                          0    Medium      Adding DOMAIN\user to local group 0.     
    09/12/2009 15:05:09.70     w3wp.exe (0x193C)                           0x1390    Windows SharePoint Services       General                           8kh7    High        Web s názvem /projekty/0000_projekt/Lists/Kalendar/calendar.aspx neexistuje.     
    09/12/2009 15:05:09.70     w3wp.exe (0x193C)                           0x1390    Windows SharePoint Services       General                           8e2r    Medium      Possible mismatch between the reported error with code = 0x81070504 and message: "Web s názvem /projekty/0000_projekt/Lists/Kalendar/calendar.aspx neexistuje." and the returned error with code 0x80070002.     
    09/12/2009 15:05:09.71     w3wp.exe (0x193C)                           0x1390    Windows SharePoint Services       General                           8kh7    High        Web s názvem /projekty/0000_projekt/Lists/Projektov kontakty/AllItems.aspx neexistuje.     



    Any idea or solution ?? - searching web bring me nothing...
    Monday, September 14, 2009 12:00 PM
  • I faced similar issue in the sharepoint logs.

    High     There is no Web named "/FCPATrainingMaterial/Forms/AllItems.aspx". 

    there are many errors as above.

    Fadi Noja
     mentioned notes in the above replies helped me in resolving.

    I created a site and few lists with option to show the lists in quick launch. After that, my master page changed, in which no list was shown in the home page as quick launch section removed completely. But, all the lists were still having "Display this list on the Quick Launch?" option set to Yes.

    I navigated to settings of each list -> Title,description,navigation -> marked "Display this list on the quick launch?" to No.

    After browing the site for a while, i checked the logs and found no related errors.

    • Proposed as answer by Hari2009 Tuesday, November 10, 2009 12:01 PM
    • Unproposed as answer by Mike Walsh FIN Tuesday, April 20, 2010 1:02 PM
    Friday, October 9, 2009 1:32 PM
  • Has this topic been abandond?

    My logs contain an entry 8kh7 High / 8e2r Medium for almost every library in the site collection.
    Monday, November 9, 2009 10:52 PM
  • I submitted this question and i still have the problem.  Still havent resolved this issue.  This is very annoying and prevents me troubleshooting other issues.  I am also very wary about applying SP2.
    Tuesday, November 10, 2009 9:39 AM
  • Are any of your deployments upgraded from SharePoint v2 to v3? Do you have language packs installed? Have your site definitions been changed pre-upgrade (say from v3 rtm to sp1) and then changed after upgrade?

    Tuesday, November 10, 2009 12:12 PM
  • Hi,

    I have followed Mr. Sai Krishna Rachakonda Users MedalsUsers Medalsabove comments and it worked for me.
    Now i am not getting this error in log file.

    Thanks a lot Sai Krishna.

    Regards,
    Hari Proposed Answer
    Tuesday, November 10, 2009 12:25 PM
  • Our deployment was an upgrade from sharepoint v2.    dont have any language packs installed. not sure about site definitions.
    Tuesday, November 10, 2009 12:32 PM
  • My Environment:
    1. Clean install MOSS Std x64 with SP1 integrated/slip-streamed.
    2. 1 custom site definition for 90% of sites.
    3. No Upgrades
    4. Restores
    5. No lang packs
    6. No 3rd party dll's
    The "There is no Web named" happens on both the out of the box definitions (Team Site/Blank Site) and in the custom site definition.

    It's seems obvious that one of the SharePoint classes is trying to instantiate an SPWeb / SPSite object with a URL path to an aspx page.

    Eg:

    SPWeb web = site.OpenWeb ("/FCPATrainingMaterial/Forms/AllItems.aspx ")
    instead of
    SPWeb web = site.OpenWeb ("/FCPATrainingMaterial ")
    Tuesday, November 10, 2009 10:33 PM
  • Just looked at my logs on our live.  It does look like all the errors end in /Allitems.aspx

    e.g:
    8kh7 High     There is no Web named "/site1/Customisation/Lists/Team Discussion/AllItems.aspx"


    Wednesday, November 11, 2009 12:49 PM
  • If you go to the Site Settings of the site that is listed (/site1/Customization...) and go to Master Page in the Look and Feel column, does it show that you have any masterpage issues?
    • Proposed as answer by Rodney Langley Tuesday, October 12, 2010 1:37 PM
    Tuesday, December 1, 2009 9:49 PM
  • Bingo!

    The site master page setting currently applied to this site is invalid. Please select a new master page and apply it

    But the masterpage hasn't been customized infact sites with this issue use standard out of the box templates (Wiki/Team/Blank)... others use custom site definitions.

    Setting:
    Specify a master page to be used by this site and all sites that inherit from it == default.master
    Select a system master page for this site and its subsites to inherit. == default.master

    Re-selected default.master...

    Restarted server

    Checked logs again and guess what  There is no Web named "/wiki/Lists/Questions/AllItems.aspx"

    Checked  Site Settings > Site Master Page Settings   >>> No warnings.

    So it hasn't made any difference.
    Wednesday, December 2, 2009 12:27 AM
  • First of all, SharePoint has sooo many errors and "noise" that you should all be very aware that most of them are meaningless and will cause you hours and hours of rabbit hole chasing.  You can throttle back errors in the Admin Site if need be, in fact there are KB articles claiming the fix to some errors is just hiding them...way to go Microsoft!

    This error has me fairly perplexed as well, I have been seeing it and wondered if there was a problem or a fix (keep in mind that not every error is actually an issue).  I just noticed this morning that the links in the log do not corespond to a site in my collection.  I have special characters in the URL (this was back before I named lists and sites without spaces and characters). 

    Not sure if this can be fixed, but I find that best practice in SharePoint is to name your site, list or item without spaces or special characters, then go back and rename your site to whatever you want it to read.  SharePoint always uses the first name of the site/list when creating the URL...after that and more changes to the name or site will not update the url.
    Sunday, December 6, 2009 5:07 PM

  • I have the same "There is no Web named" messages in the log files and couldn't fix it. There is something about the error in the following URLs: http://www.msexperts.org/blogs/mark/archive/2009/03/02/content-deployment-error-there-is-no-web-named-quot-quot.aspx ,  http://fnoja.blogspot.com/2009/04/error-there-is-no-web-named-when.html . It didn't work for me, but someone may find it useful.
    Monday, December 7, 2009 2:50 PM
  • Bingo!

    The site master page setting currently applied to this site is invalid.

    Allow me to add my tuppence worth. I also have the same issue, and find it equally annoying. Every time someone looks over my shoulder while I am debugging some other problem, I have to explain to them why I am ignoring these messages. They frequently don't believe me, and frankly I don't blame them.

    I attempted the "master page" fix described above, had the same "invalid" warning, re-selected "default.master", and restarted. The error still appears in the logfile even though the warning is gone.

    I had the issue before I installed SP2 and I still have the issue after I installed SP2.

    Like others, the list names always end in "allitems.aspx". However, subsites always end in "default.aspx".

    *sigh*
    • Proposed as answer by Mike Elgan Tuesday, April 20, 2010 12:06 PM
    • Edited by Mike Walsh FIN Tuesday, April 20, 2010 1:03 PM Don't use full quote -it uses up screen space for no good reason
    • Unproposed as answer by Mike Walsh FIN Tuesday, April 20, 2010 1:04 PM
    Thursday, December 17, 2009 2:43 PM
  • Excuse the "Proposed as answer" you may see earlier from me.
    Sometimes, you just click on the wrong thing.


    I found a cause of this error message for a customer, but found no resolution on the web during research.
    I want others to find this and hopefully resolve this issue more easilly.

    Synopsis:
    The cusomer had a SharePoint MOSS2007 environment.
    The sites displaying the problem were based on a standard Team Site Template.
    The Publishing Infrastructure Feature was active.
    Disabling the Publishing Infrastructure Feature fixed the problem.

    Quick Indications:
    The "There is no web..." error message being logged and possible performance impact.
    Display of a "Navigation" instead of "QuickLaunch" linkage area.

    Quick Information (Emperical):
    The Publishing Infrastructure Feature creates objects in the site.
    If the site is not based on a Publishing Template, the Navigation component does not have everything it is expecting.

    How to find your base Site Definition:
    I suggest verifying that you have the same situation by checking the Site Definiton your problem site is based upon.

    1. Make a site template, no content, of the problem site.
    2. Download the site template to your file system.
        The site template has an .stp file extension, but it is in fact a compressed (zip) file.
    3. Change the file extension from .stp to .cab .
    4. Open the site template and extract the Manifest.xml file.
    5. Open the Manifest.xml file and look for:
    <TemplateID>
    <Configuration>
    6. The vaules defined can be found in OneNet.xml (SharePoint Hive) for exact reference.
        The following are the values for a standard Team Site:
    <TemplateID>1</TemplateID>
    <Configuration>0</Configuration>

    Good luck, and I hope this helps.

    Tuesday, April 20, 2010 12:39 PM
  • Thank you very much for this. I have not validated that this is the case I have seen numerous times, but it make obvious (of course now it is obvious) sense. I almost can't wait until I have my next client that is experiencing this issue.

    Once again thank you,

    Eric VanRoy

    Tuesday, April 20, 2010 1:22 PM
  • You are welcome Eric, and it would be interesting to know how many of these problems are based upon what I found.
    I wish there was a way for us to know.

    A suggested customer scenario:
    Log shows the error Message.
    "Tsk...".
    Navigation instead of QuickLaunch.
    "Mmmmm...".
    Site Template verified as non-publishing.
    "Uh-huh...".
    Feature found active.
    "Yep...".
    Deactivate the Feature, Error goes away, Eric basks in the glow of success, Customer ecstatic.
    Hopefully.

    Michael E. Elgan

    Sunday, April 25, 2010 12:44 PM
  • Synopsis:
    The Publishing Infrastructure Feature was active.
    Disabling the Publishing Infrastructure Feature fixed the problem.

    Thanks bigmee.  Your post set me off on a quick fix to resolve the error.

    In my case, I have a farm in which I am adding additional servers.  Our app does an API call to SharePoint and results in an exception with the message containing "There is no web named ..."

    The existing servers were built with MOSS 2007 and later had service packs applied.  The new servers had MOSS installed with the updates slip-streamed.  (I don't yet know this difference to be the cause, but I'm suspicious of it).

    The observed difference between the two builds is several hundred file differences in the 12 hive (mostly regarding features, templates, and language resources).  However, one that caught my eye was that the file ...12\Template\Features\PublishingTimerJobs\feature.xml was not present on the new servers (and publishing is active on the site).  Copying that file over provided a quick fix for the exception while we assess the rest of the differences.

    Thursday, April 29, 2010 3:55 PM
  • You are welcome, jrjespersen.
    I am pleased that the posting triggered a "brain storm" that provided you with a quick fix.
    I am especially pleased that you took the time to post your situation and resolution.

    While your situation was different than mine, it appears to have the same root cause.
    I will be adding your information to my personal knowledgebase for future reference.
    "Publishing Site with missing functionality" will now become the root cause description for this problem.

    If we are lucky, others will post their experiences with what they found, and we can find more situations that cause this.
    I would really like to see if this "root cause" is producing the log entries for others.

    Mike

    Wednesday, May 12, 2010 1:11 PM
  • Synopsis:
    The cusomer had a SharePoint MOSS2007 environment.
    The sites displaying the problem were based on a standard Team Site Template.
    The Publishing Infrastructure Feature was active.
    Disabling the Publishing Infrastructure Feature fixed the problem.

     

    What if you don't want to deactivate the Publishing feature?  

    I understand that we are seeing these errors in the logs because our sites were initially created from a non-publishing site template and then we activated the Publishing feature.  The reason that I create non-publishing sites and then activate Publishing afterwards is due to the fact that creating a customized Publishing site template is not supported (hence there is no button for 'save site as template' when you view the Site Settings on a Publishing site).  I want the ability to create new sites with some customizations added, have all sites with the same web parts, etc... AND be able to use the Publishing feature. 

    Has anyone else found a way to fix the problem without turning off Publishing or rebuilding the sites directly from a Publishing template? 

    Wednesday, May 12, 2010 3:45 PM
  • SharePointDrivesMeCrazy,

    I did forsee your situation as one possible source of this problem, and appreciate your posting it.

    I find it strange that SharePoint allows the activation of a publishing feature on a non-publishing site.
    And then apparently does not include all the functionality to support the Feature.

    If the missing dependencies can be located, they could be included in your custom site definition.
    I hope that someone has done this previously, and can provide the appropriate dependency list.
    It would be great if it was only a matter of activating some other Feature(s).
    Wishful thinking.

    Mike

     

    Wednesday, May 12, 2010 4:22 PM
  • Go to C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\_vti_pvt on your web frond end server.

    follow this instruction
    http://support.microsoft.com/kb/300246

    Aniket

    I did what the article said additionaly at the c:\inetpub\... directory. It seems to have stopped logging the error.
    Thursday, May 20, 2010 10:12 AM
  • I don't think that is the answer for the majority of people that are dealing with this issue.  On all three environments where I'm seeing 'There is no web named...'  the only thing that is in the services.cnf file is a slash \. Furthermore, the KB article cited applies to FrontPage 2000 Server Extensions and FrontPage 98 Standard Edition.

    So...I disagree that Aniket's post is the answer.  Chris - did Aniket's proposed solution fix the problem for you?

    Thursday, May 20, 2010 3:30 PM
  • I agree that this prob is associated with enabling Publisher feature at site collection level.

    I have also found that using 'relative' path names in your quick-launch will provoke the error in the log. If you change the URL to absolute paths..i.e full URLs then they do not appear in the log. That is why so many people get this with the ../../AllItems.aspx paths. It is because these are the default URLs generated when you make an item and select 'show in quick-launch'. If you edit the URL and add the full server path e.g. http://<spserver>/<site>/Lists/Products/Allitems.apsx then the Publish process can identify it and no error in log. Of course this means you need to be careful when restoring the site to another server!


    Software Techie
    Wednesday, May 26, 2010 2:05 PM
  • I had this happen to me, and I've researched more than I care to admit.  I found that by turning on/off Publishing feature at site collection, it fixed it.  However, I don't have the luxury of turning this off, so I'm going to ignore it.  I came across some info in an unrelated search for another SP bug and thought it may explain a few things for you techies out there...

    The next step was to consider the CrossListQueryCache class which provides the ability to cache the results. In reality, apart from introducing the cache, this class doesn’t do much more than wrap the SPSiteDataQuery class and the call to SPWeb.GetSiteData().  Unfortunately attempting to use the cache for each site collection query causes problems – any attempt to query a site collection beyond the current one results in a error:

    There is no Web named "/sites/WebSite".

    This is due to the way that CrossListQueryCache class is written – as revealed by examining Microsoft.SharePoint.Publishing with .NET Reflector. During the execution of the GetSiteData method, a call is made to the getWeb method of the ContentByQueryWebPart:   So when the cached query is executed it uses the getWeb method to get the reference to the SPWeb object to run the query against. The problem is that this method uses the context of the calling code, via SPContext, to open the web site specified by the URL:  Thus, even though the caller has passed through the correct SPSite to use when opening the SPWeb against which the query is to be run, the CrossListQueryCache ignores this and instead uses the context of the caller. 

    Original article was found at http://oidatsmyleg.wordpress.com/2009/08/13/cross-site-collection-query-almost/

    Monday, June 7, 2010 7:28 PM
  • Thank you Jennifer for the information. I can attest to the fact that Jenn has put in more time than she would like to admit on this issue.

    Thank you to Mark too. Your information on relative paths in quick launch has been verified and helps.

    I opened a Microsoft incident a short while back on this, and have a great fellow working with me on the issue. The case was opened with the express intent of taking the time to research and attempt an easy resolution, if possible. The case directly targets quick launch as the source of the problem, since that was my particular case.

    To reproduce the situation:
    1. Create a Team Site in a new site collection.
    2. Turn on the site collection publishing feature (this is enough to cause the error to occur).
    3. Turn on the site publishing feature (just to make it more real world).
    4. Browse to the site, and "No web named.." error is logged.
    5. Cycle the web app when attempting anything to get immediate error logging when browsing to the site (I have a feeling that caching is involved).
    6. Cycle Windows Sharepoint Services Tracing (services.msc), if you want a new log file without waiting for SharePoint to create one. Throttling can be used to, to filter out other logging.

    Some of the things Courtney (Microsoft) and I have found out so far:
    1. Definitely Quick Launch related for this situation.
    2. Disabling Quick Launch in Site Settings > Tree View will make the problem go away (not a reasonable solution, but good to know). Also, disabling display on Quick Launch for individual List, Library, etc. will make the error go away for those items not being displayed.
    3. Changing relative paths to absolute paths, as Mark noted, does work. Using an absolute path in quck launch to an external web site makes the error return (go figure). For a site being used as a template, this is not the best viable solution (good information for troubleshooting though).

    Additionally, I have just run a test against some Courtney information.
    1. Top level site is Team Site, Publishing turned on for Site Collection and Top level site.
    2. Created a subsite, Team Site, nothing turned on (though Site Collection publishing is on from 1. ).
    3. Cycled Tracing and Web App for a nice clean test.
    4. Browsed directly to the subsite.
    5. Error log messages for both the top level and subsite (anything in quick launch for both sites).

    I will post more information, when pertinent, as the research into the case continues. Additional information from others might provide us more clues.

    Mike

    Tuesday, June 8, 2010 1:33 PM
  • By the time this gets resolved, we will all be on 2010!  I just surpress or ignore these errors...SharePoint logs are horrible to track and have so much clutter that they almost become useless unless you turn down the error collection to just critical issues.  It should be set that way by default and then allow you to go into verbose mode like most normal products.

    Is it safe to say that nothing is really broken?  I get tons of these errors becasue I turned on Publishing after the fact to get some of the publishing column types into my site. 

     

    Tuesday, June 8, 2010 2:13 PM
  • Having the same issue myself. Noticed it a long time ago and mostly ignored it. We are probably going to fall into the publishing feature turned on in a non-publishing site. Just adding myself to the thread so I can see the result.
    Thursday, June 10, 2010 6:29 PM
  • By the time this gets resolved, we will all be on 2010!  

    I upgraded a site with this issue using content database attachment and it did no longer occur.
    Thursday, June 10, 2010 7:25 PM
  • Trying to track down the There is no Web named "/sites/etc" error, these are my findings, in my environment:

    1. It occurs when the SharePoint Publishing Infrastructure is enabled at Site Collection level, which is often used only to give more flexible navigation.
    2. Links which do not have the full path seem to create the error in the log. (ie those starting /sites/sitename/etc)
    3. If you put the full path, with the full domain name path, the error messages in the log go away.

    This is not great as the /sites/ path gives more reliability should the domain name change. But if you want to get rid of polluting messages in your SharePoint logs, take this route. 

    Friday, June 11, 2010 10:57 AM
  • I have had the same problem with a lot of these error messages in the logs.

    Fortunately, I have found a solution - it turned out that:

    • SharePoint's content database was rather big - about 36 Gb
    • Log of SharePoint's content database was much biggger - about 270 Gb
    • The size of the database and its log was assigned as 10% of the current size - so the database will require 3.6Gb and the log wil require 27Gb to increase
    • Free availabel space on the disk was only 9Gb (enough for database increase but not enough for log increase)

    I freed the space and now everything starts workign correctly! :-)

    I hope it helps!

    Thursday, August 26, 2010 2:14 PM
  • I have been getting these errors.  I read through the thread.  This is my situation. 

    I've got a site template that has been and will be used to create many different sites in many different site collections on the same server.  This server is under control of the Navy's IT and we have no direct access to it.  (Can't see logs, can't see files, can't see IIS, can't create site collections, etc).  We can manipulate the settings that can be done through the browser.  The site templates are for dozens of sites so that they must be able to be quickly implemented with a minimum of manual customization.  This was done by utilizing a lot of XLS parameters and Javascript variables. 

    A "unknown error" was occurring alternately whenever an edit to a folder was taking place on these sites.  (i.e. the error would occur then after a refresh of the folder edit page, the error would not occur.)   So the site was copied to our development server. 

    It was copied to a site collection on the development server where we started seeing these errors in the log.  We theorized that these errors would cause a problem on the production server because of the much larger content database and the greater amount of server resources being employed, whereas on the development server they get logged, then a retry permits the operation to succeed.  Just a theory. 

    The site collection that this site was added to shows as having the publishing infrastructure activated. The site uses a few master pages.  Some pages use the customized default master page which does not show the quick lauch menu. A number of lists were created as "show in quick launch".   Yes when I turned off "show in quick launch" on some of the offending list the errors went away.   However other pages are using the built in default.master which does have a quick launch menu, in which these lists need to be shown. paradox.

    In addition, in conjunction with these errors I was getting another error that seems to be associated with it. 

    It was < Unexpected query execution failure, error code 282. Additional error information from SQL Server is included below. "The 'proc_GetTpWebMetaDataAndListMetaData' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead." Query text (if available): "{?=call proc_GetTpWebMetaDataAndListMetaData(?,'1BCD7BAB-80D3-4D2F-8441-54D3D0F14D33',?,NULL,1,?,?,6187)}"  >.  It would appear in the log right after each "There is no web called ..." error. 

    I am reluctant to turn off the Publishing feature at this time because last time I did I was not able to get it come back on.  I had to run a set of 5 stsadm commands not all of which were successfully completed.  And the server administrators of the customer's sites want that feature turned on for the parent site collections. 

    Vladimir we have no access to the database so we cannot check that issue.  If we put the full URL in  the navigation of the quick launch for the site template then each of the dozens of site that are created from this template will have to be extensively manually edited before in can be place in operation a task which the customer does not want to do or pay to keep us available to do.

    Jennifer did not explain how to resolve the CrossListQueryCache class issue.

    So is there anyway I can resolve these errors without turning off publishing and without turning off "show in quick launch" on every list?


    ERJ MCSD MCDBA
    Friday, September 17, 2010 8:18 PM
  • Per the boss, I am not able to turn off publishing as that will screw up our menus.  I did go through each list and change "Show in Quick Launch" to no.  However the there is not web called and the "Unexpected Query execution" errors are  still continuing.  In addition there is a new error saying "List does not exist  The page you selected contains a list that does not exist."  Yet no list has been deleted since Friday and today.
    ERJ MCSD MCDBA
    Monday, September 20, 2010 4:35 PM
    1. If you put the full path, with the full domain name path, the error messages in the log go away.

    I attempted to fix this issue by specifying all links in Site Settings -> Navigation as full URLs starting with http://, rather than just the relative URLs that are used by default (and -should- be used, especially as our MOSS server is accessible through different domains for different purposes).

    This did remove the "There is no Web named..." errors, however I am now seeing the following error:

    8kh7  High    Cannot open "/<site coll>/<site>/http://<server>/<site coll>/<site>/Lists/<list name>/My Tasks.aspx": no such file or folder. 

     

    Which seems to agree with what Jennifer Anders had said earlier about some of the code in the publishing feature always using SPContext, regardless of the correct content. So even though I have "http://server/siteCollection/site/list/deaultView.aspx" as the URL in the Navigation settings, SP is still prefixing that with the current relative site path.

     

    I attempted to out-maneuver SP by changing the Navigation links to just "list/defaultView.aspx", assuming it would then prefix the "/siteCollection/site/" to it, but the JS validation on that Navigation page requires the link to start with either a protocol or slash, and disabling JS on the page breaks all functionality.

    Tuesday, January 18, 2011 3:22 PM
  • I am locking this thread started in 2008 because it is far too long and because the original question was answered long ago (somewhere but possibly not in the post marked as an answer - the text is such that I'm unclear as to whether "Bingo!" means a solution or not).

    If anyone feels they have a question open they should re-post it as a new thread with a suitable title.

    Moderator


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapter s
    Tuesday, January 18, 2011 4:05 PM