Hello Yana, 

We strongly recommend to transfer packages between sites with the same build (products) and versions to avoid any errors. 

It's hard to identify the root cause of the issue with no access to the system. But based on the shared information, I may assume that the issue is related to the lookup column that has no "Do not control integrity" option enabled in its settings and the issue occurs as the database structure for the object cannot be successfully updated while installing the package. I'd suggest to check it and as well fully generate and compile the system, and also resolve possible generation / compilation errors. 

If the issue persists despite the provided recommendations, please contact support team via support@creatio.com to proceed with investigation. 

Best regards,

Anastasiia

hi.

You do need to look at server logs.

SQL.json + Packages.log

You'll see there not only most recent error but first error, for example

"ErrorMessage":"The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FKcCbW9f8n8IYIlNxWjlw0Vi1Gqc"

The conflict occurred in database \"...........\", table \"<lookup_table_name>\", column 'Id'."

and only next - 'dbo.UsrGeneralViewFile.FKcCbW9f8n8IYIlNxWjlw0Vi1Gqc', or the object does not exist."

most probably, you have records in the lookup column of the table UsrGeneralViewFile that do not exists in your lookup table