Sadly, this is once again an issue for me - well, in reality, it never stopped being an issue. I had one successful publish and since then, I've never performed a Republish All action. As long as I just published changes, it was successful.
However, today, the project was inadvertently deleted from the server and now I have no choice but to republish all files. I have repeated the steps mentioned in my original post again to try to get it published. It failed on one PDF, so I deleted that PDF for now -- just as a test but it failed on a different PDF. So I deleted and then re-imported all the PDF baggage files and removed the hyperlinks referencing those PDFs and and re-added the links back in. Still fails. Other attempts where it seemingly moves past the PDFs, it gets hung up on a Captivate SWF file. Keep in mind, this is not a new project or even new PDFs or Captivate SWFs, it has successfully published for at least 2 years prior to this issue 6 months ago and now.
I chatted with support and confirmed that WebHelp Pro publishing from RH 2017 to RH Server 9 is compatible. I am trying to see if they can offer any other assistance about this particular project’s problem
Just ended chat and remote session with Adobe Support. He did a lot but in the end he said what allowed him to publish finally - were the following steps:
- Delete CPD
- Delete XPJ
- He moved Project Folder from My Docs on C Drive to new location on Desktop (I would guess this would be optional)
- Start RoboHelp > File > Open > Project Folder Location > Choose HHP File
- Open project as HHP file.
- Publish - It finally published all files.
I have since just opened the project using the standard .xpj file and have generated and published successfully.
However, one caveat I will mention - is that it is now publishing with a hybrid of two different skins - but that is a problem I can work on tomorrow as long as the content is there!!
I am surprised to see that was the solution. It is a known way of opening a corrupt project (it's on my site for that purpose) but I wouldn't have thought of it in this connection.
I have edited your post to number the steps and I think that Step 3 is what fixed it and probably would have done so alone. Behind it is likely a long path that exceeded the number of characters Windows supports. I didn't consider that as you had published before but likely you added something that just ran over the limit (256).
Using that method, certain things may have been lost. You need to take a look at Opening Corrupt RoboHelp Projects on my site and check them out.
See www.grainge.org for RoboHelp and Authoring information