Do you get the same with a non-customised layout? Then we will know whether
or not the issue is your customisation.
If that has the same problem then this post might be better in the Fm
Let us know and I can move it if required.
I did as you asked, and I did receive the same message with a fresh copy of the Azure_Blue screen layout.
If this would be better in another forum, yes, please move it. And thank you.
Where is that R:\ drive located? You might try creating a new blank project on your c:\projects\project_name\ folder as a test.
The R:\ drive is a shared drive for the documentation for our product. There is a main folder that all the FrameMaker books are kept in - between 35 and 40; and a folder with all the images for all those books. There are 2 of us that share these subfolders. As you can see in the supplied image, we are importing the FM books into the RH2017 folder\product version folder\ and then what specific book. This message does not happen for all the projects, just 5 or 6.
I will try and copy the necessary folders locally and test as you requested, but I'm concerned that missing and broken links will make this an exercise in futility.
Update: I copied the FM book and images matching the folder names on the network to my local machine. I repeated the RH project creation 3 times, twice it worked and once I got the error messages. So bizarre. There are 73 records in the FPJ file, and they don't change before to after this process
You shouldn't have to copy anything - just create a new blank RH project on your local c:\ drive and import your FM docs into it to see what's happening.
That worked. The FM documents are where they live on the master drive and I created the RH project on my local machine. I imported the FM documents and RH layout from the master drive, and there were no errors as the RH project completed it's import process on my local machine. So we have a work-around to the error. Thank you!
But the QA part of my brain is still yelling "Why?" I would really love to solve the mystery if there is a data issue so we are not having to move/copy data folders in the rush to get a release out the door by a deadline.
Again, thanks for your help.
It might be due to the "invisible" path/file length restriction that RH has - when your source FM files have a total length of path+filename of about 30 characters or longer, RH starts having a fit - some xrefs don't come across properly or not at all. Ran into that one a few years ago.
You might also have some issue with permissions/restrictions on that network location.