Anith Gopal

Carl here. ProjHugger is for Microsoft Office Project newbies, enthusiasts, and zealots. I publish new posts every Monday morning, but you can add comments any time.

Projektidel on alati olemas oma kriitiline ahel ning selle juhtimiseks vajame ajapuhvrit.

Maybe it’s because I’ve been swamped this week while the sun’s been shining here in the beautiful Pacific Northwest, but I’ve been doing some thinking about buffer, downtime, and productivity. I don’t think it’s a secret that projects have a tendency to come in late sometimes

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

Dear Project developers! Let me remind you about Larry Duff’s WebCast tomorrow! “During this webcast we will explore a new solution starter for Microsoft Office Project Server 2007, EPM Auditing.

The distributed cache platform code-named "Velocity" has been updated with the third community technology preview (CTP). Microsoft project code named “Velocity” promises to speed up .NET-based Web applications. "Velocity" is a distributed in-memory application cache platform for developing scalable, high-performance applications

Dieses Kalenderjahr ist ein Projekt der Ärztekammer Österreich, die Standesführung zur Verwaltung der Daten niedergelassener Ärzte durch die Kammer, auf Basis neuester Microsoft-Technologien in Produktivbetrieb gegangen. Das Projekt wurde von einem unserer Gold Certified Partner, Anecon Software Design und Beratung abgewickelt und umgesetzt. Nachdem im Rahmen dieses Projektes neueste Technologien (.NET Framework 3.5, Windows Presentation Foundation, Windows Workflow Foundation, SQL Server Service Broker) zum Einsatz kamen und das Projekt auch strategische Bedeutung für Microsoft (eHealth als strategischer Markt) hat, haben wir das Projekt von unserem Team punktuell mit Architektur-Workshops betreut

在 Project Server 2007 的升级或者迁移的过程中，有人会遇到一些棘手的问题。比如当在 SQL 服务器里恢复了四个 Project 服务器数据库和若干个 Sharepoint 内容数据库（Content Database）之后，如果之前 Project Web Access (PWA) 就是 项目工作环境 （Project Workspaces – PWS）所在的 网站集 （Site Collection），比如说 http://oldserver/PWA ，就可能会不清楚应该先恢复 PWA 还是 PWS： 如果先恢复 PWA，那么 Project 服务器会在 Sharepoint 里面重新创建一个新的网站集（ http://newserver/PWA ）给 PWA。那么当通过用 stsadm -o addcontentdb 来恢复 PWS 的时候，这个操作就会失败。因为在当前的 Sharepoint 里面已经有了那个新的 /PWA ，和将要被恢复的内容数据库里的那个旧的 /PWA 冲突了。 如果先恢复 PWS 的话，那么当前的 Sharepoint 里就会有一个旧的 /PWA （而且是失效的），导致之后在尝试恢复 PWA 的时候不能使用同样的路径。当然，我们完全可以给 PWA 想一个新的路径名字，比如 /PWA2 ，来解决这个问题。只不过这样的方法不是太完美罢了。 那怎么才能完美地让升级、迁移 Project 服务器呢？这就需要在当初规划 Project Server 的时候巧妙一点了。最好的建议就是， 在第一次安装好 Project 服务器之后，去 中心管理 （Center Administration）创建一个新的内容数据库。 然后把原本 PWA 所在的内容数据库的允许创建网站的数目设置成远小于新的内容数据库所允许的网站数目，比如新的内容数据库允许创建 1000 个，那么原本的内容数据库就应该设置为 10 个。这样就可以保证新的网站集或者网站可以自动在新的内容数据库里创建。 然后创建一个新的网站集。这个网站集应该是会自动在新的内容数据库中创建。 接下来登录到 PWA 去 服务器设置 里的 项目工作环境设置 ，把 网站URL 替换成步骤 3 里面所创建的网站集的路径。这样在之后的运营中，新的 PWS 就会在 /PWA 之外的地方创建。 做好了这样的规划，等之后的某一天需要升级或者迁移的时候，只要备份并恢复四个 Project 服务器的数据库和有 PWS 的内容数据库，就不会出现上面的麻烦了。这是为什么呢？因为在升级或者迁移的时候，所有的 PWS 都没有在 PWA 所在的网站集下，所以无论是先恢复 PWA 还是 PWS，都不会有冲突。   参考： 创建（提供）项目工作环境网站： http://office.microsoft.com/zh-cn/projectserver/HA100996542052.aspx

SQL Compact Replication initial subscription may take significant time on devices.

I tripped across the daedalus project  this morning while I was looking for player statistics for World of Warcraft.

Conheça o caso Finsolutia , num projecto in-house criado em apenas dois meses, suportado pela plataforma colaborativa Microsoft Visual Studio Team System 2008 Team Foundation Server, utilizando a metodologia SCRUM. Obrigada

[For a moment I thought of the “Why so serious” scene of  “The dark knight”…