Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Error message

2 replies [Last post]
Tue, 2007-10-23 05:07
Mirza Imam Baig
User offline. Last seen 6 years 39 weeks ago. Offline
Joined: 29 Apr 2003
Posts: 39
Groups: None
Hello Planners,

I am getting an error message (Event Code: CVRJC-3802-1) when I tried to import the P5 backup file. Can any one help me how to resolev it. Thanks.

Regards
Top

Replies

Wed, 2007-10-31 00:51
#1
Mirza Imam Baig
User offline. Last seen 6 years 39 weeks ago. Offline
Joined: 29 Apr 2003
Posts: 39
Groups: None
Thanks Andrew. I have uploaded the SP4 and it works now.

Regards.
Top
Tue, 2007-10-23 05:25
#2
Andrew Dick
User offline. Last seen 9 years 5 weeks ago. Offline
Joined: 14 Feb 2007
Posts: 295
Groups: Regional Representatives, The GrapeVine
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.)
Top