SharePoint 2010 Install & Powershell Issue on Windows Server 2008

PowerShell is an optional component available with the Windows Server 2008 default install.  If you enable this feature in Server Manager you will run into an issue when installing the pre-release version of SharePoint 2010.  2010 depends on the PowerShell CTP3 which cannot be installed without uninstalling the inbuilt PowerShell feature. 

To Uninstall PowerShell.  goto Server Manager and uncheck the PowerShell feature.

Now your 2010 install should proceed without any issues

Check this post below to review and download the various versions of Powershell

Getting Ready for SharePoint 2010

Last month at the SharePoint conference in Las Vegas, Microsoft unveiled the feature set and hardware requirements for SharePoint 2010.  2010 requires 64 bit hardware and that might mean a significant re-platforming of your existing developer machines.  With MOSS 2007 developers were free to run a test environment on their 32 bit machines using Virtual PC.  Bamboo Solutions even came up with an innovative solution to run MOSS 2007 locally on Vista machines

MOSS on Vista

However, If you are a SharePoint developer and you currently have a 32 bit machine, there are some significant changes coming down the road.

First, if you can, move on to a 64 bit platform.  Irrespective of whatever OS you run(Windows 7 , Vista or Windows Server 2008) moving to a 64 bit platform provides you the flexibility to run 64-bit 2010 Virtual machines natively using Hyper-V or VMWare Server or Virtual Box

If you are running Windows 7 and do not want to deal with VMs, there is an interesting option called “Boot from VHD” in Windows 7.  With this option,  you could boot directly into a Windows 7 or Windows Server 2008 test environment VHD and hence leverage all of your system resources within the VHD.  Here is a great post that talks about the steps to prepare a VHD and boot from it.

If you are stuck with a 32 bit machine and you are not part of a hardware refresh cycle, you have one option.  If your machine has a Intel/AMD chipset that supports virtualization, make sure to update your BIOS by visiting the manufacturer’s website.  Once your BIOS is updated, you should see an option to turn on Virtualization within your BIOS setup.  After turning on virtualization within the BIOS, you can run your 2010 VMs.  Currently,  VMWare Server 2.0 and Sun’s VirtualBox support running 64 bit guests on 32 bit hosts.   The performance of these VMs on 32 bit hosts leave a lot to be desired and is definitely not recommended for hard core SharePoint development.  You will be better off developing off of a Hyper-V or VMware Server hosting your VMs remotely.

SharePoint 2010 New Features

Microsoft has released a couple of sneak peek videos about SharePoint 2010 at

Here are some of my notes from these videos

Business Value

The SharePoint pie from MOSS 2007 has been changed for 2010.  Instead of focusing on generic portal topics, the focus is more on the business value of SharePoint.  Here is the new pie



Sites are all about sharing info with employees/partners/customers – empowering customers across all mediums
Team Sites, Internet Facing sites, extranets for customers and partners


Ad-Hoc Communities
Communities in terms of hierarchy (comes from AD)
Communities now include Business Partners. You could search for users who are non-employees


Collaboration Content
Line of Business Content
People Centric Content


FAST Search is integrated into SharePoint
Highly scalable Search engine
Emphasis on getting the right results on the first page
Enhanced People Search
Enhanced Business Data Search


Combination of all the above
Microsoft’s vision is a decision engine that brings other tools into unison


Help rapidly create dynamic business solutions
End user applications
Business Processes
Tools and integration with SharePoint Designer, Visual Studio

New Features

  1. Ribbon inside SharePoint
  2. Customizable Ribbon
  3. Contextual
  4. Removable and users have the option to go back to the MOSS 2007 interface
  5. Asynchronous user interface – minimal postbacks
  6. Dialogs employ DHTML effects to gray the background and provide user dialogs

Functionality previously available under the Content and Structure pages are now available in the main library

Multi select documents to checkout /check -in/delete etc.

Customization Capabilities

  1. Page edits are called Web-Edits – This replaces the Site Text and font etc.
  2. Live Preview of fonts/colors etc, similar to Office 2007
  3. Upload and modify Images directly instead of uploading first to a image library
  4. Picture Tools provide Resizing of pictures directly using the picture
  5. Changing styles like having borders etc. for images


  1. Add SilverLight web parts without additional configuration
  2. Just point the web part to a XAP file in a document library
    Interactive zoom is available on SilverLight web parts


  1. You can theme SharePoint using the same theme as PowerPoint
  2. e.g Upload a Powerpoint theme
    Choose the theme and apply it to the site
    Now the site looks like the Powerpoint slide
    You can preview a theme on the site before applying it
  3. Firefox is fully supported and can do the same things as IE
  4. Completely redesigned Sharepoint Designer with Ribbon

