No JournalArticle exists problem during import process

Ervinas Marocka, modified 6 Years ago. Junior Member Posts: 31 Join Date: 10/8/18 Recent Posts
Hello,Having a hard time discovering the problem, remembered that community exists. Having a question, what does exactly means the following situation. I'm taking all web content as an export to prepare for import process in my staging server. Want to get all web content from one site template to the other. What do i do:
1. Doing an export on site A;
2. Getting the .lar file from site A;3. Getting to the site B -> Web content section -> Import;4. Choosing the .lar import file to import.5. Running import.Everything is doing clearly with AssetTags, and finally, somewhere it freezes. I know how to unstuck the process running some sql scripts. 

Problem:
Facing some errors related with JournalArticle : "No JournalArticle exists with the primary key xxxxx". Not sure if this stucks the process.
Moreover, having some other problems : "[CompanyThreadLocal:38] getCompanyId 0" Is this the case ? It stucks when Quartz Worker failed to get values?
By any chance there is a better and deeper logging on import/export process? I have already did the debug levels to "ALL" on export and import classes, also on "lar" classes. 
Working with Liferay 7 GA7.
thumbnail
Jorge Díaz, modified 6 Years ago. Liferay Master Posts: 753 Join Date: 1/9/14 Recent Posts
Hi Ervinas,
Do you think you are going to receive more attention writing "Help" every two hours?
This is a community forum and people will answer in case they have time and they know the response.
Regards,
Jorge
-----
Update: thank you for removing all the "Help" messages from the thread.
Ervinas Marocka, modified 6 Years ago. Junior Member Posts: 31 Join Date: 10/8/18 Recent Posts
That means, no one have time and no one knows the response for their own products. Seems nice. 
thumbnail
Jorge Díaz, modified 6 Years ago. Liferay Master Posts: 753 Join Date: 1/9/14 Recent Posts
 Hi Ervinas,

If you think you are going to get more help with comments like that, please go on.

I think it is better to give more information, for example:
  -  Activate debug traces and try getting more information
  -  Attach the log errors
  -  Check database information
  -  etc...


Regards,

Jorge