RH2019 Update 2: Publishing error "Failed to create directory"

[joannez73713747]

Hello everyone:

Background: My company upgraded laptops, so I'm setting up my new system, including RoboHelp. I just upgraded to version 2019, Update 2 (but want to use RH Classic).

I did a quick test to see how things would go. I successfully generated my files using the Responsive HTML5 output. (I verified my FTP connection and credentials were all still valid.) Upon publishing, I received the following error: "Publishing has been cancelled. Failed to create directory: site."

I checked with our IT team, and they verified that things were working properly on the server side.

Have any of you seen this error, and can you possibly advise me on how I might resolve this? Thank you in advance.

[Peter Grainge]

See Item 5 in Snippets WebHelp on my site.

---

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

[joannez73713747]

Hi Peter:

Thanks so much for your response. I visited the link you provided, and tried all of the options, but had no success. This morning I re-created my Responsive HTML5 output, re-entered my FTP credentials, and tried again, but got the same error. On a side note, I have an FTP tool (FileZilla) open, and I'm able to ftp my updated help topics and publish them with no errors using that method. It's only when I try to publish via RoboHelp 2019 (Classic) that I'm having this problem.

Do you have any additional thoughts on what else I might try? Thanks again for responding to my initial post.

JZ

[Peter Grainge]

Sorry but no other answers. Creating a new folder has always worked to the best of my recollection

As an alternative to File Zilla, you could try SyncBack. I have used for publishing to a server that does not allow FTP connections and requires SFTP, which RoboHelp did not support. With that I published locally and then SyncBack compares the local and remote folders and files. It can be configured to delete as well.

---

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge