Anith Gopal

I posted a short while ago about this topic , but wanted to make clear how you can continue working with time phased tracking for normal projects if you have got used to it since the IU.  Brief re-introduction to the problem for new readers – we introduced a time-phased grid for time entry with the Infrastructure Update, but this opened a back door for time phased entry where the project manager was trying to enforce a different tracking method.  SP2 closed this back door.  So if you have been enjoying this loophole between IU and SP2 then you can continue working in this way with your projects (I’ll come to activity plans and proposals later) by the correct application of settings in PWA, Server Settings, Task Settings and Display – and also Project Professional, Tools, Options, Collaborate.  First the PWA settings. If you only want to have time phased task entry for all projects then you should also check the “Force” option.  If you want to have time phased for some projects then you can select the default method here as required, and not set the “force” option – and then in Project Professional you can set the option on a project by project basis, on the Collaborate tab under Tools, Options.

The full error is Cannot insert duplicate key row in object ‘dbo.Objects’ with unique index ‘IX_Objects_ClassId_ParentId_Name’, and this occurs when trying to provision a new PWA site in a farm.  Some background first, and then the workaround.  In the February CU we added a fix for the “waiting for resources” problems customers had run into when trying to provision new PWA sites.  This was caused by a missing timer job.  The fix checked for the timer job, and if it wasn’t found it was created – which for most of our customers was a perfect fix. However, for customers running multiple language versions (MUIs), or even just non US English versions it could fail to detect the timer job and think it was missing and try to re-create it – which led to the error! My colleague Aik had been working on this problem and had a couple of workarounds we’d shared with customers and these turned up back in my blog comments a couple of days ago (Thanks Jose!) – so I thought the time was right for a full posting.  So here are the workarounds – with option #1 being the favored one as it has the least impact on the users of the server: Option #1 – Delete sync jobs before provisioning site To delete a timer definition job, find the Job ID by going to the Sharepoint Central Administration site | Operations | Timer Job Definitions Look for the Project Server sync jobs and right click on the links and select Copy Link – the default names for the jobs (in English) will be something like Project Server Synchronizing job for ‘SharedServices1’. Paste the link into Notepad and the link will look something like this: :/_admin/JobEdit.aspx?JobId=57b935d4%2Db43f%2D4dc4%2Dbd9c%2Dc74bb000b9c6">http://<servername>:<Central Admin Port>/_admin/JobEdit.aspx?JobId=57b935d4%2Db43f%2D4dc4%2Dbd9c%2Dc74bb000b9c6 Copy out just the JobId section and replace the text "%2D" with a dash e.g – Once you are done your GUID should look like the following based on the example above: 57b935d4-b43f-4dc4-bd9c-c74bb000b9c6 Run the following command with the jobID

By the time you get to Phoenix… there will be some excellent Project Server 2007 and 2010 content for you.  New information on the site at http://www.msprojectconference.com/ including an extension to the Early Bird rate!  This will be the only Microsoft Project Conference anywhere in the world this year , so don’t miss the opportunity to “Learn, Connect and Grow” at Project Conference 2009 in Phoenix, AZ from September 14th-17th, 2009. Let’s get some action going on Facebook too!   Session information is being posted (more to come in the next month), so come see these and many other: Connecting the Worlds of Project Portfolio Management & Application Development Introducing Microsoft’s Innovation Process Management (IPM) Solution Microsoft Enterprise Project Management 2010 Migration Deep Dive Project Desktop 2010 Overview Project Server 2010 – Demand Management Application Lifecycle Management with Project Server 2010 And how about the Microsoft Project Conference 2009 Awards Program The Microsoft Project Conference 2009 awards program recognizes customers and partners who have delivered innovative solutions built on Microsoft Enterprise Project Management 2007 technologies.

News from TechEd 2009 this morning on the requirements for the next release of SharePoint – which will be called SharePoint Server 2010 .  As Project Server 2010 will be built on the same platform then expect similar requirements.  In brief these are: SharePoint Server 2010 will be 64-bit only – this was announced during the SP2 webcasts for Project Server, so isn’t totally new news.