Search results matching tags 'SharePoint 2007' and 'SharePoint'

SharePoint Navigation broken after migration from 2007 to 2010

Bas — Tue, 05 Jul 2011 22:02:00 GMT

When migrating from SharePoint 2007 to SharePoint 2010, it might be possible that your navigation is broken. The error I encountered was the following, but it can occur in more functions within the Navigation namespace.

Object Reference not set to an instance of an object. Stacktrace: at Microsoft.SharePoint.Publishing.Navigation.PortalSiteWebSiteMapNode.FetchDynamicItems(PublishingWeb pubWeb, NodeTypes includedTypes, Boolean& websFetched, Boolean& pagesFetched) at Microsoft.SharePoint.Publishing.Navigation.PortalWebSiteMapNode.PopulateNavigationChildrenInner(NodeTypes includedTypes)

This error can arise when you restored a SharePoint site to SharePoint 2010, and that site was created in a language which had it's default "Pages Library" location changed.

for example

English pages library was located at "Pages" and not changed
The German pages library was called "Seiten" (if i recall it correctly), and is not changed
The dutch pages library was called "Pages" (and thus, not localized), but has the default location of "Paginas" in SharePoint 2010 (so it's location was changed)

When a SP2007 site is migrated to SP2010, the navigation provider expects that any changes to the default location, is stored in a specific property, which, apparently, isn't the case, after a migration.

Luckily, Microsoft provided a powershell for this to fix it. And no, it has not been fixed in SP1. Check the following link for the exact cause and resolution:
http://support.microsoft.com/kb/2484317

Using SharePoint 2007 Site Templates in SharePoint 2010

hvdkamp — Wed, 01 Dec 2010 20:10:44 GMT

In SharePoint 2007 it is possible to create site templates based on an existing site. A template can be used to create new site collections and subsites based on that template. When you export a site template, it creates a .stp file for you. Copying this .stp file over to an other evironment gives you the possibility to start using your template over there also.

In SharePoint 2010 site templates are still there. You can create site templates, but these are created as .wsp files instead of .stp files. This gives you the advantage of importing this .wsp into Visual Studio and make solutions based on it.

If you have a SharePoint 2007 Site Template, you cannot export it as a .stp file and import it into SharePoint 2010. The approach for getting your SharePoint 2007 Site Template into SharePoint 2010 is as follows:

Setup a SharePoint 2007 environment
Create a SharePoint 2007 site using the .STP site template
Backup the SharePoint 2007 site
Restore the SharePoint site into a SharePoint 2010 environment
If needed update your site, so that it matches the SharePoint 2010 v4 masterpage and makes use of the new SharePoint 2010 features.
Export your site into a new Site Template

Now you have your SharePoint 2007 Site Template converted into SharePoint 2010, so you can use it to make site collections and subsites based on that template.

Booting from VHD files and using Windows Server 2008 R2 as a Workstation

hvdkamp — Thu, 22 Jul 2010 07:39:35 GMT

For my work I'm using a laptop that has several operating systems installed. Depending on the customer related work, e.g. office work, giving presentations and developing software, I'm booting one of these environments.

My multi-boot installation consists of several environments including:

Windows 7
Windows Server 2008 R2 with SharePoint 2007
Windows Server 2008 R2 with SharePoint 2010
Windows Server 2008 R2 with SharePoint 2007 and Dynamics CRM 4.0.

All the operating systems boot from a virtual hard disk instead of using virtualization by booting an operating system that hosts an other operating system.

I prefer using VHD files and booting from them because of several reason, e.g.:

The whole virtual memory is available for use on the work environment, instead of loosing virtual memory to an operating system that hosts a guest operation system using virtualization
Creating backups of a whole operating system is easily done by just backing up one .vhd file.
Normal hardware and drivers are used instead of emulated hardware and drivers.
By creating a clean installed base environment, you can quickly go back to that state or derive environments based on the base environment.

People often ask me:

How do you install operating systems on a VHD file and setup up a multi-boot environment?
How can you boot from a virtual hard disk?
What did you change to your Windows Server 2008 environment so that it looks like Windows 7?

You can get answers to all of these questions by visiting "How can I install Windows 7 or Windows Server 2008 R2 to a virtual hard disk (VHD) file?" about how to install an operating system on a VHD. Visit Win2008r2workstation.com which explains how to convert your Windows Server 2008 R2 server to a workstation.

Ramp Up learning program

hvdkamp — Mon, 10 Nov 2008 20:46:00 GMT

Ramp Up is a new learning program on the MSDN website.

About Ramp Up:

Introduction
Take the Next Step on Your Career Path
Ramp Up is a free, online, community-based learning program, with a number of different tracks that will help you build your portfolio of professional development skills. Ramp Up has a solid foundation of premium technical content from subject-matter gurus, and provides easy-to-access content in a variety of forms that guide you in learning the important skills. Join Ramp Up (it's free!) and help advance your career - click on a track now to start!

Benefits
Take the Next Step on Your Career Path
Ramp Up is a free, online, community-based learning program, with a number of different tracks that will help you build your portfolio of professional development skills. Ramp Up has a solid foundation of premium technical content from subject-matter gurus, and provides easy-to-access content in a variety of forms that guide you in learning the important skills. Join Ramp Up (it's free!) and help advance your career - click on a track now to start!

At the moment you can focus on the tracks: SharePoint for developers (part 1), Visual Studio 2008, Aspiring Developer, Java Developer, Visual Sudio 6.0 Developer, Visual Studio 2002/2003 Developer.

Good to see a SharePoint track already. Part 1 of the SharePoint developers track is focused on:

As a developer, would you like to learn more about Microsoft Office SharePoint Server (MOSS)? MOSS is based on Microsoft Windows SharePoint Services, which gives developers the opportunity to get more problems solved with less effort. Windows SharePoint Services 3.0 takes full advantage of Microsoft ASP.NET and the Microsoft .NET runtime. The new features and added programmability support in MOSS provide a wealth of development opportunities. This course will immerse you in many of the developer-centric capabilities of Microsoft Office SharePoint Server.

Level 1: Web Parts
Did you know that in SharePoint you can build pages as easy as in ASP.NET – and allow end users to create dashboards? Web parts allow for creating components of Web user interface that can be reused on multiple Web pages. These are introduced in ASP.NET and built on in SharePoint where they can be added to pages by end users and managed by IT Professionals. In this topic you will learn about building simple Web parts for SharePoint and how to connect them back to SharePoint site data.

Level 2: Data Lists
Did you know that SharePoint developers can work with data from lists that users get access to too? Data lists provide data storage for end users in SharePoint. End users can create lists with schema all through the SharePoint user interface and they can create, edit, and view the data. All of this data can be programmatically accessed by developers and this topic is all about that.

Level 3: Event Handlers
Did you know that SharePoint developers can automatically process data that your users upload via a spreadsheet? Event handlers (or event receivers) are custom code that runs on the SharePoint server in response to something that happens on the server. Event handlers can be useful for running business logic in response to data being added to the site. This topic shows how to create simple event handlers and investigates ways that event handlers can be used in SharePoint.

Level 4: Workflow
Did you know that you can write WF workflows in SharePoint without having to worry about storage, persistence, or how to interact with the user? Workflow in SharePoint allows for implementation of processes that require interaction such as email approvals or form completion by people in your organization. This topic shows you how to create simple workflows in SharePoint using Visual Studio that involve approvals from people by email and for meeting room resource bookings with an administrator.

Level 5: Silverlight Web Parts
Did you know that you can build rich Internet applications with SharePoint? Silverlight is a new Web user interface technology from Microsoft that allows for each implementation of animations and videos. This topic shows how a SharePoint user interface can be enhanced by using Silverlight in Web parts as part of a SharePoint site.

Index PDF documents on SharePoint using Adobe PDF IFilter 9

hvdkamp — Thu, 02 Oct 2008 13:30:00 GMT

Using the SharePoint Search you can find documents based on their filename, metadata or content within a document. By default the content of Office documents is indexed by the SharePoint crawler, but PDF files are not crawled. To add support for PDF files you have to add an IFilter which the SharePoint crawler uses to read through PDF files and add the information to the search index.

To obtain an IFilter for PDF you can purchase the Foxit PDF IFilter from Foxit Software. There is also a free PDF IFilter available from Adobe which does exactly what you need and what this post is all about.

Getting Adobe IFilter 9 to work with SharePoint

In earlier days you were required to download Adobe's IFilter as a separate file. Since Adobe 8.0 it is included within the Adobe Acrobat and Adobe Reader products. The current version of Adobe Reader is 9.0 includes an IFilter that is compatible with the latest PDF implementations.

To enable PDF indexing use the following steps:

Download Adobe Reader 9.0, which includes IFilter 9.0.0.0, from http://www.adobe.com/products/acrobat/
Download the Acrobat PDF Picture, to display in front of PDF search result items, from http://www.adobe.com/misc/linking.html
Add the PDF file type to the Extensions List for WSS search by editing the registry
- Start regedit
- Open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\{Random GUID}\Gather\Search\Extensions\ExtensionList
- Add PDF to the list as a new String Value. Use a new high value e.g. if 37 is the highest value, use "38" as the key with the value "pdf"
Add the Acrobat PDF picture to the SharePoint templates directory. Copy the Acrobat PDF picture called pdficon_small.gif in the 12 Hive\TEMPLATE\IMAGES folder, e.g. %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\IMAGES.
Bind the Acrobat PDF picture to the PDF file type
- Open the 12 Hive\TEMPLATE\XML\DOCICON.XML file
- Find the <DocIcons.ByExtension> part
- Add the following mapping:
  <mapping Key="pdf" Value="pdficon_small.gif" OpenControl="" />
Change IFilter mapping in registry
- Start regedit
- Open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\
- Add (or modify) the .pdf key
- Add a Multi-String value with value {E8978DA6-047F-4E3D-9C78-CDBE46041603} or modify if another GUID value already exists.
- Open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\
- Add (or modify) the .pdf key
- Add a Multi-String value with value {E8978DA6-047F-4E3D-9C78-CDBE46041603} or modify if another GUID value already exists.
Add the Adobe Reader folder to the environment path variable
- Right Click on My Computer
- Open Properties
- Open the Advanced tab
- Go to the Environment variables
- Edit the Path variable
- Add your Reader folder to the Path list, e.g. C:\Program Files\Adobe\Reader 9.0\Reader
Restart the Search service by restarting your server or executing the following commands:
- Run: net stop osearch
- Run: net start osearch
Crawl the PDF documents
- Existing PDF documents that were crawled before the Adobe PDF IFilter has been installed are not indexed during an incremental crawl. You have to edit each existing PDF file to trigger the crawler to reindex the file during an incremental crawl. It´s easier to run a full crawl after you have installed the Adobe PDF IFilter.

Now all PDF documents are crawled you can query on content inside a PDF document.