I don’t usually steal all of Christophe’s blog postings but this one is worth it. Mostly planning content at the moment – but expect a ton more as we go through November and the Beta release. Certainly worth bookmarking for future reference. And if I get time I will be hanging out on the forums, along with my European colleague Alex. See you there!
We are pleased to announce the availability of the following Microsoft Project 2010 technical resources, save these bookmarks!
TechNet Project 2010 TechCenter
At http://technet.microsoft.com/en-us/projectserver/ee263909.aspx the following areas are covered for IT Professionals:
MSDN Project 2010 Developer Center
At http://msdn.microsoft.com/project/ developers will find a growing list of resources including Project 2010 Beta Software Development Kit (SDK) as we move closer to Project 2010 Beta in November.
Project 2010 Forums
Get all of your Project 2010 end-user, IT Professional and Developer questions answered by product experts from Microsoft and the community (Project MVPs):
Please note this is the first milestone of a journey, new content will continuously flow to these sites.
Thanks to the Product Group, our partners in Office Sustained Engineering partners and of course Rob – who keeps this all running smoothly from the support side - we now have a new set of Cumulative Updates! One fix that I know Mary is waiting for (we met at the Project Conference) is the ‘loading grid’ issue when updating milestone tasks – Fixed! Details of the CU follow, and also included are more general links regarding application of Service Packs.
The Server CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately.
The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger (~200MB each) but they will greatly simplify MOSS patch deployment.
A reminder on the download links – just replace the KB number where I have xxxxxx and you will go straight there:
You can read about the fixes included in the October CU from the following articles:
Server Rollup Packages:
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): October 27, 2009
Description of the SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): October 27, 2009
Server Individual Product Packages:
Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (Sts-x-none.msp): October 27, 2009
Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp, Pjsrvwfe-x-none.msp): October 27, 2009
The server patches require that WSS and Office Servers 2007 SP1 be installed. For clarity, SP1 is required and SP2 is strongly recommended. Here are the links to the SP1 Server Patches for your convenience:
Description of the 2007 Microsoft Office servers Service Pack 1 and the 2007 Microsoft Office servers Language Pack Service Pack 1
How to deploy the 2007 Microsoft Office servers Service Pack 1 and Office Server Language Pack 2007 Service Pack 1
and here are the links for SP2
Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2
Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2)
Client Individual Product Package:
Description of the Office Project 2007 hotfix package (Project-x-none.msp): October 27, 2009 http://support.microsoft.com/kb/975923
In order to install this hotfix, you will need to have Microsoft Project 2007 SP1 installed on the client. The article at the URL below contains information on how install download and install SP1 should you not have it installed already.
Note: We strongly recommend that you install Project 2007 SP2 from the information earlier in the article.
Description of Project 2007 Service Pack 1 and of Project Language Pack 2007 Service Pack 1
With the 2010 release Project Server now requires SharePoint Server 2010 Enterprise (what we might previously thought of as MOSS) rather than just SharePoint Foundation (previously WSS). This gives us access to all the features such as Excel Services for reporting, but also such things as PerformancePoint Services for Business Intelligence. But as well as these things at the feature level we also benefit from the under the covers changes – such as the great improvements in ULS logging (“unexpected errors” can still happen – but they give you a correlation ID so you can easily find in the ULS logs more information about just how unexpected it was!) The UI for setting verbosity of the ULS logs is also vastly improved and you don’t have to make each change one at a time – you can select whole features or individual sub features and then set the level of logging you require.
Another neat feature is that once you have changed things it is obvious from the UI (Bold) – and this rolls up to the feature level.
And if you do forget and leave logging set at verbose? Well the new health analyzer has a rule for that, and can even alert you!
and automatically fix things too. Sweet!
This is an issue that has been around for a while – the different versions of the SQL components between the SSRS add-in for SharePoint and the Analysis Services requirements for cube building caused a catch-22. Thanks to Bart for finding a resolution to this - install the Management Objects Collection component of the SQL 2005 SP3 CU5 patch (KB 972511).
Some more words to describe the problem and help Bing find this resolution for you:
- When you install Reporting Services 2008 in SharePoint integration mode and you install the rsSharePoint.exe component on the application server, then the OLAP generation fails because of the Management Objects Collection 2005 that is of the wrong version.
- You cannot install the Management Objects Collection 2005 from the December 2008 feature pack (error: a higher version is already installed)
- You cannot un-install the "higher version" because it is integral part of the rsSharePoint.exe package
The issue is described in KB 972694
Hope this helps resolve this long running issue.
I posted a while back about an issue where the Application Server had an alias for the SQL Server, but when the Analysis Services cube build was requested the alias was passed to the Analysis Services server and it didn’t know the SQL Server by this alias (even if it was in fact the same server as SQL and the reporting database was running on!
My colleague in Europe – Nuno – had a similar issue, but with a slight twist that makes a new post worthwhile. ProjectServerOlapCubeGenerator.exe is the executable that builds the cube (it does exactly what it says on the box). It is a 32 bit application and there is not a 64 bit version – so if you are running x64 then this executable will still be running x32. SQL Server 2005 and 2008 Configuration Manager allow you to create aliases for servers – and if you look at the screenshot below you will see that you can create both 32bit and 64bit versions of the alias. If you don’t have the 32bit version set then the 32 bit ProjectServerOlapCubGenerator.exe will not be able to find your SQL Server!
Expect an error something like the following to be in the ULS logs.
CBSGeneralFailure was associated with exception: Microsoft.Office.Project.PI.CBSCommon.CBSProcessException at Microsoft.Office.Project.Server.CBSLayer.ProcessCBSRequestMessage.SpawnOlapDatabaseGenerator(OlapStage olapStage, CubeAdmin cubeAdmin, CBSResource cbsResource, CubeGenerationSettings cubeGenerationSettings, OlapDatabaseDescription olapDatabaseDescription, String publishedDBConnectionString, Guid requestUid) at Microsoft.Office.Project.Server.CBSLayer.ProcessCBSRequestMessage.GenerateOlapDatabase
Thanks Nuno for alerting me to this issue and suggesting the blog posting.