Brian Smith's Microsoft Office Project Support Blog

Is your Virtualized Environment Supported? Virtualization Support Policy Wizard Now Publicly Available

If you are running Project Server 2007 in a virtualized environment, how do you know if it is supported or not?  As you may be aware we announced support through the Server Virtualization Validation Program, and now there is a Wizard to help you get a quick answer. 

Just choose your product:

Select your environment (Hyper-V and the non-Microsoft ones are listed – Cisco, Novell, VMWare and Citrix), Guest OS and architecture:

and it gives you a support statement and some useful links!

Project 2007: Mixed up views after updating the Enterprise Global after SP2

I know quite a few customers have run into this issue, and we have a fix in the pipeline which should see the light of day in the August CU, but to help just in case others come across this we thought it worth getting this information out there (Thanks Rob).  First some details, and then the suggested workaround.

The problem and fix is for Project Professional 2007, but only in an Enterprise environment with connectivity to Project Server 2007 – and the views I am referencing are the views within the client application.  When you open the Enterprise Global from Tools, Enterprise Options, Open Enterprise Global and then go to edit a view (View, More Views) you will find that the view it brings up for editing is not the one you thought you should see, but a random view from the list.

For now our suggested workaround is that those few administrative users who need the ability to open the enterprise global should hold off installing SP2, but instead install SP2 with the August CU when it becomes available.  If anything changes in our plans to get this fix out then I will update this blog.

If you have already upgraded to SP2 then just for those few admins who need to open the EGT you could return to pre-SP2.  First make sure that for the user who needs to be “downgraded” that their projects are checked in, then uninstall Project Professional, then remove your cache files from <drive>:\Documents and Settings\<user>\Application Data\Microsoft\MS Project\Cache (or for Vista and Windows 7 users <drive>:\Users\<user>\AppData\Roaming\Microsoft\MS Project\Cache)  and then re-install to the level you were at prior to SP2 (probably either SP1, or preferably Feb CU).

The reason for checking in your projects first is that deleting from the Cache will lose any local changes that have not been saved.  If you prefer not to go dabbling and deleting in the OS then another option would be to create a new connection account that would then give you a brand new cache.  The account I am referring to is the account you set up in Office Project Professional 2007 on the Microsoft Office Project Server Accounts page. You can access this page by clicking the Tools menu and then clicking Enterprise Options.

More details on the local cache can be found here - Understanding the Local Project Cache feature.

Sorry for any inconvenience this issue has caused you, but hopefully most users of Project Professional will not be affected as they will not normally have access to even open the Enterprise Global.

Project Server 2007: Office Server Service Pack 2 (SP2) Update – KB 971620

Following this post: Project Server 2007: License type set to trial after loading Office Server Service Pack 2 (SP2), please find an important update from the SharePoint team:

The public update to fix this issue is available for customers to download.  If you have any questions please send them here.

Post URL is here: http://blogs.msdn.com/sharepoint/archive/2009/06/25/service-pack-2-update.aspx

Service Pack 2 Update.

The public update for the Service Pack 2 expiration date issue is now available for download. 

The update can be applied before or after Service Pack 2 installation.  If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.

The update is applicable to all of the products that this issue affected (see the list in the KB linked below).

Installation instructions and download links for x86 and x64 are available in this KB: http://support.microsoft.com/kb/971620

The direct download link for x86 is: http://download.microsoft.com/download/2/F/5/2F51AB71-1325-49D2-9CB9-18DEC4780E99/office2007-kb971620-fullfile-x86-glb.exe

And for x64: http://download.microsoft.com/download/5/B/B/5BBD34A9-C528-42B0-8A5F-9A8997B25C32/office2007-kb971620-fullfile-x64-glb.exe

We will be updating the existing Service Pack 2 download package with a new package that includes this fix within the next 4-6 weeks.

Microsoft Office Project: New Partner Solutions Directory

For those who haven’t found Doug McCutcheon’s blog yet here is some breaking news on new ways for our partners in the EPM community to post and market their solutions. Also of great interest to our customers I am sure – on where they can go looking for solutions!  News from Doug is:

