Hi All,
Recently I upgraded our OpenKM instance from 6.2.2 to 6.3.1. Generally speaking the upgrade went pretty well. This week someone tried to access this directory from Taxonomy: "Field Service & QC" which resulted in the error in the attached screenshot.
I went back to the backup I made prior to the upgrade and exported the directory. I then imported it into a new folder "Field Service and QC" as my current working theory is that the ampersand (&) caused a problem somewhere during the upgrade. I'll be discussing special characters with the app admin tomorrow.
Here's what I want to know:
Recently I upgraded our OpenKM instance from 6.2.2 to 6.3.1. Generally speaking the upgrade went pretty well. This week someone tried to access this directory from Taxonomy: "Field Service & QC" which resulted in the error in the attached screenshot.
I went back to the backup I made prior to the upgrade and exported the directory. I then imported it into a new folder "Field Service and QC" as my current working theory is that the ampersand (&) caused a problem somewhere during the upgrade. I'll be discussing special characters with the app admin tomorrow.
Here's what I want to know:
- What table or tables in the database translates the UUID into the physical file location on disk?
- Has anyone had an issue like this before?
- My current plan is to either re-add or correct the UUID (69910746-c658-47ae-91b9-d399e4e3c667) to the db and map to a good file location, or delete the uuid and it's references within the database. My hope is that this will delete the directory. Any other suggetions?
Attachments
screenshot.PNG (9.73 KiB) Viewed 2082 times
