"Event Code Error: CVRJC-3802-1 when importing an XER"
Solution ID: prim22467
Cause - This is caused by orphaned records in the database being extracted into the XER file during export, then the error is received when importing an XER file that contains these orphaned records. Orphaned records can happen for a variety of reasons.
Note:
- One known cause is if multiple users are in a project and user 1 runs a global change or fill down for a user defined field and user 2 is deleting an activity at the same time. The activity is successfully deleted but leaves an orphaned UDF value. (Note: Primavera recommends running these type of changes in "Exclusive mode". )
- This particular cause of orphaned records has been fixed in Project Management 5.0 SP1 and 4.1 SP4. Applying these releases will not fix pre-existing orphaned records in databases or XER files but will prevent new orphaned records from being created by this scenario. Therefore, the error will continue to happen if the XER being imported contains orphaned UDFs. (see the delete_orphaned_UDFVALUE scripts below for database cleanup of orphaned records.)
Member for
22 years 6 monthsRE: Error message
Thanks Andrew. I have uploaded the SP4 and it works now.
Regards.
Member for
18 years 8 monthsRE: Error message
From the POINT site,
"Event Code Error: CVRJC-3802-1 when importing an XER"
Solution ID: prim22467
Cause - This is caused by orphaned records in the database being extracted into the XER file during export, then the error is received when importing an XER file that contains these orphaned records. Orphaned records can happen for a variety of reasons.
Note:
- One known cause is if multiple users are in a project and user 1 runs a global change or fill down for a user defined field and user 2 is deleting an activity at the same time. The activity is successfully deleted but leaves an orphaned UDF value. (Note: Primavera recommends running these type of changes in "Exclusive mode". )
- This particular cause of orphaned records has been fixed in Project Management 5.0 SP1 and 4.1 SP4. Applying these releases will not fix pre-existing orphaned records in databases or XER files but will prevent new orphaned records from being created by this scenario. Therefore, the error will continue to happen if the XER being imported contains orphaned UDFs. (see the delete_orphaned_UDFVALUE scripts below for database cleanup of orphaned records.)