Visio Services

  1. Visio can connect to backend and visualize the data
  2. Can publish visio into SharePoint and can render them without the need for visio on the client (similar to Excel Services)
  3. This functionality is called Visio Services
  4. Can zoom in and zoom out of diagrams
  5. Needs a good Visio design first for Business processes

BDC is now Business Connectivity Services

  1. Can take LOB data offline using SharePoint workspace Manager(previously Groove)
  2. Tools in SPD and VS for modeling LOB entities
  3. External data are called Entities – they live in BCS and you can work with them in SPD
  4. External Content types based on these LOB entities can be created within SPD
  5. There is a browser within SPD which can browse SQL Databases and provide views/stored procs etc.
  6. You can right click on an entity and create CRUD operations on it using a simple wizard and publish from SPD
  7. External data gets converted to a list like view
  8. Users can filter and sort BCS data and work with it like they would with a SharePoint list
  9. Users can seamlessly update data in 2010, which will automatically update the LOB system
  10. You can create a Word template with BDC elements and publish to a library. When the user creates a new document they can pick those BCS entities within Office
  11. To take items offline use Groove – SharePoint workspace manager – Click on Sync to Computer
  12. Lists/Libraries are all synced
  13. LOB data flows offline in Groove
  14. Can edit LOB data when offline and sync back when connected

Whats New for Developers

  1. Visual Studio 2010  has Visual Web part Designer. No more building tables for layout. You can drag and drop and create controls within web parts, similar to ASP.NET forms
  2. Developer Dashboard – can allow any page to provide debug info
  3. LINQ for SharePoint has been released and allows developers to use LINQ objects to query SharePoint lists
  4. Client Object Model – can run code on the client using JS/.NET.  This is especially useful when building Silverlight applications
  5. Supports TFS , automated builds
  6. New Project Templates are available in Visual Studio 2010
  7. Comes with a SharePoint Server Explorer within VS
  8. Can lookup Sites/Lists etc. as just like SQL Explorer in visual studio
  9. Can automate post deployment tasks – no more post deploy batch files required, UI to specify deployment steps
  10. There is a BDC explorer within VS to explore LOB data from within VS
  11. Visual Web part project comes with Features and Packages automatically.  Complete drag and drop functionality to visually build a web part
  12. SilverLight can use Client Object Model to access list data using Microsoft.SharePoint.Client namespace
  13. Runs CAML queries asynch and provides a rich client side object model to access data

Whats New for Administrators

  1. New SharePoint best practices analyzer – Comes with a set of pre-built rules , You can build your own rule if you need. It can automatically correct issues provided you set it up to do so
  2. New Central Admin Console look and feel.  Items are grouped differently compared to the 2007 version
  3. New Backup and Restore Tools in the UI
  4. Visual Upgrade option – Can upgrade 2007 to 2010 and keep the old layout and customizations
  5. New SQL Logging Database – Developers can write code to log to this SQL database ,  Can write your own events into the logging database, Whole bunch of out of the box reports for logging
  6. Scalable List infrastructure –  Can control how many items get returned from a list , Can set happy hour deadlines to filter the number of items in a list based on time of day
  7. Unattached Content DB recovery – If you need to recover sites/lists from a DB backup you can do so without restoring it onto a temporary site. You can also – Browse content, Backup the site ,  Export site and all of this without restoring it onto a site
  8. Upgrade looks and feels like 2007  – Can preview the new look and feel and revert back to the old version

6 Things that you think will work in SharePoint but doesnt

  1. When you have a Gantt view of the Task List, Web part connections are unavailable.  Hence you cant filter a Gantt View using the Filter Web Parts
  2. DateTime columns cannot be used for Grouping in the Content Query Web Part out of the box
  3. You cannot use the PortalSiteMapProvider to retrieve Navigation items from another site collection
  4. If you have a Date Column in a List, it cannot be used as a Lookup Column on another List
  5. If you activate a Feature on a site and then save it as a Site template and create a new site from this template, the FeatureActivated code doesnt fire
  6. You cannot write back to a List from Excel 2007.  This was available in Excel 2003. You will need Access for writing back to a List from Office (Update: Refer to WorkerThread’s link below for an add-in)