Office System Solutions Directory Migration to Partner Solution Profiler

• Increase Your Visibility to Customers with Partner Solution Profiler
• Drive awareness of your business solutions.

Customers find partner solutions on the following Microsoft sites:

• Microsoft Communications Sector Directory
• Microsoft Dynamics website
• Microsoft People-Ready campaign
• Solution Finder website
• Windows Marketplace
• Public Sector Partner Solution MarketPlace
• PinPoint

This also applies to all partners who currently use EPMCONNECT.

The Office System Solutions Directory (OSSD) will be retired on July 1, 2009. The last day for updating profiles in OSSD is June 26, 2009. After OSSD is retired, to simplify and streamline the solution profiling experience, the Microsoft Partner Program will require that all solution profiles be created and managed in Partner Solution Profiler.

If you have questions about the retirement of OSSD, download the OSSD Transition FAQ.

Increase your visibility by including your solutions on customer-facing sites and directories worldwide. How? By creating or updating your profile in the Partner Solution Profiler.

As an Information Worker Solutions or Unified Communications Solutions partner, you gain access to a variety of directories, when you create a solution profile in Partner Solution Profiler by following these steps:

1. For general profile information, download the Partner Solution Profiler Completion Guide about creating a successful, effective solution profile.
2. On Tab 2, Solution Overview, in the Products section, select the Office products that your solution uses. Click the Solution Built on Office/MOSS system check box and complete the Office system specific fields.
3. On Tab 6, Preview and Publish, click Publish.

If You Have an Existing Profile in Partner Solution Profiler

If you do not see your profile in the Partner Solution Profiler, go to the Partner Membership Center to review your consent and organizational profile. You must provide your consent for your profile to appear in Microsoft partner directories.

If you have other directory-related questions or issues, contact your Regional Service Center.

Project Server 2007: Why do my removed tasks keep coming back to my Timesheet?

We have had a few reports back since we released SP2 of another behavior change that is catching people out. We have a KB article coming along to describe this behavior change – and I’ll update with the KB when it arrives.

First this is what we did.  In Timesheets we had heard frustration from customer that even though they had set timesheets to auto-populate with tasks from My Tasks, that this only happened when you created the timesheet.  If you added new tasks or were assigned to new tasks once the timesheet was created then you needed to manually add this.  So we listened, and in SP2 changed the behavior so that these new tasks would automatically be there when you opened the timesheet again.  Of course this is only if you have the setting to automatically add new tasks, such as Current Task assignments or current projects selected.

And the problem some customers are reporting?  If you have the setting that introduces this new behavior then even if you remove a task line from your timesheet (Actions, Delete Line) – it comes back next time you open it.

If you are finding the need to delete lines then perhaps the better option for you is No prepopulation, and then just add the ones you need (and keep an eye out for e-mail notifications of new assignments once the timesheet is created).  If neither of these options seems to fit you well then I am sure you will let us know what we are missing.

*** Update - Trackbacks are being slow for now, but do take time to see Brian Kennemer's thoughts on this change at http://blogs.technet.com/projectified/archive/2009/06/25/3258829.aspx.

Project Server 2010 and Project 2010: Final Call to Join the Technical Preview

For the one or two of you who may not have seen Doug or Christophe’s postings I’m just making sure you don’t miss this opportunity.  Final call for access to the Microsoft Project 2010 and Microsoft Project Server 2010 Technical Preview for our Project partners.  This is a great chance to see what’s coming down the line with the next release of Project.

We have issued an invitation asking to show and expression of interest in gaining access to the Technical Preview of Project/Project Server 2010. The invitation was issued to all known EPM Specialized partners; Independent Software Vendors (ISV’s) that build on Project/Project Server; Project Most Valued Professionals (MVP’s) and  Project/Project Server courseware builders (books, Computer Based Training (CBT) DVD’s, instructor lead, on-demand).

There is only one invitation per company and it was sent to the company’s primary contact as registered in the Microsoft Partner Portal or through the Microsoft field providing contact details. Be aware as part of the process the person accepting the invitation must also sign a Non-Disclosure Agreement which applies to the individual and their company.

