If this is the first you have heard of the Beta (Where have you been? Can I come next time?) then take a look at http://blogs.msdn.com/project/archive/2009/11/18/now-available-project-2010-beta.aspx for the links to Project and http://blogs.msdn.com/project_programmability/archive/2009/11/19/project-2010-sdk.aspx for great links to the new developer stuff (Great work Jim!).
A couple of early issues or regular questions are:
No, 2010 can only talk to 2010 Server. You can however still use 2007 against an upgraded (2007 to 2010) Project Server instance as long as it is still set for Backwards Compatibility Mode. Once you switch to native mode you cannot switch back1 Another option available to you is installing 2007 and 2010 side by side (but not running both at the same time). If you have any connectivity issues then usually running a repair on the 2007 Project Professional will resolve this. Be aware that opening Projects from PWA will likely give you issues, as the wrong Pro may try and start.
This one relates to a bug which we thought we had addressed in the documentation, but it came back to bite us. The docs are being updated as I write, but in case you already ran in to this you can remove your provisioned PWA and the associated databases, carry out these steps:
and then provisioning PWA should work just fine. This issue will also give errors in various places – the event log will show a compatibility issue with the published database, the queue will not start, and then a couple of new pages in Central Admin will also get alarm bells ringing:
The key things here are “Upgrade Required” against the server, and “Database is too old and upgrade is required” against each of the ProjectServer databases.
Cheers, that solved some early pain!
psconfig command went only through 3 of the four steps. In the third step it stops at "task 10% completed". (windows R2 and sql server 2008). Could you point me in the direction of a solution. Kind regards, Pieter
Did you delete your PWA sites Pieter? I've not seen a failure at this point, but know that existing PWA sites will cause a problem. The logs may also indicate why the update stopped.
I'm getting this error when running the command:
Cannot open SPTimerV4 service on computer '.'.
Am I missing something?
I have issues whith the "Proposal Reviewers" Security Group missing from my install. This is a major problem b/c all proposals are being automatically approved due to "no one in the proposal reviewers security group" - according to the workflow status messages. Is this a bug or did I just miss something during setup?
I am facing a very unique issue with project installation. My installation works fine till provisioing of PWA site. I can browse site do what ever I want with it.
However as soon as server is rebooted, for some odd reason everything stops working. Even all the services of Win2k8 stops working.
Has any one experienced any issue with rebooting of server? any solution/advice?
Please tell me, its posible install Project Server 2007 with SharePoint Server 2010.
No, this is not possible. You need Project Server 2010 if you want to run with SharePoint Server 2010.
I haven;t seen this issue - you might be best opening asupport incident if you are still facing it.
The proposal reviewers group is actually either the Portfolio Managers group or the Project Managers group (or possibly the Resource Managers?). We have been changing this around in different Beta releases. If you add yoursefl to each then you should see approval messages coming through.
I have been slow to respond - so you may well have resolved this now. When do you see this error?
Hello Assaf, try this solution here it works for me as I just had the same issue with the "SPTimerV4 service"