If you have any more of these oddities, please post in the comments and I will update this list

Edit: When you use the Content Migration APIs to copy lists and libraries from one farm to another, person fields do not copy over correctly

Create Publishing Pages on custom Document Libraries in SharePoint

Have you ever wanted to create pages in your custom document libraries in MOSS 2007 ?

When you click on Create Page under Site Actions, it always defaults to the Pages library. Well not any more.

Here is a great post on how to work around that limitation.

Some things to note after making these changes

  1. Import the Microsoft.SharePoint.Publishing namespace in your custom page
  2. Enable the Page Content Type for the document library for it to show up in the dropdown list

Office 2007 Integration with SharePoint

One of the frequent questions we encounter from our customers is

“Why do I need Office 2007 and how does it integrate with MOSS 2007”

Here is a great post on the  integration of the different Office applications with SharePoint

MOSS 2007 ULS Logs Folder in 12 Hive is Empty!


The Microsoft VHD for MOSS 2007 is a great time saver.  You can download the VHD from here

Download MOSS 2007 VHD

I am working on a demo for BDC and ran into some issues.  As usual when I looked at the 12 hive folder there were no logs.  Not a single log file.  I logged into the Central Admin Console and setup the Logging parameters and still nothing. 

I thought this might be related to the Timer service being corrupted and hence restarted the timer as well to no avail.

Poking through the services, I noticed that the Windows SharePoint Services Tracing service was disabled.  I set the service to Automatic start and the logs started to fill up.  It makes sense to disable this in a VHD by default, but a valuable lesson was learned. When some one else builds an MOSS 2007 image, do not assume all the services are on!

System.IO.FileNotFoundException when creating SPSite objects using the SharePoint object model

This is one of the interesting errors that we encountered recently. A console application was developed for content migration from a file share to SharePoint with an Excel file for mapping the files to specific content types. The application was run on our test environment and everything seemed to work fine. Of course we wanted to run this over the weekend. Time for easy deployment right since it is all tested and ready right? Wrong! When deploying to the server we came across this error

“Provider not registered in this environment” . After a bit of googling we realized the issue. Our test environment was running a 32 bit SharePoint installation, whereas the production version was 64 bit. Since we were using Jet drivers to connect to the Excel spreadsheet, we had to retool our application or target a specific architecture(since 32 bit drivers are available on the server). We chose the second option. We set the target platform to x86 and deployed it on production.

Update: Here is the forum post with the link to the solution. Scroll down to the 3rd comment with a link to the vbtips site

Now we were seeing the dreaded System.IO.FileNotFoundException when creating SPSite objects in our code.

Apparently setting the target architecture to x86 and running the code on a x64 SharePoint installation, throws the FileNotFoundException. We changed the target architecture back to the default setting and had to retool the code to read the mappings using an Xml export.

Sharepoint – Managing Access Requests email

The SharePoint administrator for our client recently changed teams. She was still receiving all the access request emails and wanted us to move it to another user. This took quite a bit of snooping around, since the option is not available front and center in the Site Settings page. We looked at all the security groups and checked to see if there were any access request emails set up on the groups. All those groups looked fine, but she was still getting those emails. Then we looked at the site permissions and sure enough there was an option under Settings called Access Requests with her email in it.


SharePoint Single Signon Error 0x8063064a

Our environment had 2 front end servers with MOSS 2007. The single sign-on service was leveraged within the web parts and everything worked fine on one server. However the following message was found in the event log on the second front-end server.

Event Type:    Error

Event Source:    Office SharePoint Server

Event Category:    SSO

Event ID:    6494

Date:        7/1/2008

Time:        2:43:21 PM

User:        N/A


The Microsoft Single Sign-on (SSOSrv) service failed to store credentials for user <DOMAIN\UserName>, enterprise application definition postini. The error returned was 0x8063064a. For more information, see the Microsoft SharePoint Products and Technologies Software Development Kit (SDK).


The Microsoft Single Sign-On Service was running as “LocalSystem” on the second server. Once we changed that to run as the MOSS 2007 application pool account, everything started working back as usual.

%d bloggers like this: