Skip to main content

Chandima.Net Blog for SharePoint solutions

Go Search
Home
Blog
Demo
  

Chandima.NET > Chandima.Net Blog for SharePoint solutions > Categories
Troubleshooting Event 2436

Recently after I had configured a SharePoint farm I ran into this little error relating to the Search indexer. Found out this was related how the loopback adapter tries to resolve addresses when using Windows Authentication. The result is no matter how many times you try to crawl your SharePoint content sources (sites) you will get access denied for the Search content access account.

Detailed error message on the event log as follows.

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date:  04/11/2008
Time:  10:32:31 a.m.
User:  N/A
Computer: WLGSPDSPOINT02
Description:
The start address <http://myporal> cannot be crawled.

Context: Application 'SSPKBPRD', Catalog 'Portal_Content'

Details: Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0x80041205)

To fix this error follow these steps.

Specify host names for Search Indexer to work > http://support.microsoft.com/kb/896861

To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. Type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
7. Quit Registry Editor, and then restart the IISAdmin service.

SharePoint Post SP1 Infrastructure Update - August Cumulative Updates

Previously I posted about the major post SP 1 SharePoint Infrastructure Update which was released July and notes on some issues that were discovered post release.

Subsequently MSFT has released a cumulative update that addresses these issues. Needless to say that you should test these in your pre-deployment servers prior to installing on your production deployments.

To specifically address the prior mentioned Alternate Access Mapping Issue a Fix is now available on request. The download link and details about this fix is available via the following KB article.

http://support.microsoft.com/kb/956248/en-us

I haven' tested these thoroughly yet so I am unable to confirm or deny but this post is highlight the availability of the August Updates.

WSS 3.0 August Update

Detailed description of the update - 956057

http://support.microsoft.com/kb/956057/en-us

MOSS 2007 August Update

Detailed description of the update - 956056

http://support.microsoft.com/kb/956056/en-us

Detailed article on the SharePoint Team Blog

How do I list all my SharePoint sites in the Site Gallery?

When you create a site collection in SharePoint based on the OOTB starter template "Collaboration Portal Template" you get a series of sub sites such as "Document Center", "News", "Reports", "Search" and "Sites". Typically if your organisations has just installed SharePoint or are evaluating SharePoint this "Collaboration Portal Template" is the first place an end user will start their interaction with SharePoint.

 

SiteDirectoryDefault

One main point to note is that the slight variation of the available templates under the "Publishing" tab in Central Administration and on an existing SharePoint site which has been based on the  "Collaboration Portal Template" which is available the first time you create your starter site collection in the Central Administration Site when you first install and configure SharePoint. Typically this is done by your SharePoint Administrator at the beginning.

PublishingTemplatesSiteCollection PublishingTemplatesSubSite
Available via Central Administration Available via an existing SharePoint Site

I want go into too much details about these templates now since the point of this post is to highlight how you can list all your SharePoint sites in the "Site Directory".

One of the Site Templates that you can use to categorise and view all of your SharePoint sites is the "Site Directory" Template. Often the Site Directory template features and functionality are not used effectively due to the not so apparent configuration options that you or your SharePoint administrator need to configure to ensure that any SharePoint site and site collection created in your SharePoint farm is categorised and listed to provide you with a list of all sites. Effectively you can almost create a global categorisation of all your sites in your SharePoint deployment.

This process involves some thinking and a few configuration options that I will highlight.

Scenario: You want to create a single list of all your SharePoint site's that are being used in your organisation and you also want to minimise the overhead of categorising these manually. You also want your users with rights to create sites the ability to categorise the sites they create when they are creating them.

Master Site Directory

To ensure that any site and site collection being created within your SharePoint farm is listed in your "Site Directory" you need to add/configure the URL of your "Site Directory" in Central Administration. Go to Central Administration and to the Operations Tab. Under "Global Configuration" click on "Master site directory settings".

SiteDirectoryListingMaster

Once the URL of your master site directory has been set you can enforce the listing of new site collections in the Site Directory and ensure that you capture the correct Categorisation meta data for your sites. This settings effectively provides the Global location for your Master Site Directory. You may think that this is all it's required to list all the sites in the Site Directory but you also need to configure this at your site collection level in your deployment.

Site Directory Settings

Next step involves that you configure the "Site directory settings" to capture site categorisation when users create sites in an existing site collection. Go to Site Settings and select "Site directory settings".

SiteDirectorySettings

Once you configure the settings in the next screen accordingly you can enforce your site's to be listed in the Site Directory and capture the correct meta data against your sites. One decision that you may need to make is if you should allow users to create "Site Collections". Site Collections effectively provide isolation and portability. In large deployments particular types of sites depending on their use and functionality maybe better created as Site Collections. For users to be able to create  site collections Administrators need to enable "Self-Service Site Management" for the SharePoint web application.

SiteDirectorySettingsListing 

Once you enforce the listing of sites and site categorisations any site that is created by an end user will always be listed in the "Master Site Directory" .

To add some context to this consider this scenario. In my example I have a SharePoint Intranet/Portal where all employees are directed to access organisational information. The Intranet/Portal provides access to various functional business applications such as Collaboration sites and document management sites etc.  The URL of this SharePoint site is http://intranet/ In this deployment my SharePoint Administrator sets the Global Site Directory setting URL as http://intranet/SiteDirectory in Central Administration. I want all sites created within my organisation to be listed in this directory. Since I am the "Owner" of the Intranet I can enforce this at the Intranet/Portal level.

Furthermore certain departmental leads have the "Create Site Collection Permission" and are allowed to create own "Site Collections". The authority to create site collections is delegated by IT to these groups. Since the global setting enforces all sites and site collections to be listed in the "Site Directory" users are able to find any new site that is created in my deployment.

Also any new SharePoint web applications that are created in my Farm can be effectively listed in the Global Site Directory since the global setting enforces new Site Collections created via Central Administration on the same Farm to be listed in the Site Directory. When a new Site is created under the existing site structure the site can now be categorised and listed in the "Site Directory"

EnforceSiteListing

Once the site is created the site is listed under the correct Category.

SiteListed

Site Directory Links Scan

Another most often overlooked functional part of maintaining the Site Directory is hidden away in Central Administration. This is called "Site Directory Links Scan"

Effectively you can check for broken site links and get a report as well as update your site description listings in the Site Directory using Site Directory Links Scan. Site Directory Links Scan is available via the Operations tab in Central Administration.

LinksScan

The site property update is automated to reflect any changes you may apply to how the sites are categorised and listed in the Sites list in your Site Directory.

Once you have enabled Site Directory Links Scan you can also go to your SharePoint Site and from your Site Directory site select Site Settings and "Scan for Broken Links" which will initiate a manual scan. This will search the "Sites" list located in the Site Directory site for any changed or broken links.

ScanSiteDirectoryList

The scanner will provide you with options of what View you would like to scan and update you of the Scan progress.

ScanStart Scanning
   

Resources for Planning Sites and Site Collections

Default SharePoint Site Templates - End/Power User Oriented Content

Planning Process for creating Sites - TechNet IT Pro Content

Notes on the recently released Infrastructure Update for SharePoint

UPDATE [29 July 2008]: Infratsructure Update Known Issues

Please note that there are some issues with regards to this update and I highly recommend this update to be thoroughly tested prior to being deployed

Please notice that the Infrastructure Update [ http://support.microsoft.com/kb/951695 ] has been updated to include the following information with regards to AAM:

Known issues discovered after release of this update

  • Installing the Infrastructure Update in a SharePoint farm that uses Alternate Access Mapping with a reverse proxy or a network load balancer, such as in an extranet deployment, may cause some public URLs to become unresponsive.
  • Microsoft is aware of this issue and is developing a solution. Before installing the Infrastructure Update, customers who use this configuration should use a test environment to verify that public URLs remain accessible after the update is installed.

As previously mentioned here in my blog the infrastructure upgrade installation should be be planned since it will essentially take your SharePoint farm offline until the updates have been applied. The services that will be affected with this update include IIS, SharePoint Timer Service and the SharePoint Administration Service. These services will be stopped and started by the setup wizard during the update process.

Things you *Must* do when updating an existing SharePoint deployment

  • It is highly recommended that you have upgraded your server farm to WSS and MOSS Service Pack 1 level. (Honestly I think you must upgrade to SP1 before applying these updates)
  • You have to first install the WSS V3.0 update before installing the MOSS update.
  • Ensure that you use the correct version of each update on your farm. (Make sure to download the x86 update on x86 servers and x64 for the x64)

Infrastructure Update for Microsoft Office Servers (32-bit, 64-bit)

  • Logon with the "Setup Admin" account to each server when installing this update. This is the account that you used when you first installed SharePoint. If you don't know what this account is then it's time to find out. Don't even attempt to install this update if you don't have this account details. This should be a domain account in a farm deployment.
  • This update *must* be installed to all servers in your SharePoint server farm before running the configuration wizard. The recommended order for each server roles are as follows: Index server, Query server(s) and finally all Web front end servers.
  • Backup all of your Databases via your preferred backup method
  • Backup all of your Custom solution files that are deployed to your Web front end servers

This is an update and not a Service Pack hence the requirement to update WSS first then MOSS. You can skip the Config Wizard after the WSS install and install the MOSS update and run the wizard at the end.

If all goes well you should see the version number 12.0.0.6318 in the Servers in Farm page in Central Administration after the Config wizard finishes applying the updates.

Infra6318

 

Resources

On TechNet: Updates Resource Center for SharePoint Products and Technologies

Issues that are fixed in Windows SharePoint Services 3.0 by the Infrastructure Update

Description of the SharePoint Server 2007 issues that are fixed by the Infrastructure Update


Infrastructure Updates for SharePoint (KB951297 - MOSS and KB951695 - WSS)

Via the ECM Team and SharePoint Team Blog

SharePoint related Infrastructure updates are now available for download.

To understand the issues fixed in these releases please read the following blog posts.

Content Deployment and Infrastructure Update - ECM Team Blog


It is strongly recommended that you install Windows SharePoint Services 3.0 Service Pack 1 and Office Servers Service Pack 1 before installing the
Infrastructure Update for Microsoft Office Servers (KB951297) and the Infrastructure Update for Windows SharePoint Services 3.0 (KB951695).

The installation process will incur server and farm downtime that you will need to plan for – updates should be installed on all servers in a farm. Please refer to the TechNet SharePoint Service Pack 1 deployment article.

 

The Infrastructure Update for Microsoft Office Servers (KB951297) applies to:

  • Microsoft Office SharePoint Server 2007
  • Microsoft Office Project Server 2007
  • Microsoft Search Server 2008
  • Microsoft Search Server 2008 Express

The Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) applies to:

  • Windows SharePoint Services 3.0

