Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Rick, thanks so much for the details here. I've seen this posting before because I've encountered this error, but I must have missed the "Hide protected operating system files" option. This little bugger seems to have been the problem today. Found the file and deleted it. Now I can publish again. Guess that's what I get for scanning instead of reading thoroughly the first time. Thanks!!
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
not sure why you're chiming in on a post from 2008/2009 about something that Adobe has no control over (i.e. your Windows settings in the location you're trying to publish output to).
​Edited to remove email address
Copy link to clipboard
Copied
I am on this thread because I am having the same issue with Robohelp in 2016. Another user said he determined that there was no issue with the target directory being locked and I did the same determination. So it is an invalid assumption to categorize this as a user error with no responsibility on the software itself.
Copy link to clipboard
Copied
Hi just want to point out that this is some issue with Windows itself, rather than user error. I sometimes get locked out of publishing and find that closing Windows Explorer can fix the issue. (Note I'm also not saying Adobe is perfect, just that this issue doesn't appear to be something they can do anything about.)
Edited by moderator to remove email address
Copy link to clipboard
Copied
Have you tried adding a Publish location that is on your local drive? If it publishes OK there, then it's usually the case that either it is permissions or the above mentioned issue that trashing the output folder and recreating it works. That said, it is now years since I have encountered this myself.
Are you using a recent version of RoboHelp?
See www.grainge.org for RoboHelp and Authoring information
Copy link to clipboard
Copied
No I have tried adding a publish location on my local drive. The issue only randomly happens, not always. It is not something I can easily reproduce. I have noticed that directing the output to another folder first and then directing it back to the folder that had the issue also seems to correct it. I am using RoboHelp 11. I still suspect it is Robohelp itself that is causing this.
Copy link to clipboard
Copied
When you publish, it's basically just FTPing the contents of the generated folder in your \!SSL!\ output folder up to wherever you told it. When it happens again, try using some FTP software to upload it & see if it has an issue. I don't recall if you mentioned where your published location is - is a folder on a web server or someplace internal to your operation? I just wonder if the files are being tied up because of someone accessing them while you are trying to replace them.
Copy link to clipboard
Copied
The published location is on a network drive on our local intranet. It could be that someone else is accessing the files as I am trying to replace them. I did not intend to come off sounding so critical of Adobe or Robohelp. I appreciate the assistance everyone here has provided.
Copy link to clipboard
Copied
Here is an update about this issue which to me appears significant. Today I again got this issue multiple times when I was publishing my Help project, so as a workaround I generated help and published to a temporary location on the same network drive where the original help project that is having this issue is located. Once that was done I copied all the published files from the temporary location to the original location and there were no issues in copying. If the issue really is locked Windows files as some here are saying, how am I able to copy over those same files in Windows Explorer without issue that RoboHelp repeatedly said it was denied access to?
Copy link to clipboard
Copied
Hi there
One possibility is that at the moment you were copying any file that may have been locked before actually had the lock released.
I'm not sure anyone has categorically stated that THE reason this is happening is because files are locked. It's only been mentioned as a possibility.
I find myself wondering if RoboHelp just consistently refused to publish. Also, when the process bombs, is anything posted in the dialog that may mention what the file it gagged on is?
Cheers... Rick
Copy link to clipboard
Copied
@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
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied