Project Server 2003 migration to #ProjectServer 2007 error #PS2007 #PS2010 #MSProject

February 13, 2012 at 6:23 pm | Posted in Issue | Comments Off on Project Server 2003 migration to #ProjectServer 2007 error #PS2007 #PS2010 #MSProject
Tags: , , , , , ,

I recently worked on a project to migrate from Project Server 2003 to Project Server 2010. While running the P12 migration tool the error below was thrown in the command prompt window:

PWA Migration: Setup views to Project Server 2003 – Failed

The Log file details for the error were as follows:

Err1 = 37000 Err2 = [Microsoft][ODBC SQL Server Drive][SQL Server] could not find server ‘server name’ in sys.servers. Verify that the correct server name was specified. If necessary, execute the sp_addlinkedserver to add the server.

Migration finished with error return code 80004005.

Running the –verify switch completed successfully but running the actual migration failed. 

This is due to using an FQDN or DNS Alias name for the SQL Server in the P12 configuration file rather than the actual short name for the SQL Server. After updating the configuration file “Project2007SQLServer” value the migration ran successfully.  

#ProjectServer 2003 migration to Project Server 2007 issue #PS2003 #PS2007 #MSProject

September 7, 2011 at 9:50 pm | Posted in Fixes, Issue | Comments Off on #ProjectServer 2003 migration to Project Server 2007 issue #PS2003 #PS2007 #MSProject
Tags: , , ,

I came across an issue today running the P12 migration tool and thought I would share the error and simple fix. The command prompt didn’t update for around an hour, the last entry mentioned about custom field name conflicts. Looking in the log file it was just repeating the following messages:

Received serializer callback: 4
Waiting for Job to be Processed. percentage complete: 0
Time to execute P12ProjectUpgrader::SerializerCallBack(): 0 ms

After looking in Project Server 2007 PWA it appeared that there was an issue with the queue service as the jobs were waiting to be processed. After a restart of the Project Server Queue service, the jobs processed though the queue and the migration then progressed and completed successfully.

Report on Project Server baseline save dates? #ProjectServer #PS2003 #PS2007 #PS2010 #MSProject #EPM

August 20, 2011 at 11:16 pm | Posted in Customisation, Functionality | 2 Comments
Tags: , , , , , ,

Quite often clients want to report on the dates when the baselines were saved. This information is not available out of the box in the databases using T-SQL. This post explains how to get this data into the database so that is accessible using T-SQL in the Reporting database.

Firstly we need to create 11 Project level enterprise custom text fields to store the baseline save dates. For the purpose of this post not all custom fields have been created, the custom fields in this example are Baseline0saveddate, Baseline1savedate and Baseline2savedate. Next add a VBA macro into the Enterprise Global that copies the baseline save dates to the enterprise custom fields created above. The following macro is just an example cut down version to copy the baseline save dates to the custom fields. This cut down version also only includes the first 3 baseline save dates.

Private Sub Project_BeforeSave(ByVal pj As Project)
ActiveProject.ProjectSummaryTask.Baseline0saveddate = ActiveProject.BaselineSavedDate(pjBaseline)
ActiveProject.ProjectSummaryTask.Baseline1saveddate = ActiveProject.BaselineSavedDate(pjBaseline1)
ActiveProject.ProjectSummaryTask.Baseline2saveddate = ActiveProject.BaselineSavedDate(pjBaseline2)
End Sub

The macro above will work for Project 2003, 2007 and 2010.

If a baseline value is not set NA will be set in the associated custom field. Once the macro has been added to the enterprise global, save the changes then close Project Professional. Re-launch Project Professional and open a project that has baselines set. Insert the new Project level custom fields into the view, click Save and you will see either the baseline save date appear in the associated custom field or NA if a baseline has not been set for a particular baseline. Once this project is published this information will be available to report on in the Reporting database. For example, the following T-SQL will give you the baseline save dates based on this post example:

use            PWA_Reporting
select        ProjectName
        ,    Baseline0saveddate
        ,    Baseline1saveddate
        ,    Baseline2saveddate
from        dbo.MSP_EpmProject_UserView

The T-SQL above will work for Project Server 2007 and Project Server 2010.

As mentioned above the VBA code is just as an example and would need to be improved for a production environment.

Create a free website or blog at
Entries and comments feeds.