Skip to main content
Mark Puddephatt
Mark Puddephatt
Participating Frequently
February 9, 2017
Question

Publishing to Sharepoint

  • February 9, 2017
  • 1 reply
  • 1221 views

Hi all,

Firstly, the basic info. We're using RoboHelp 8 and publishing to Sharepoint 2010. Upgrading either of these is not an option, sadly.

I have been publishing to Sharepoint from a HTML project for years without issue, but now am trying to migrate one of our other projects to be published on SP and the user keeps getting the same issue which causes the Publish to fail...

I have ruled out a few issues including fixing filenames with & symbols (Sharepoint doesn't support them) and I've elevated this user to "Full control" of the target Document Library (effectively admin level permissions), but it still keeps failing part way through. If I publish the same from my PC then it works fine though. The only difference is that I have "site admin" permissions on the Sharepoint site, rather than just having permissions on the Library.

I did another test on another RH project to a different Doc Library on the same site, with a different user, and they were able to publish without any issue - hence I believe the SP permission level is fine and there may be some other issue I'm not able to figure.

I cleared all the files out of the SP library and then got my test user to try again, it got a little further but still failed (as shown above). It always seems to stop at the bsscftp.txt file. I've read some posts about that file on the forum and it seems to be generated as part of the Publish process by RH. Again this hasn't caused any issues for my other projects.

Any suggestions please?!

This topic has been closed for replies.

1 reply

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity Expert
Community Expert
February 9, 2017

have you had them try the 2 step process? Generate to a local folder, then copy it to the destination? That way you can isolate the issue to RH or the destination (my money's on SharePoint messing up)

Willam van Weelden
Willam van Weelden
Inspiring
February 10, 2017

To rule out the permission issue, could you try (temporarily) making the user you use for publishing as site collection admin?

My first thought is to check the path length. Windows doesn't allow paths over 256 characters. Can you map the SharePoint library to a network drive letter in your Windows and publish using that?

Mark Puddephatt
Mark PuddephattAuthor
Participating Frequently
February 10, 2017

Thanks both I will try all these suggestions.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices