Skip to main content

Posts

Showing posts from 2011

SharePoint 2010 Content Migration - PDF icons don't appear in document libraries

Description

When a document library includes PDF files, by default these file’s icons are displayed with the generic “blank” icon.
Resolution

Upload the .gif file for the PDF icon to C:\Program Files\Common Files\Microsoft Shared\Web server extensions\14\Template\Images
Update the Docicon.xml file in the following folder C:\Program Files\Common Files\Microsoft Shared\Web server extensions\14\Template\Xml\ to include the following node: <Mapping Key="pdf" Value="NameofIconFile.gif"/>
Restart IIS after making the change
Details on how to perform this for all versions of SharePoint are available at this Microsoft KnowledgeBase article.

SharePoint 2010 Content Migration - Custom Content Query Web Part doesn’t show some Lookup data from underlying list

Description

Fields used in a custom CQWP that are of "Lookup" type don’t render out correctly. This occurs when the CQWP is designed to strip extraneous information from the values of the Lookup field
Resolution

Updates to the custom CQWP .webpart file, and the associated XSLT file are required. Ensure the .webpart file refers to the Lookup field as a “Lookup” type in the CommonViewFields node, and update the XSL file associated to the CQWP to no longer remove characters prior to a “#” character (SharePoint 2010’s CQWP parses the data from a Lookup field without the pure “2;#Value” style rendering, instead the looked up value comes out in the CQWP as “Value”)

SharePoint 2010 Content Migration - Discussion Boards web parts don’t function

Description

Discussion Board web parts that exist on pages throughout the site don’t work. When you select a link to view a Discussion Board thread, the link doesn’t send you to the thread details. Instead it sends you back to the same page, but the Discussion Board web part is emptied
Resolution

Ensure SharePoint Server 2010 SP1 and the SharePoint Server 2010 June 2011 Cumulative Update is installed prior to performing the db attach upgrade.

SharePoint 2010 Content Migration - Broken images on Contact Details web part

Description

If you're migrating some content from your MOSS 2007 environment, but staff photos are remaining at their original location, profile data included in content (i.e. in Contact Details Web Parts) may include source addresses that are updated via the database-attach approach to refer to the new 2010 site collection’s host name.
Resolution

Possible resolution is to ensure a profile sync is done from Active Directory and subsequently perform profile sync to site collections (run the respective Timer Jobs), after the site collection is migrated

SharePoint 2010 Content Migration - links that use relative URLs

Description

Some links defined in the content of sub-sites refer to relative URLs for pages outside of the Team Centre site collection.
Resolution

Request site owners to update links in navigation, so absolute paths including hostnames are used instead of relative links (to be performed retrospectively, after content migration has occurred)
Implement redirect handling on the SharePoint 2010 site(s) to “catch” any requests to the relative address

SharePoint 2010 Content Migration - left-hand navigation and absolute URLs

Description

Some navigation items defined in sub-sites refer to the absolute web address (including host name). This may include nav items that have been defined by administrators or site owners over the years.
Resolution

Request site owners to update links in navigation, so server relative paths are used instead of absolute host name links (to be performed retrospectively, after content migration has taken place)
If like us, your old MOSS 2007 site will run in parallel with the new site, implement redirect handling on the MOSS 2007 environment to “catch” any requests to the old address

SharePoint 2010 Content Migration - Custom site map provider

Our Intranet site has a custom site map provider - which is used across all site collections to consistently display the same navigation regardless of where the user is on the site.

Description of problem

A custom site map provider is used in the custom master page across the entire site collection. This site map provider is used to ensure consistent site architecture for the top navigation bar
Resolution

Add the custom site map provider to all web applications' web.config files (except the web.config for Central Admin, and SharePoint web services). If thecustom site map provider is an XML based provider, ensure the .sitemap file is also uploaded to the appropriate location on the server (in our case, it's under 14\TEMPLATE\LAYOUTS\customername\customerTopNav.sitemap)

MOSS 2007 to SharePoint Server 2010 upgrade

I haven't posted to this blog for a while, but I have been working on a number of things including an upgrade of my employer's MOSS 2007 environment to SharePoint Server 2010. One of the key areas is to get the content from one environment to another, and there is one section of our Intranet - that soley contains MOSS 2007 Team Sites - that is practically ready to go.

So in the coming days I'm going to post details of a few problems we've encountered. Hopefully none of them are too obscure, so the information I'm putting out there is actually useful to others who might be embarking on a similar project.

SharePoint 2010 Foundation Event Viewer errors refer to old GUID database names

After going through the steps of removing GUIDs from the default SharePoint 2010 databases, I noticed a whole lot of Event Log critical errors listed against the SharePoint Foundation source column. Specifically, these errors would refer to the old database name of the Content DB for Central Admin.

The Event log errors would look something like this:

SQL Database 'SharePoint_AdminContent_28d23664-bca8-4408-99dc-12fe65cd3f96' on SQL Server instance 'xxx' not found. Additional error information from SQL Server is included below.


Cannot open database "SharePoint_AdminContent_28d23664-bca8-4408-99dc-12fe65cd3f96" requested by the login. The login failed.

Login failed for user 'yyy'.

After performing the steps (e.g. what's listed in this blog post by Dirk Van den Berghe) to change the Central Admin's content db name (aka. SharePoint_AdminContent_[guid]), there seems to be a missing step. After moving the content around and perhaps (if you're brave) …

SharePoint List-based 404 handler

A project that I'm involved in is about to begin, which includes a complete refresh of our Intranet site, based on SharePoint. One of the key requirements of the refresh is to look at the Information Architecture, and look at ways of making it easier to find content for the typical user.

As you may know, dealing with a major site re-architecture like this will innevitably mean links strewn around the place that refer to old content. These might be favourites on users' web browsers, links on other websites, and indeed links throughout the content of your SharePoint site. Some may be updated within the SharePoint site, but a large proportion of them remain static due to various factors such as them being defined in Content Editor Web Parts, or the like.

As it stands, the SharePoint site in question doesn't have any custom 404 page handling already, so even now when minor changes occur to the Information Architecture of the site, old links are left behind without any thought…