The Infrastructure Update for Microsoft Office Project 2007 (KB951547) applies to:

  • Microsoft Office Project Professional 2007

Read the detailed post about the Infrastructure update on the SharePoint Team Blog.

Here is a summary of the Content Deployment issues addressed in the Infrastructure Update:

Incremental bug fixes:

  • Incremental import can fail if a feature with a custom content type has been reactivated on the destination.
  • Unpublished pages do not get unpublished on the destination.
  • Reinheriting permissions on the source does not propagate incrementally.
  • Deleting a permission level on the source causes a "Permission level cannot be found." exception during incremental import.
  • Incremental behavior with the Recycle Bin improved. Incremental import fails with a "FatalError: You cannot perform this action on a checked out document." exception.
  • "Violation of PRIMARY KEY constraint" error during export.
  • Document "Title" field does not get deployed by incremental deployment in some cases.
  • In some cases, making permissions changes on the source or destination will result in a "The specified name is already in use." error.
  • Deleting or renaming an item then creating one with the same name causes incremental deployment to fail.
  • Incremental deployment fails when pages have independent permission settings.
  • Deleting a file and folder can cause incremental deployment to fail in some cases.

Other bug fixes:

  • Removing a User from a group does not propagate to the destination during incremental deployment.
  • Some source web settings related to search are not propagated to the destination.
  • Content Deployment can time out incorrectly on large deployment jobs.
  • Miscellaneous SQL deadlocks.
  • Quick deployment jobs behave incorrectly when Variations is used.
  • Quick deployment fails when pages are Quick Deployed while the Quick Deploy job is running.
  • Running One-time jobs manually can fail.
  • In some cases, a content deployment job can get stuck in a "Preparing" state forever.
  • Deployment sometimes unghosts items that are ghosted on the source.
  • Custom master page settings on the source are not propagated to the destination during deployment.
  • Content deployment fails when compression is disabled.
Recently Released Post SP 1 updates for SharePoint

As most of you know SharePoint Service Pack 1 was released some time ago which included some must have updates for your deployment. If you still have not updated your servers to SP1 well.. better get on to it because it is something that should be done. Applying SP 1 should not be major task in fact it should be part of your routine maintenance to update your servers with service packs.

I also pointed out about the availability of the SharePoint Administration Toolkit which is a good addition to your deployment with more advanced admin releases on the way.

Since SP 1 there are some other significant updates that are available for your deployment that you should look at on a case by case basis.

I want to point out that these should be requested according to your own situation and then applied to your servers. if you have been getting a lot of 7076, 6398 and 6432 errors in your event log then you need a recently released IIS6 hotfix for Windows Server 2003. The KB is IIS6 946517. I previously posted this error and a resolution prior to this fix being released.

This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this occurs, you may find that:

  • In SharePoint Server 2007, tasks that are scheduled do not run.

  • When you try to manage IIS 6.0 by using Server Manager, you receive a blank page, or you receive the following error message: "the path specified cannot be used at this time".

The Event ID's 7076, 6398 and 6432 and memory error messages described above will also be recorded in the Application Event Logs.

