Archive for June 30, 2009

Getting Ready for SharePoint 2010

The Microsoft SharePoint Product Team released some preliminary system requirements on their blog. We have known for some time that SharePoint 2010 will only ship in 64-bit flavor, but I was surprised to learn that there is a requirement that the SQL Server back-end must also be 64-bit.

http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx

Bottom line: you need to be thinking about 64-bit architectures for your core infrastructure. This will cause some pain for some firms who have resisted the move.

Brian Berry is a Director of Technology Consulting with BlumShapiro, focusing on Microsoft Business Intelligence solutions, with a strong focus on Systems Integration, Master Data Management and PerformancePoint Services. He has been helping companies optimize their investments in Microsoft technology for over 12 years.

Installing PerformancePoint Server SP2

This morning, I installed PerformancePoint Server in a standalone development environment. This was an opportunity for me to work through the complexities of using SQL Server 2008 as the Monitoring Database. This TechNet article helped a good deal: http://technet.microsoft.com/en-us/library/dd335966.aspx

Usually, when installing PPS, I use the Planning and Architecture Guide to remind myself of the various prerequisite libraries which PPS needs in order to work with SQL Server. These include SQL Native Client, AJAX 1.0, ADOMD.NET SP2, Analysis Services OLE SP2 and SQL XML 6.0. Knowing that I need these components, I like to download and install them first before insert the PPS media.

I did this before I realized that I did not have an instance of SQL Server running locally, and I did not have the SQL Server 2005 media handy. No problem: I’ll use SQL Server 2008 Developer Edition for my development environment.

However, I learned that if you do this, rather than following the steps explicitly in the TechNet documentation, the PPS Monitoring Configuration will complain that ADOMD.NET SP2 is not installed. I suspect this is a consequence of installing SQL Server 2008 after installing the SQL 2005 Client components. The documentation sends you to a link for this component, which is a Hot Fix Download; one of those you must explicitly request in order to gain access to. I found that the email contained a broken link.

Fortunately, I found that repairing the installation of ADOMD.NET SP2 within “Programs and Features” fixed my problem; the configuration manager passed all checks.

Finally, it is important to note that you should install both PPS RTM and SP2 versions first before attempting to configure. If you do not, the configuration tool will not see the SQL Server 2008 instance which you intend to use as your Monitoring Database.

Enjoy!

Brian Berry is a Director of Technology Consulting with BlumShapiro, focusing on Microsoft Business Intelligence solutions, with a strong focus on Systems Integration, Master Data Management and PerformancePoint Services. He has been helping companies optimize their investments in Microsoft technology for over 12 years.