prim22467:Event Code Error: ‘CVRJC-3802-1′ when importing an XER

Event Code Error: ‘CVRJC-3802-1: TCCustomVirtualRow.getJoinedColItems: UDFVALUE row has blank fk_id’ when importing an XER

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.)

** Other scenarios that cause orphaned records may still exist. **

To download the latest Service Pack, see:

Solution ID: prim29265 揥hat are the latest Service Packs for Primavera version 5.0??/A>

Run database queries/scripts on the source database (the database where the XER was exported from).  See steps below.

PROJECT MANAGEMENT FIX:

Run the appropriate script below on the database that the XER was exported from
     – For Microsoft SQL Server, run the script as PRIVUSER
     – For Oracle , run the script as ADMUSER
     - For MSDE Primavera 5.0 Standalone installation, save the appropriate script to the root of the C:\ drive and run the following from a DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d pmdb$primavera -i c:\delete_orphaned_UDFVALUE_##.sql

CONTRACTOR FIX:

      - For Contractor 5.0, save the delete_orphaned_UDFVALUE_50 script to the root of the C:\ drive and run this from the DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d PCONDB -i c:\delete_orphaned_UDFVALUE_50.sql

Note:  RUN THIS SCRIPT ON A BACKUP OF THE DATABASE FIRST!

For Project Management 4.1 databases:  delete_orphaned_UDFVALUE_41.sql

For Project Management 5.0 databases: delete_orphaned_UDFVALUE_50.sql

 If the script seems to hang at the section where the script attempts to delete UDF data which has no corresponding entry in the TASK table, please replace it for:

Workaround 2:

If the source database is not accessible, the XER file can be fixed.  Please see:

 PRIM16871: Receiving Event Code:  CVRJC-3802-1 while importing a project with orphaned rows in UDFVALUE table

If a 5.0 SP2 or higher implementation is available (both client application and database patched) the project may be imported and then re-exported to XER format to remove the Orphaned Records causing this problem.  It may then be imported into a pre SP2 database.