Enterprise fields come from Project Server which is not supported. One way to determine if this is the cause of the issue is to open the project in the MSP Legacy driver. In MSP, go to File->Organizer then click on the Fields tab. For any fields showing either for Tasks or Resources, right click it and select Rename. If it is an enterprise field, you will get a warning informing you the field cannot be renamed starting with 'Enterprise fields cannot be renamed in the Organizer'.
To resolve the issue:
1. Disable any Enterprise fields on workstations that have these fields mapped.
2. Run the below query to temporarily remove the project from the prdocument table. (For On Demand customers, please open a case to have this resolved):
IMPACT OF RUNNING SCRIPT:
- The update will wipe out the views for the project, so when the project is opened from PPM after the update, the project will only open with the default columns. Users will have to recreate their views for the project, unless they have them saved in MSP. (This doesn't apply starting in the 14.2 new driver, as views are no longer saved. Users should always save the views on their MSP and switch to that view after the project opens).
- Any custom field data not mapped to PPM will be deleted from the project. This only impacts data entered in a MSP Field (such as a text field) and that data isn't stored in PPM.
Run the below query:
set prrecordid = ?? where prrecordid=?
and prtablename= 'PRJ_PROJECTS'
1. Replace the ? with the 5 million number of the project. For ?? change the 5 to a 9. This will create a backup of the record in the database.
2. Run the below query to ensure that there is not already a project with the ?? prrecordid:
select * from prdocument where prrecordid = ??
3. To find the 5 million number for the project, you can run the below query (or it can be found in the PPM URL when clicking on the link to the project from the project list)
select id from inv_investments where name='<project name>' and object_type = 'PROJECT'