Well Microsoft have finally come out with the news that they are planning to release the Office. The latest news is that the next version of Microsoft Office Project will be Office 2010 which will be released....wait for it........ in the first half of 2010. Exactly when in the first half is uncertain at this stage, but the good news is that change for the better is on the way.

Prior to final public release there will be the Technical Preview and Beta Release. This is generally offered to select users/testers.

Many organisations would like to package the Microsoft Project Server Active X Components instead of allowing users to directly install the components onto their PC’s

The two files that need to be deployed/installed on the client PC’s are.

1. Pjcintl.cab

On the application server where Project Server 2007 this is typically located under the following path

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\PWA\OBJECTS\1033

2. pjclient.cab

On the application server where Project Server 2007 this is typically located under the following path

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\PWA\OBJECTS

Quote

How to determine which version of a 2007 Office product is installed?

The October Cumulative Update was released on October 28th

For deployment guidance refer to:  Deploy cumulative updates (Project Server 2007)

Knowledge Base Articles and Downloads

Project Interdependency in Project Server 2007 Part 2

In Project Server 2007, you can manage Project Interdependencies using Deliverables as well.

This has been excellently explained in the below article.

http://office.microsoft.com/en-us/project/HA101230571033.aspx

How to determine which version of a 2007 Office product is installed including Project Server?

Method 1: Use the "Add or Remove Programs" item in Control Panel in Windows XP or in Windows Server 2003, or use the "Programs" item in Windows Vista

Windows XP or Windows Server 2003

(Check with Table below)

Windows Vista

To look for installed updates including service packs, follow these steps:

Method 2: Verify the version in the properties of the executable file

Public updates and hotfixes other than service packs do not change the version of the installed product. To verify the version of the executable or other core file for an application, you can view the properties of a file.

Note If a software update does not include an updated version of the program’s executable file, view the documentation that is provided with the update to determine which files are updated. Then, check the versions of the updated files.

By default, the 2007 Office programs are located in the following folder:

 C:\Program Files \Microsoft Office\Office12

By default, the Mso.dll file is located in the following folder:

 C:\Program Files\Common Files\Microsoft Shared\OFFICE12

The original release and service packs of the 2007 Office programs have the following executable file names and version numbers:

What is Playbooks?

Microsoft has released a tool call Playbooks with their Project Server 2007 resource kit to assist users in moving configurations of Project Server from one instance to another.

Gordon plays with Playbooks.

I recently had the experience to run into one of the pitfalls in using this tool. I was attempting to move configurations from my development server to the production server.

Playbooks is a fantastic tool to assist in that process which previously was manual. What I noticed was that while rest of the configurations moved across smoothly, the formulas did not move across correctly.

The formulas failed to calculate and just displayed “Error”. I had validated these formulas prior and was initially surprised that this would happen. I deleted the formulas and re-created them.

This generally used to work for me, but surprisingly enough the formulas seems to break the formula calculation engine on the server. This was in spite a success message displayed once Playbooks completes the move.

There is no recovery once this happened. The only way I was able to get project server to function again was to re-provision Project Web Access and recreate the databases or restore from the back-up taken, prior to running the playbooks tool.

What I found was that if I used Playbooks to copy the rest of the configuration without formulas the configuration move went successfully. Somehow playbooks was not able to move formulas successfully across.

Workaround I used to get around this.

Step 1: Ran playbooks and backed up configuration on source server.

Step 2: Deleted all the formula based fields from the source server.

Step 3: Ran Playbooks and backed up a second time.

Step 4: Restored second playbooks config (without formulas) on the target server.

Step 5: Restored first playbooks conf back on source server.

Step 6: Manually re-created the formulas on the target server.

Conclusion

Playbooks for me is a great tool to reduce the effort in moving configurations from one Project Web Access instance to another. However I feel there are certain disconnects with the tool.

I would use it, but with caution depending on the scenario and situation. Never know what surprise it could spring up on me. Happy playing !!!

Gordon Lewis

Quote 1

Project Server 2007 Data Analysis common issues 

Project Server 2007 Data Analysis errors and common issues faced

   

I have faced a number of scenarios where client machines are not able to process the data analysis views of PWA. Some of the common error messages faced were.

Error Message

Project Server query could not be processed.

Cannot connect to the server 'Project Server'. The server is either not started or too busy.

 

Situation 1: Missing components on the client machine.

Refer to article View OLAP Cube data   Describes methods for your users to access OLAP cube data.

It is important you read this article.

 

