locked
Sharepoint issues after MOSS sp1,sp2, WSS updates RRS feed

  • Question

  • We had a site collection running more or less ok, on old hardware, and we decided it was time to install service packs for MOSS and WSS so that the site could be migrated to 2010 on a new server. This is where the problems started, just getting the updates installed took a lot of troubleshooting with service accounts, sql permissions etc. Now we get constant issues with clients connecting to the site; weird formatting on the page, script errors in the browser, login prompts, and errors opening documents. Sometimes these problems seem to go away for the day after a reboot or iisreset, and we are flailing away trying to find the magic settings in IIS, Central Administration, and SQL server (2005) to get everything working normally. Our sharepoint server, SP-MON, seems fine if we browse it locally on the server, but if we access it using its alias (http://sharepoint ) from a client, the errors abound. It is also inaccessible from a client using http://sp-mon (authentication prompts), which wasn't always the case.
    This is a single server farm, currently using spadmin account (local administrator, db_owner on dbs) to run most services.

    Thanks for any help or ideas you can provide!

    one consistent error showing up in the app log throughout all this is a 2436 error, every 5 minutes:

    The start address <sts3://sp-mon:28437/contentdbid={31b337c5-dea7-4c0e-aec5-4e64a3ac0a4b}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:
        The object was not found.   (0x80041201)

    and I've also started seeing this WSS 6875 error:

    Error loading and running event receiver Microsoft.SharePoint.Publishing.Internal.PublishingWebEventReceiver in Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Additional information is below.

    : Access denied.

    Monday, March 7, 2011 9:04 PM

All replies

  • Hi Imoss,

     

    The error 2436 occurs if text files are blocked on the Blocked File Types page in SharePoint Server 2007. The gatherer is unable to access the Robots.txt file when it starts to crawl the specified URL. You can refer to this KB article to get more detailed information and solution about this problem: http://support.microsoft.com/kb/952172.

     

    And the error 6875 occurs if the following conditions are true:

    1.       You use the Publishing Portal template to create a collection.

    2.       You create a page when major versioning is turned on.

    For this error, you can go through this KB article: http://support.microsoft.com/kb/948323. You can get solution for this issue there.

     

    Thanks & Regards,

    Peng Lei

    Tuesday, March 8, 2011 2:25 AM
  • Thanks for the reply, somehow I hadn't seen those kb articles yet - unfortunately, the solution for the 2436 errors doesn't apply in my case. The .txt file extension is not on the block list for any of my web apps.
    It looks like 6875 is not a real problem.

     

    any ideas about what settings could cause users from having these problems browsing the site, but for it to work perfectly locally on the server? something with IIS? Sometimes having the user press refresh seems to improve the visual glitches momentarily.

    Tuesday, March 8, 2011 12:19 PM