*** Update *** Now available - http://blogs.msdn.com/brismith/archive/2009/04/28/project-server-2007-service-pack-2-sp2-is-now-available.aspx
Next week, on April 28th, Service Pack 2 (SP2) for Microsoft Office System – including Project and Project Server 2007 will be released, along with SP2 for all the other office applications, including Office SharePoint Server and also WSS. We have a couple of webcasts organized on the morning of the 29th and the evening of the 30th which hopefully allow us to cover most time zones. Join Adrian Jenkins and Christophe Fiessinger as they give an overview of this important release, best practices for deployment and also time for questions and answers. As a reminder the key fixes in this release will be:
Details of the webcasts follow:
Please note we will deliver the same webcast twice to accommodate different time zones, we will also record these webcast and will make them available on EPMConnect:
April 29 – 8-9am Pacific Time April 30 – 5-6pm Pacific Time
Meeting URL https://www.livemeeting.com/cc/lmevents/join?id=OEM042AM&role=attend&pw=ATT5678 https://www.livemeeting.com/cc/lmevents/join?id=OEM042PM&role=attend&pw=ATT6789
Event Info Meeting ID: OEM042AM Entry Code: ATT5678 Meeting ID: OEM042PM Entry Code: ATT6789
Back-up Audio (If you are unable to connect to the audio through the Computer Audio, you can dial in to the audio over a traditional telephony line) US/Canada: (1) (877) 241-9971 International: (1) (503) 295-8000 Pin: 3616 US/Canada: (1) (877) 241-9971 International: (1) (503) 295-8000 Pin: 3616
Requirements for Attending this Event We strongly suggest you test your computer's configuration: https://events.livemeeting.com/LM2007test.htm to ensure you are running the most current version of Microsoft Office Live Meeting.
PingBack from http://skmullen.wordpress.com/2009/04/24/links-for-the-week-of-april-20-2009/
Any idea that Service Pack 2 address this timesheet issue [Message at bottom of timesheet with Red Color at the time] of saving amendment in timesheet i.e. Adding more lines and deleting lines from timesheet.
"While communicating with the Project Server an error occured. Check connectivity with your administrator to determine if further action is necessary"
I don't see a specific fix for this and there could be different root causes. If this is reproducible then best open a support incident and a support engineer will help to establish if this is a known scenario. (For example I know blank task names can cause this - but isn't fixed yet).
Thanks Brian for your prompt reply. This error actually occurs on my production box and effecting few timesheet users at the time of saving amendment (adding new lines (not blank) or changing committed hours in existing timesheet. I have contacted support engineer and he told me a weeks back that this is a known issue of Microsoft Project Server 2007 and will be fixed in service pack 2 which will be shipped by 28-April. Any idea when Microsoft is going to fix this issue. I am open to share log files, if required.
Similarly, I restore my production box data just to confirm it out that this issue will be fixed after installing SP2 but unfortunately test environment doesn't produce this error before installing the SP2 and this situation drives me crazy. I have totally failed to produce the same error on test box and at-last I give up and install SP2.
My experience with SP2 is quite strange, since Microsoft claimed that this is a unique type of SP that gives an opportunity for unistalling the service pack, but unfortunately this is not the case. Similarly, nothing has been noticed by my team regarding improving memory management (2GB data of Project Server 2007, 4 years data i.e. from earliest starting and ending period of projects plus 4 months timesheet data) will take arround 17 minutes time to produce Data Analysis Cube (which is actual 5-7 minutes job before installing SP1 and Infrastructure).
If SP2 was said to fix this and it hasn't then I would suggest calling back in to re-open that support incident for further investigation.
As SP2 for Office Servers will update the database I can't see how this can be uninstallable. Where did you read this?
Finally on the cube build there were some additions to the data actually carried through to the cube in SP1 so not suprised the time increased at that time. There was a SQL bug that could increase the time considerably (to man, many hours) but I don't think you are seeing this issue.
The memory management improvements have been around the queue - it may be you were not seeing these issues, but in our experience the fixes mean no need for regular service restarts. I hope this helps.
I found this un-installation feature on http://blogs.technet.com/office_sustained_engineering/archive/2009/04/16/service-pack-2-for-the-2007-microsoft-office-system-due-to-ship-april-28th.aspx
Can you suggest to install SQL Service Pack 3 for better memory management as I have read some where that Service Pack 3 will resolve this known issue of slow building cube.
Does it supports Project Server 2007.
Thanks Hyder, I see that the uninstall is only for the clients - "The 2007 Microsoft Office Service Pack 2 is the first service pack to support uninstall of client updates through the Microsoft Service Pack Uninstall Tool for the 2007 Microsoft Office Suite as well as via Windows Installer command line. The Service Pack Uninstall Tool will be available as a separate download."
SQL Service pack 3 may help - x64 and/or SQL Server 2008 may help even more.
Thanks Brian, I am ready to upgrade my SQL Server from 2005 to 2008 (64 bit) but I reckoned that complete EPM Suite 2007 (Project Server, Portfolio Server, WSS) can't run on Windows 2008 64 bit. I am not sure about this fact, but I heard from my technical consultant last year that portfolio server 2007 can't run over Windows 2008 x64 release and MS will release another built soon.
Can you kindly confirm it out for me or do have any experience on mentioned technology.
You are correct Hyder that PPS does not currently support x64. This is not going to be addressed within the current release.
I just wanted to update you on specific issue which I am facing when my users are trying to update their timesheet after making amendment in existing timesheets (i.e. deleting line or amending their actual hours) and try to save it and got a red line at the bottom "While communicating with the Project Server an error occurred. Check connectivity with your administrator to determine if further action is necessary", so that all others affected users can at-least try a similar effort to resolve this issue.
I have upgraded my farm with SP2 and April Cumulative Update [WSS + PS2007] along with latest SP3 and CU 3 of SQL 2005. Problem almost resolved and people are freely saving the timesheets after amending it.
However, this makes me bit confused and puzzled because this issue has just occurred after applying Daylight Time Saving (DTS) in mid of timesheet period in late hours (i.e. between April 13-19) and people are still unable to amend this particular period. As a contingency, I have asked affected users (1/4 of project server users) to take snapshoot or copy this particular week data in notepad and re-produce their timesheet by deleting it first.
By doing this so, I am seeing facing the same issue further when we are going to revert back DTS changes in the month of October . I wish and praying Microsoft will address this issue in their next Cumulative update ;)
On the other hand, Cubes still takes much longer time to build (i.e. 1.6 GB data) took 22 minutes and I can’t upgrade my SQL Server 2005 to x64 just because of Portfolio Server ~)
Can you help to improve performance.I have split my farm into two components i.e. App + Web and DB server, but unfortunately performance still not up to the satisficatory level and cubes takes much longer time i.e. 22 minutes to build 1.4 GB data with a CPU utilization of 97-100% at DB server. This farm is not accessible by any one other than my-self. Configuration of server is Dell 1950 Power Edge with 8 GB Ram
This isn't really something I can deal with via blog comments as there could be so many factors involved. I'd certainly suggest any cube build should happen in any "out of hours" time the server has (and 22m doesn't sound too bad). Next steps could be offloading this reporting work away from your transactional system and possibly the reporting database to a separate server.
One of my user complained that the server shows wrong hours in CreatedDate when he has created an issue in PWA. System shows 1 hour difference, however, client and server shows the right date and time. Can you advice any thing to start debugging this mystery.
We have deployed all latest patches (including SP and cummulative updates) of SQL Server, PS2007 and WSS.
Has anyone seen any new issues brought on by SP2 and the April CU. We are getting ready to install and test both.
I have faced three issues in SP2 + April Cumulative Updates and can't figure out the reason so far and I hope we all can solve this mystery.
Issue #1: Base Capacity + Capacity Data missed in reporting database for certain months & certain resources
Issue #2: Which I just noticied after publishing the previous issue on the site is, Project Planned Hours is missed in Timesheet Cube.
Issue #3: Receiver will continously receiving alert/notification from PS2007 on deleted Status Report (by sender).