Component			Version	State during installation
Microsoft Core XML Services (MSXML)			6.0	All components are available in the downloadable Feature Pack for Microsoft SQL Server 2005.
Microsoft SQL Server 2005 Analysis Services OLE DB provider			9.0
Microsoft Office Web Components 11 (OWC11)			2003	This is if you have office 2003 installed on the client machines. If you have another version of Office, you will need to install the appropriate Office Web Component for that version

 

Situation 2: Cross liking of MSOLAP dll

 

If you have a situation where by the issue is client machine specific after ensuring that the above components are installed and available, I would suspect a cross interference of msolap dll.

I have seen this happen in the past and adopted the following to get around the issue.

The registration of MSOLAP90.dll may not have been completed as being default. A prior version of MSOLAP dll may be registered as the default. 

Browse to location of MSOLAP dll using the command prompt and run the following. (you can easily find the location of MSOLAP.dll by runnin a search for MSOLAP*.dll on the client machine)

Sometimes instances of 8.0 and 9.0 get cross linked. Run the below from command prompt 

• Regsvr32 –u msolap80.dll
• Regsvr32 –u msolap.dll
• Regsvr32 –u msolap90.dll
• Regsvr32 msolap90.dll

Now try and access the Data analysis Views.

Quote

Talking about MS Project 2007: My Tasks Web Part Error

 

MS Project Server 2007: My Tasks Web Part Error

1. One or more of your resource report that his "My Tasks" is showing a SharePoint error message

2. If you know how to query your database (Published DB of your server) and get unfortunately one row at least, this would indicate a corrupted

Task assignment.

SELECT MSP_PROJECTS.PROJ_NAME, MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME, MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID, MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID =
MSP_ASSIGNMENTS_SAVED.TASK_UID)))

To resolve this issue try the following

· Open Gantt View, Insert "Publish" column, and select No for the task that you got from the above query

· Publish your project.

· Again Gantt View, For the  "Publish" column, and select "Yes" for the task that you got from the above query

· Publish you project

Optionally

· Create a new task with remaining work as work from Task corrupted.

· Re-assign the resources to this task.

· Release the resources from the previous task whereby Remaining Work = 0 and task maked 100% complete.

· Publish the Task/Project

How can Tasks get corrupted?

A common trend that I have seen is for Tasks that are tracked following the Actual work done and work remaining. (Where Resources report the actual work done and the work remaining to be done on each task) whereby, actuals have been entered against this task. If the project manager then switches and tracks progress on task with % complete this could corrupt task assignments giving rise to the error.

Quote

Project Interdependency Project Server 2007 Part 1

 

Project Interdependency in Project Server 2007 Part 1 (Linking Tasks across Projects)

What is interdependency of Projects?

During the executing of project work, the entire execution may not be solely independent of external influences of external projects.

During the planning phase, it is important that a matrix of interdependencies of projects and program of work is established.

Keeping across externally dependent tasks or activities is equally important to managing tasks on the critical plan on your project.

How to set Project interdependency between projects in Project Server?

Open the Project for which the interdependency is to be set in MS Project Professional (in edit mode)

In the Predecessors column type in <>\Project Name\Task ID where Project Name is the name of the Project to which the predecessor dependency is to be set.

The Project ID is the task ID of the task for which the predecessor relationship is to be set.

Once this has been set you will notice a ghost dependent task appear from the dependent project in your project plan.

Save and Publish the Project Plan.

Note: To set this inter-dependency it is important to open the dependent project in at least ‘read only’ mode. For this inter-dependency to be reflected in both Project Plans, both projects need to be opened in Edit Mode and changes saved accordingly.

What happens if the dependent task on the external project changes?

When the dependent task on the external project changes, the next time the project is opened, changes to the external predecessor task will be shown.

The user will have the option to accept the changed on dependency to the external project or if needed Delete the Link.

On Accepting and closing the dialogue box the accepted changes are reflected in the project plan.

Project Interdependency in Project Server 2007 Part 1 (Linking Tasks across Projects)

What is interdependency of Projects?

During the executing of project work, the entire execution may not be solely independent of external influences of external projects.

During the planning phase, it is important that a matrix of interdependencies of projects and program of work is established.

Keeping across externally dependent tasks or activities is equally important to managing tasks on the critical plan on your project.

How to set Project interdependency between projects in Project Server?

Open the Project for which the interdependency is to be set in MS Project Professional (in edit mode)

In the Predecessors column type in <>\Project Name\Task ID where Project Name is the name of the Project to which the predecessor dependency is to be set.

The Project ID is the task ID of the task for which the predecessor relationship is to be set.

Once this has been set you will notice a ghost dependent task appear from the dependent project in your project plan.

