You are currently browsing the tag archive for the ‘SharePoint 2010’ tag.

Now with SharePoint and Dynamics CRM running on the same dev box, attaching to a Process ID can become a challenge in identifying which one is what.

Luckily, IIS comes to the rescue. In a command prompt, run appcmd with the list command to list all the worker processes and the associated application pools. The command looks like so:

appcmd list wp

you need to have the PATH mapped to C:\Windows\System32\inetsrv

Now you don’t have to attach the VS debugged to all w3wp processes, just pick the one you want to debug against.


At the Central Administration Level (across the farm)

Open up Central Administration > Application Management

Under “Service Applications” click on Manage service applications


Click on Search Service Application


Under Queries and Results on the Quick navigation click on Scopes

From here on instructions are identical to the steps performed at the Site collection Level.

At the Site Collection Level

Site Actions > Site Settings

Under “Site Collection Administration”, click on Search Scopes


Here you can create new scopes, and edit the custom scopes. Once a scope is created, you have to add rules for crawling.


Pay close attention to how you can structure include/exclude settings to capture only a certain section of a network share:



This is something simple, but I’ve been asked several times about it already, so I’m going to post instructions here on how to achieve this.

Requirement: Store documents and links to documents in the same library


1. Create a Document Library within your site

2. In Library Settings > Advanced Settings enable management of content types

3. Add content type from existing site content types

4. Select and add Link to a Document as a new second content type


5. Start adding content using both content types:


Now you can store in the same document library both Documents and Links to external documents.

Hope this helps, enjoy!

So you’ve set-up your account to be a farm admin, and you’re trying to deploy your solution. But you get the message above.

That is because, even though you are a farm admin, your account does not have the proper permissions to the SQL database.

Check that first. Keep in mind, in 2007 certain update could cause this behavior, in which case just restart the DB service.


  • The farm is unavailable
  • Object reference not set to an instance of an object.

The following permissions are required to allow you to deploy a solution:

  • Farm Administrator (Central Admin)
  • db_owner and db_securityadmin on the config database
  • Local admin on the servers

As you’ve probably seen by now, once you create multiple site collections in the same web application, you don’t get a lot of options as far as database location. Well, it’s really not that complicated:

  • Create the databases for the new site collections (easy enough in CA)
  • Run the following PowerShell command for each site collection, or put it in a script if you feel like it:

Move-SPSite <YourSiteURL> –DestinationDatabase <ContentDBName>

That’s it, easy as pie. See more information on TechNet:


MVP Reconnect

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 617 other followers

Follow Dynamics 365 Wizardry on