Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
Junior Member
Posts: 74
Join Date: 7/28/15
Recent Posts
Hello,
We are in the process of upgrading from 6.2 to DXP 7.1
While running the db upgrade tool i am having following multiple exceptions(count is 365 for different unique files) related to document library files.
2019-02-25 20:14:29.866 ERROR [main][JournalArticleImageUpgradeUtil:88] Unable to get file entry from URL /documents/24059/30825/OnboardingChecklist_Terrein+functies_Manager_aanwerving+na+interim_FR.docx/a925fde7-13a6-4eac-a95c-c8d231160e57 com.liferay.document.library.kernel.exception.NoSuchFileEntryException: No DLFileEntry exists with the key {uuid=a925fde7-13a6-4eac-a95c-c8d231160e57, groupId=24059}
Using com.liferay.portal.store.file.system.configuration.AdvancedFileSystemStoreConfiguration for document library.
For the file mentioned in the above error i dont see a similar structure in my document library directory. Please see the image attached
How can i check if these files are really missing inside document library?
Also apart from that, have mentioned following incom.liferay.portal.store.file.system.configuration.AdvancedFileSystemStoreConfiguration.config file as well. rootDir="/liferay/data/document_library"
Then maybe they are just 365 images referenced in certain journal article (maybe pretty old versions) which are already lost in the original Liferay version. Could you check those articles in your current Liferay version?
Junior Member
Posts: 74
Join Date: 7/28/15
Recent Posts
Yes Alberto,
That is what we are trying to figure out, but bit confused on how AdvancedFileSystemStore stores data and how liferay tries to fetch data.
Meaning if the url is /documents/24059/30825/OnboardingChecklist_Terrein+functies_Manager_aanwerving+na+interim_FR.docx/a925fde7-13a6-4eac-a95c-c8d231160e57 then do i need to check insidedocument_library/20157/24059/30825 directory to see if the file exists or not?(20157 is the company id and inside the 6.2 document library there ate two directories namely 0 and 20157)
OR
Being the administrator can i simply hit the <domain name>/documents/24059/30825/OnboardingChecklist_Terrein+functies_Manager_aanwerving+na+interim_FR.docx/a925fde7-13a6-4eac-a95c-c8d231160e57 url to check if the file exists?
The error is thrown during the manipulation of image references inside JournalArticle XMLs, what I am suggesting is that you look for those references in the JournalArticle.content field in the original database. Once you know which journalArticles have those references you will be able to check if those references are already broken in the original version of Liferay just trying to edit those articles from the UI.
Junior Member
Posts: 74
Join Date: 7/28/15
Recent Posts
Hello Alberto,
I just followed what you suggested and checked randomly for some JournalArticles and found that yes indeed for those the old versions are having issues and the files are missing in the 6.2 environment itself.
I want to keep those old versions of JournalArticles as it is and want to proceed with the Upgrade. So can i simply ignore those exceptions?
This website uses cookies and similar tools, some of which are provided by third parties (together “tools”). These tools enable us and the third parties to access and record certain user-related and activity data and to track your interactions with this website. These tools and the informationcollected are used to operate and secure this website, enhance performance, enable certain website features and functionality, analyze and improve website performance, and personalize user experience.
If you click “Accept All”, you allow the deployment of all these tools and collection of the information by us and the third parties for all these purposes.
If you click “Decline All” your IP address and other information may still be collected but only by tools (including third party tools) that are necessary to operate, secure and enable default website features and functionalities. Review and change your preferences by clicking the “Configurations” at any time.