Save and Publish the Project Plan.

Note: To set this inter-dependency it is important to open the dependent project in at least ‘read only’ mode. For this inter-dependency to be reflected in both Project Plans, both projects need to be opened in Edit Mode and changes saved accordingly.

What happens if the dependent task on the external project changes?

When the dependent task on the external project changes, the next time the project is opened, changes to the external predecessor task will be shown.

The user will have the option to accept the changed on dependency to the external project or if needed Delete the Link.

On Accepting and closing the dialogue box the accepted changes are reflected in the project plan.

MS Project Server 2007: My Tasks Web Part Error

1. One or more of your resource report that his "My Tasks" is showing a SharePoint error message

2. If you know how to query your database (Published DB of your server) and get unfortunately one row at least, this would indicate a corrupted

Task assignment.

SELECT MSP_PROJECTS.PROJ_NAME, MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME, MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID, MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID =
MSP_ASSIGNMENTS_SAVED.TASK_UID)))

To resolve this issue try the following

· Open Gantt View, Insert "Publish" column, and select No for the task that you got from the above query

· Publish your project.

· Again Gantt View, For the  "Publish" column, and select "Yes" for the task that you got from the above query

· Publish you project

Optionally

· Create a new task with remaining work as work from Task corrupted.

· Re-assign the resources to this task.

· Release the resources from the previous task whereby Remaining Work = 0 and task maked 100% complete.

· Publish the Task/Project

How can Tasks get corrupted?

A common trend that I have seen is for Tasks that are tracked following the Actual work done and work remaining. (Where Resources report the actual work done and the work remaining to be done on each task) whereby, actuals have been entered against this task. If the project manager then switches and tracks progress on task with % complete this could corrupt task assignments giving rise to the error.

Project Server 2007 Data Analysis errors and common issues faced

   

I have faced a number of scenarios where client machines are not able to process the data analysis views of PWA. Some of the common error messages faced were.

Error Message

Project Server query could not be processed.

Cannot connect to the server 'Project Server'. The server is either not started or too busy.

 

Situation 1: Missing components on the client machine.

Refer to article View OLAP Cube data   Describes methods for your users to access OLAP cube data.

It is important you read this article.

 

Component			Version	State during installation
Microsoft Core XML Services (MSXML)			6.0	All components are available in the downloadable Feature Pack for Microsoft SQL Server 2005.
Microsoft SQL Server 2005 Analysis Services OLE DB provider			9.0
Microsoft Office Web Components 11 (OWC11)			2003	This is if you have office 2003 installed on the client machines. If you have another version of Office, you will need to install the appropriate Office Web Component for that version

 

Situation 2: Cross liking of MSOLAP dll

 

If you have a situation where by the issue is client machine specific after ensuring that the above components are installed and available, I would suspect a cross interference of msolap dll.

I have seen this happen in the past and adopted the following to get around the issue.

The registration of MSOLAP90.dll may not have been completed as being default. A prior version of MSOLAP dll may be registered as the default. 

Browse to location of MSOLAP dll using the command prompt and run the following. (you can easily find the location of MSOLAP.dll by runnin a search for MSOLAP*.dll on the client machine)

Sometimes instances of 8.0 and 9.0 get cross linked. Run the below from command prompt 

• Regsvr32 –u msolap80.dll
• Regsvr32 –u msolap.dll
• Regsvr32 –u msolap90.dll
• Regsvr32 msolap90.dll

Now try and access the Data analysis Views.

One might encounter errors of synchronisation of resources with Active Directory.

Error Message

Project User: AD\glewis

Correlation Id: 8d0de900-0500-4a45-80a4-3ec45d2107db

PWA Site URL: https://projectserver/PWA

SSP Name: SharedServices1 SSP Administration

PSError: Success (0)

A resource could not be updated during Project Server Active Directory Synchronization because a duplicate windows account name conflict occured that could not be resolved. Resource GUID: 38c2d710-e92c-4181-91e8-b1e8f79acb5a. Resource Name Paris Hilton Windows Account:

Things to check:

1. Resource is checked out

Sometimes when the resource is checked out you could get errors. It is advisable to update details of resource and check the resource back in.

Sometimes the resource is checked out by the AD sync service accoutn and could be checked out in the DB but not appear as checked out in PWA.

Re-run the synchronisation

2. Resource details manually entered and not aligned to conventions in Active Directory

What I found was that somehow the resource to which Active Directory was synchronising to was already defined manually and names were not correctly defined as they were in Active Directory.

Delete the resource if not assigned to tasks or project and re-run synchronisation or edit the resource to as defined in the Active Directory