Microsoft now has a KB article describing this problem http://support.microsoft.com/?id=946517 along with details of the fix and how to obtain it. This can be applied regardless of your SharePoint service pack level.

The following are the updates that are available from MSFT for download.

Thanks to Spence for posting the full list of the Post SP1 Update Releases in his blog.

One of the key post SP1 releases that relate to Content Deployment is the 952698 for WSS and 952704 for MOSS which was released on 20 May 2008 and is available on demand. You should consider this if you are experiencing issues with content deployment between your servers.

SharePoint Administration Toolkit

About one month ago (April 30th 2008) Zach Rosenfield (SharePoint Program Manager - Infrastructure) announced on his blog about the availability of the SharePoint Administration Toolkit. The Toolkit is the first in a series of updates that you should consider to be deployed into your SharePoint farm deployment. I haven't had the time to test this out hence the delayed post.

This update will add the following capabilities to your SharePoint farm.

  • A new menu named "Batch Site Manager" with a link to "Move, Lock and Delete Site Collections"
  • A new STSADM command to update user alerts to a new URL when a site has been moved

Let me explain what these mean and what you'll need to consider for deploying this update to your farm.

There are two installers available for x86 and x64 and you can download the correct version of the SharePoint Administration Toolkit from the following locations.

x64: http://www.microsoft.com/downloads/details.aspx?FamilyId=F8EEA8F0-FA30-4C10-ABC9-217EEACEC9CE&displaylang=en

x86: http://www.microsoft.com/downloads/details.aspx?FamilyId=263CD480-F6EB-4FA3-9F2E-2D47618505F2&displaylang=en  

Before you hit the install button after your download you should read the release white paper for SharePoint Administration Toolkit (MS Word) about known issues and how to install this on your farm. There are differences between the x64 install and x86 install.

Here are some basics you should know when installing and using the new updates.

  • You must be a local administrator of the server and also belong to the SharePoint farm administrator group in your SharePoint farm to install this update (Most common for updates)
  • You should run the "Move, Lock and Delete Site Collections" option from the server where the "Central Administration Service" is running. Basically this is your primary server in your farm
  • If your farm has not been updated to Service Pack 1 of SharePoint you should first consider upgrading (Although you can still use the commands you *may* encounter Timer job errors)
  • For x64 edition first run the "MicrosoftSharePointAdministrationToolkit.exe" from your download location and then you will need to manually run the following commands.

 

From a command prompt, navigate to the following location:
%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin

Type the following commands (without the quotation marks):

“psconfig –cmd applicationcontent –install”
“stsadm –o installfeature –name BatchSiteManagerLinks”

  • When you first navigate to the "Move Lock and Delete Site Collections Screen" you will need to "Update Statistics Aggregation". (Would have been nice if the link was on the actual word than on click here.)

 

BatchSites
The Move Lock and Delete Site Collections Screen once statistics have been updated. In this demo server I have two content databases for my Web Application. One for My Sites content and the other for a single site collection.

  • The Move Lock and Delete Site Collections option only shows 100 site collections. So if you are doing more than 100 site collection moves soon as you move to 101 you'll lose what you selected in the previous screen. In any case you should not Move hundreds of site collections on one go since that will put quite a heavy load on your farm as well as SQL server. Make sure that you schedule these after hours according to your SLA requirements. Users will lose access to your sites when the Move site operation is running. Attempting to access the sites will result in a failed Move operation. So it is required that you should "lock" the sites prior to the planned move.
  • You can only Move Site Collections within the same web application. So this means you can only go from Single web app to multiple content databases. To move from one web application to another consider using the STSADM -o export command.
  • You can only run one move operation at a time. Don't run multiple and make sure that the previous operation was successful before running the next. Do not attempt to remove already running timer jobs for move operations.
  • Make sure you backup your sites prior to doing any of the operations to ensure recoverability to previous state in case something goes wrong.
  • Once a site collection move has been finalised use the "STSADM -o updatealert" command to change the Alert URL's of the site collections existing alerts.
    • Updatealert operation will only work correctly if the URLs specified with the url and oldurl parameters reside in the same site collection. This is necessary to allow proper updating of alerts in a specific zone. Zones are defined when you create your SharePoint farm. This is when you have different URL's for accessing your sites via alternate access mappings (AAM). If you don't know what AAM's are I highly recommend this article titled "What Every SharePoint Administrator Need to know about Alternate Access Mappings" . SharePoint needs to update these on it's own.

 

Most of what I highlighted above is available on the Release white paper for SharePoint Administration Toolkit.


If you are installing on a x86 platform you will see a similar screen if your install was successful.

AdminToolkit