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.
Participant
December 2, 2008
I have no "Thumbs.DB" files. I have deleted and recreated the output folder.

I still receive this error message when I attempt to publish.

"
Publishing has been cancelled.
Access is denied.
"

I use Robohelp 5 and it is used on an intranet environment.
MergeThis
Inspiring
December 2, 2008
Try generating and publishing to completely new folder locations.

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
March 25, 2008
Unfortunately, the intranet web site links to the project at a specific folder location, so I'm permanently tied to it and can't change it. I guess I'm doing the only thing I can under the circumstances, eh? At least I know!

Thanks!
Captiv8r
Legend
March 25, 2008
Hi Maureen

Perhaps look for the existence of a file on your side of the publishing bit that is named: thumbs.db. Seems I've read somewhere that this little beastie can toss a monkey wrench into the wringer.

Note that you may need to perform the following steps in Windows Explorer to see it.

Click Tools > Folder Options...
Click the View tab
Scroll down and choose "Show hidden files and folders"
DE-select Hide extensions for known file types and Hide protected operating system files (Recommended)
Dismiss the dialog and scan for the file. If you find it, delete it and try publishing again.

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