Archive for December, 2006

Recent KB Articles

Friday, December 1st, 2006

Description of the Project 2003 post-Service Pack 2 hotfix package: November 14, 2006

http://support.microsoft.com/kb/927340

 

Description of the Project 2003 post-Service Pack 2 hotfix package: October 19, 2006

http://support.microsoft.com/kb/926327

 

Publishing is blocked when you publish large project plans in a deployment of Project Server 2003 that uses more than one server that is running the Views Notification service

http://support.microsoft.com/kb/924519

 

You cannot log on to Project Web Access, and the following error message occurs after you apply Project Server 2003 Service Pack 2a: "Microsoft JScript runtime error 800a138f"

http://support.microsoft.com/kb/925036

 

Error message when you try to log on to Project Web Access 2003: "Microsoft Jscript runtime error ‘800a138f’ ‘this.oResMgr’ is null or not an object /ProjectServer/Library/LocalizedString.asp, line 44"

http://support.microsoft.com/kb/925037

 

 

Project Server with SQL 2005 KB Articles

 

Project Web Access does not correctly display Project Server 2003 custom field titles when you run Project Server 2003 on a server that is running SQL Server 2005
http://support.microsoft.com/kb/923803

 

Error message when you try to build an OLAP cube in a deployment of Project Server 2003 that uses SQL Server 2005 Analysis Services: "Could not connect to the OLAP server specified"

http://support.microsoft.com/kb/921116/

 

Error messages when you run the Setup program for Project Server 2003: "Error 25624. Failed to execute SQL String" and "Installation ended prematurely

http://support.microsoft.com/kb/917401/

 

 

ProjectServer Reporting123 using MSAccess

Friday, December 1st, 2006

In Project Server often you find a situation where Portfolio Analyzer becomes a resource hog. On top of that cube issues sometimes make it worse. The situation happens usually if you have large number of projects, assignments & resources in your system.

 

Without getting nice & quick reports, the significance of an EPM system could reduce significantly. Though using Portfolio Analyzer, you can create good reports, but sometimes those are not sufficient. In one of my previous article I mentioned using MS Excel to create reports. You can also use MS Access with Project Server to create some excellent reports. You can use the Link Tables features in MS Access to link to Project Server tables. Then using SQL queries coupled with forms & reports within Access, you could create excellent reports in Access.

 

I’ve found an article Microsoft Project Reports on the topic. It is in fact about using MS Access with MS Project rather than MS Project Server database, even then its worth trying.