Skip to main content
Known Participant
March 25, 2008
Question

Can't Publish Project

  • March 25, 2008
  • 4 replies
  • 3201 views
Periodically, something within Robohelp appears to get corrupt with a project. When that happens, the project compiles without any problems until you click Publish. At that point, a Webhelp dialog displays, saying "Publishing has been cancelled. Access is denied."

The only thing I've found that fixes the problem is totally trashing the project and starting over. I move the existing project out of its original folder, then import the .hhc file into a new project. It retains the settings and the formatting, and publishes with no problem.

Is this the ONLY solution? Does anyone know how to fix the problem AND keep the project? I'm asking because I have over 20 projects, and they ALL went corrupt today. Usually this problem only affects one project at a time. But today I'm facing an afternoon of recreating them all...
This topic has been closed for replies.

4 replies

Peter Grainge
Community Expert
Community Expert
March 25, 2008
Anything is possible. All I can say is that the solution has worked for everyone else. That would also fit with Rick's suggestion as the process would trash those thumbs.db files.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Known Participant
March 25, 2008
Peter, you were right. I was confusing "output file" with the "Select Output Folder" field in the project setup - the one that goes to the C:\ drive. I went back in and deleted the output folder on the server and THAT'S what fixed it! All's well again! Thanks much!
MergeThis
Inspiring
March 26, 2008
Going back to your initial posting, in which you state that the project generates fine, but publishing does not ("Publishing has been cancelled. Access is denied.").

You might be overreacting to the identical situation that I encounter from time to time, which apparently is simply caused by excessive traffic on our networks, rather than any project corruption.

As long as you have published the project once (that is, the "Server Name" link has been checked and you have published), then right clicking the WebHelp layout and selecting the Publish option allows you to publish the output that was previously generated without having to re-generate it.


Good luck,
Leon
Peter Grainge
Community Expert
Community Expert
March 25, 2008
If Rick's suggestion is not it, then still no need to trash your source. Trash the target folder and then create a new folder with the same name.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Known Participant
March 25, 2008
Peter,

Our postings crossed! The fact that I couldn't reuse the project to publish in a different location suggests the corruption is in the project itself. However, it doesn't carry into a new project when you import the .hhc file. I may have a different problem from the one you've encountered, because so far that's been my only fix!

Thanks!
Peter Grainge
Community Expert
Community Expert
March 25, 2008
You do not need to trash the project, just point to a new output folder.

And sorry we don't know why. Folder permissions / Read Only flags have been suggested but I have disproved both.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Known Participant
July 19, 2016

This is why I just LOVE Adobe Products.  The company seems like it is great and all but usage of their products has left me less than thrilled.  They need to be on top of issues like this and they just never are.

Known Participant
July 29, 2016

@anyhoo What you have done in Post 23 in this thread is effectively the same as my original response in Post 2. Trashing all the content by one means or another (your way or mine) is the fix. If only we knew why.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge


I'm glad I'm not the only one who is having this issue and that others besides me at least suspect it is an issue with Robohelp and not just due to Windows locked file(s) and/or directories.  One thing I have noticed is that the issue does not always happen but when it does it happens consistently from that point on.  In other words, if the Robohelp project is left open and you publish over and over again, you will get the issue over and over again no matter how many times you publish.  That has been my experience at least. 

Known Participant
March 25, 2008
Oh. And does anyone know what causes this?????