This is a final call to express and interest in receiving an invitation. If you fell that you company has not received this invitation (and should have based on the criteria given) please email proj2010@microsoft.com with your contact name, company name and email address.

For all other partners who are reading this and wish to participate in the Project/Project Server 2010 please email proj2010@microsoft.com with your name, company, email address, city, country and three sentence explanation why you should participate in the Technical Preview. Your name will be added to a wait list, there is not a guarantee that you will receive an invitation.

It is also worth noting that  as an added value to the Microsoft Project Conference registration at no additional cost to the conference ticket, you and your technical colleagues have been invited to attend the Microsoft Project 2010 Ignite Airlift which will be held on September 13-14, 2009 at the Phoenix Sheraton in Phoenix, Arizona, USA . This is a training workshop for EPM specialized partners and ISV’s who are looking for in-depth technical training on setting up the next EPM version: Project 2010.

See  http://blogs.technet.com/doug_mccutcheon/archive/2009/04/09/project-2010-readiness-be-one-of-the-first-off-the-line.aspx

Project Server 2007: Migration from one domain to another

I’ve posted similar information before, but my colleague Lakshmana Rao (Laksh)  has come up with a great document on the steps required when you want to move Project Server 2007 between domains.  As Laksh points out at the end – please make sure you test this process in a non-production environment first – Hyper-V is perfect for these kind of tests.  On with the document…

How to Move Project Server 2007 from one domain to another:

Considerations in this Article:

1. In this setup, the Project Server 2007 Farm has two servers (One Project Server 2007 SP2 Server box and one SQL Server 2005 SP3 Server box.) For multiple servers set up, please see the Note at the end of this article.

2. Current domain name is APAC and new domain name is NORTHAMERICA.

3. In the current set up, user account used for installing Project Server 2007 and as service account where ever is required is APAC\PsvrSrvcAcct

Prior to changing the Servers to the New Domain:

1. In the new domain, ensure that you have same account IDs and names as that of the domain account IDs and names in Project Server and the service accounts used for Project Server 2007.

Otherwise, after migration; we experience issues with user mappings and unknown issues related to resource assignments/ work/Actual work etc.

2. Take Full Farm back up from SharePoint Central Admin, Operations, Perform a back up. (For more details ,please refer to “Back up and restore the Project Server 2007 farm” at http://technet.microsoft.com/en-us/library/dd207295.aspx

3. Create a user in PWA using the Local Administrator ID or any local User and add to Project Server Administrators group.

For example, if Application Server host name is PSVRPROD, create a user (PSVRPROD\Administrator) in PWA, Server Settings, Manage Users, New User and assign to Administrator group. (After domain migration, we use this account to login to PWA and perform administrative tasks).

4. Stop the WWW service in Project Server.

5. In SQL Server 2005, note the permissions of Service Accounts used on the SharePoint and Project Server databases. (Note the Server roles and User Mappings of the Service Accounts)

Steps to Move the Servers to New Domain:

Moving SQL Server 2005 box:

1. Join the SQL Server to the new domain.

2. Restart the Server.

3. Login to the server with Admin Privileges and add the respective service accounts to the Local Admin group.

In this scenario, I have added NORTHAMERICA\PsvrSrvcAcct. (Before domain change, APAC\PsvrSrvcAcct was present in Admin group.)

4. Open Services.msc and ensure that the MS SQL Server service is running. You may need to change the ‘Log on’ Account name if the service is using a domain account. Specify the correct service account and start the service.

5. Connect to the SQL Server using SQL Server Management Studio.

6. Expand the Security. Click on Logins.

7. Create Service accounts used in Project Server and provide proper permissions to the SharePoint and Project Server databases. (You need to refer to notes in step 5 in section “Prior to changing the Servers to the New Domain:” and give the same permissions ( Server roles and User mappings to the new service accounts)

In this scenario, I have created NORTHAMERICA\PsvrSrvcAcct in SQL Server and provided the same server roles and user mappings as that of APAC\ PsvrSrvcAcct

8. In MSP_RESOURCES table of Published database, change the domain name of the users.

Use the following query

UPDATE MSP_RESOURCES

SET WRES_ACCOUNT = REPLACE(LTRIM(WRES_ACCOUNT), '<Current Domain Name>', '<New Domain Name>');

In this scenario, I used,

UPDATE MSP_RESOURCES

SET WRES_ACCOUNT = REPLACE (LTRIM(WRES_ACCOUNT), 'APAC', 'NORTHAMERICA');

Moving Project Server 2007 box:

1. Join the Project Server to the new domain.

2. Restart the Server.

3. Login as local Administrator and add the respective service accounts to the Local Admin group.

In this scenario, I have added NORTHAMERICA\PsvrSrvcAcct. (Before domain change, APAC\PsvrSrvcAcct was present in Admin group.)

4. Ensure that you are able to connect to SQL Server box. (You can use UDL connection test).

5. Follow the KB article, http://support.microsoft.com/kb/934838 and change the farm service accounts and passwords.

6. Ensure that the Project Server Queue, Event, SharePoint Timer services are using the new domain service account. These should have been set by the actions in step 5 so should not need changing manually (worth noting just in case they didn't do step 5 right and think manually changing will put things right),

7. Open IIS Manager and ensure that all the service accounts are changed to the new domain service accounts. If not change them and restart the IIS.

8. Login to SharePoint Central Admin site.

9. Click on Operations, Service Accounts.

10. Select Web Application pool. For Web Service, select “Windows SharePoint Services Web Application”.

11. For each Web Application pool, verify whether the user name is correct. If not update them and restart IIS.

In this scenario, I have checked whether it is NORTHAMERICA\PsvrSrvcAcct.

(Steps 8 -11 are to make sure that the SharePoint reflects the changes)

12. Log in to PWA using local Administrator ID ( created in step 3 of section “Prior to changing the Servers to the New Domain:” )

13. To initiate “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces”, create a new Category (say “TestSync”) from on Server Settings, Manage Groups add users to this group ( do not add the currently logged in user ) and click save. Again, revert back the changes. Delete the newly created category.

14. Once, “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces” is succeeded, synchronize the Project Workspaces from Server Settings, Project Workspaces.

15. Test the server by publishing a new project and existing project as well.

16. Ask users to access the PWA and Project workspaces and test.

Note: If that farm has multiple Application Servers and WFEs, you have to detach all the servers from the farm, except the server that host Central Admin site. Follow the above steps. The, move other servers to new domain and then connect to the farm one after another.

You can also use PSI functions “SynchronizeMembershipForPwaAppRootSite ()” to update PWA WSS Root Site information and “QueueSynchronizeMembershipForWssSite “to update each WSS Workspace. This requires writing a custom code.

As with any major changes, please test in your own environment to ensure these steps work for you before moving a production system.

 

Thanks again Laksh!

Project Server 2007: Tracking Method Updates since SP2

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.

If you have set the “force” option on PWA then your Collaborate tab will show these options grayed out – and you will not be able to enter time phased work if either the Percent of work complete or Actual work done and work remaining are the Tracking Method options being “forced”.  In the following case we are forcing Hours of work done per period – so time phased entry will be possible.

Also if you have changed from either the Percent of work complete or Actual work done and work remaining tracking methods to allow time phased entry again, you will need to re-publish all active projects to re-enable the time phased entry.  You might also need to make a project change to convince Project Pro that there is data that does need to be published.

I mentioned Activity Plans and Proposals earlier – and there is no way to change settings currently to get back to the time phased entry that many customers have enjoyed between IU and SP2 – but we have heard you and are hoping to revert the change as it applies to these light weight projects.  More news soon on this one.

Thanks to Gary and Eric for the prod to get another posting out to add some clarity to these changes and potential workarounds.

End of week catch-up in ProjectLand – Active Cache Webcast, Gartner Magic Quadrant – and Solid State Disks

I haven’t posted for a little while – it has been really busy here – but fortunately for you the sort of busy that doesn’t need blogging about!  Do you really hate it when people say in their blogs “I’m working on some really cool stuff but I can’t blog about it”?  So do I – so I’m not going to say that…

Just in case any of these recent postings passed you by:

Jan did an excellent webcast on the internal workings of the Active Cache in Project Professional and the way it links to server – with some great demonstrations using Fiddler to see what traffic was going on.  Catch the recording on demand here.  If you didn’t attend you will need to register, then you will be given the option to watch online or download the recording.  I prefer downloading the wmv version as then you can use Windows Media Player and use the option to watch at a faster speed.  Doesn’t always work well if the presenter speaks quickly – but a great time saver as you can watch a one hour presentation in 40 minutes!  Another tip – if you download the high fidelity Live Meeting version the demonstrations are in the res\AppSharing folder as individual wmv files.

Great Gartner Magic Quadrant placement for both Microsoft Dynamics AX and Project Server/Portfolio Server.  Links go to Christophe’s summary.

And finally under the “boys and their toys” section, Christophe did an excellent review of running demonstration Hyper-V images on a Solid State Disk.  I want one!

Almost forgot – I didn’t do a Bing posting when it launched but I do use it and am very impressed. Worth setting as your home page just for the daily photos!  And I’m already seeing more traffic to my site from Bing than I used to get from Live so others are finding it useful too.  Just need to get Bing to put me a bit higher than all those other Brian Smith’s…

Project Server 2007: Expiration date set with SP2 – Product key is not valid?

The KB article in now live at http://support.microsoft.com/kb/971620 and localized versions will be following along.  One thing to mention is that if you have multiple SKU’s installed and you try and re-license you may get a message saying your key is not valid.  This can happen if for instance you try and use a Project Server 2007 key and you have both Microsoft Office SharePoint Server 2007 and Project Server 2007 installed. The key is not really invalid – just not the key the server is expecting. The Q&A in the KB addresses this:

Q:  When I try to follow the steps in the "Resolution" section, I am notified that my product key is not valid.
A: If multiple SKUs are installed, you have to provide the product key for the most inclusive product. Use the product key from the highest-listed product in the following ordered list:

• Microsoft Office SharePoint Server 2007
• Search Server 2008, Search Server 2008 Express, or Microsoft Office SharePoint Server 2007 for Search
• Microsoft Office Project Server 2007

Windows SharePoint Services 3.0 is not affected.

Project Server 2007: PWA Provisioning issue after February CU – Cannot insert duplicate key row

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

1. To delete a timer definition job, find the Job ID by going to the Sharepoint Central Administration site | Operations | Timer Job Definitions
2. 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’.
3. 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
4. Copy out just the JobId section and replace the text "%2D" with a dash e.g -
5. Once you are done your GUID should look like the following based on the example above: 57b935d4-b43f-4dc4-bd9c-c74bb000b9c6
6. Run the following command with the jobID. [stsadm -o deleteconfigurationobject -id <job_Id>]. For example: stsadm -o deleteconfigurationobject -id 57b935d4-b43f-4dc4-bd9c-c74bb000b9c6
7. Make sure to delete both Project Server Synchronization Timer jobs
8. Provision site as you normally would.

Option#2 – Change the regional settings

1. Change the regional settings on the server to MATCH the language of the MUI.
2. Provision site
3. Change the regional settings back to it’s original.

Any issues, or if you need some help working through these steps then please contact support.  My blog reader Jose says we are may be fixing this in the June CU – though I couldn’t possibly comment…

Project Server 2007: Changed behavior with Activity Plans and Timephased time tracking

Sometimes we fix bugs and then find that customers had been relying on the “broken” behavior.  I have covered this topic in some comment postings to the Service Pack 2 article but thought it worth a full posting to help customers understand why they are seeing different behavior.

In the Infrastructure Update we introduced a timephased grid for task time tracking.  Most customers thought this was a great thing – but it did introduce issues in that Project Managers who had specified a project tracking method of % Complete and remaining work could no longer enforce this method – the timephased grid was a back door to “hours per period” statusing.  So we fixed this in SP2 so that Project Managers could once again control how task time was entered.

How does this affect Activity Plans and Proposals?  These server-side, or Light Weight Projects, as they are sometimes called, have certain limitations; only 100 tasks, only one assignment per task and also only one method of task statusing – which is % Complete and remaining work!  This cannot be changed or over-ridden.  In fixing this issue for “real” projects the fix also applied to all projects with this tracking method – and included Activity Plans and Proposals.

Now we are finding that between the IU and SP2 many customers were enjoying the ability to enter timephased data against these server-side projects.  As always, I’d love to hear your comments.

Thanks to Laksh for his suggestion to make a full posting, and Ville for raising my awareness via comments to my blog.

 

Project Server Webcast: Check-in Pending Secrets Revealed!

Well maybe not secrets, but hopefully the webcast tomorrow (5/28/2009) will give more insight to the workings and architecture of the Active Cache.  And if “tomorrow” is in the past the webcast is/was recorded.  Chris Boyd will be presenting with Jan Kalis, and certainly myself and possibly Aik Chen will be along for the Q&A.

WebCast Overview
This webcast will uncover processes and key messaging between Microsoft Office Project Professional 2007 and Microsoft Office Project Server 2007. From first logon, through operations like project open, save and publish, we will describe in detail the ‘cache’ folder structure and registry settings. Network traffic between client and server will also be explained. Finally, we will discuss enhancements made to increase client/server communication scalability and reliability.

When?
Thursday, May 28, 2009 9:30 AM Pacific Time (US & Canada). If you can’t make it, the WebCast is recorded :)

For other sessions you may have missed go to http://www.microsoft.com/events/series/epm.aspx and check the on-demand webcast list.

Project Server 2007: License type set to trial after loading Office Server Service Pack 2 (SP2)

*** Update 2*** A fix for this issue is now released, and a replacement SP2 download will be available 4-6 weeks from now (and now is 6/26/2009).  See http://blogs.msdn.com/brismith/archive/2009/06/26/project-server-2007-office-server-service-pack-2-sp2-update-kb-971620.aspx  

***Update***  The KB for this issue is now live at  http://support.microsoft.com/kb/971620 but currently it does not say that this issue also applies to Microsoft Office Project Server 2007.  This will be corrected shortly, but this certainly does also apply to Project Server 2007 once the Office Servers SP2 is loaded - regardless of the presence of MOSS.  and Applies to section includes Project Server 2007!

This is an emerging issue where we are seeing servers that have been updated with the 2007 Microsoft Office Servers Service Pack 2 (SP2) KB953334 are set to a trial license, with an expiry around the end of October 2009. 

For the official statement on this issue please see the SharePoint blog, which also contains some FAQ answers on this topic.

This appears to apply to servers with Microsoft Office SharePoint Server 2007 and Project Server 2007 both loaded, as well as servers with just Project Server 2007.  Thanks to Shazeb and Kyle for bringing it to our attention!

The fix is simple – just re-enter the license key.  The Project Server 2007 one, or the Office SharePoint Server 2007 one if you have MOSS loaded too.  This is done on the Operations page from SharePoint Central Administration under the Upgrade and Migration section (lower left) called Convert license type.

If you see the word “Trial” in the description area then you have the problem.

On the page itself enter the key, which will be the usual 25 characters in 5 groups of 5.  The following screen shot is of a server after the correct key is entered – so it doesn’t show “trial”.

There will be a KB article coming soon KB 971620, but at the time of writing this is not live – though expected in the next 48hrs. No rush to fix as the expiry is not for a few months – but best to do it before you forget.  No reboot necessary.

 

 

 

By the time you get to Phoenix… Latest Project Conference news!

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. This worldwide event represents a unique opportunity for you to showcase your solutions and to earn recognition from customers, partners and industry influencers. Finalists and winners will be announced on August 15, 2009 and will be recognized at the Microsoft Project Conference 2009 in Phoenix, Arizona, from September 14–17, 2009.

And finally…

It has to be worth the price of admission to see Christophe in Lucchese boots and Stetson hat at the rodeo on Tuesday night!