Skip to main content
michelle_2106
Participant
February 3, 2026
Answered

Mini Toc in Frameless output is throwing an Invalid Resource error

  • February 3, 2026
  • 4 replies
  • 115 views

I am on RoboHelp R2026.01.11 and experiencing an issue with the Mini Toc in Frameless output, which is throwing an Invalid Resource error. The links work properly when Help is accessed locally, but when accessed via the Azure Storage location, the following error occurs:

"<Error> <Code>InvalidResourceName</Code> <Message>The specifed resource name contains invalid characters. RequestId:c038a57b-001e-00cd-7012-95711d000000 Time:2026-02-03T13:41:42.3999397Z</Message> </Error>"

 

I have searched the RH forums, searched AI and the web

I have tried: 

  • removing illegal characters from headings
  • changing headers to h3 only for mini toc
  • shortening the length of filenames

Does anyone else have any ideas, please?

Thank you

M

Correct answer michelle_2106

I have fixed it by manually adding mini-tocs inside the topic rather than letting the skin/output preset inject the mini-toc into build output,

4 replies

michelle_2106
michelle_2106AuthorCorrect answer
Participant
February 5, 2026

I have fixed it by manually adding mini-tocs inside the topic rather than letting the skin/output preset inject the mini-toc into build output,

Peter Grainge
Community Expert
Community Expert
February 5, 2026

OK if you are happy with that.


My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Community Expert
February 4, 2026

Are you able to publish another project on the server? The About RoboHelp sample project has a mini toc, see if that works.


My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
michelle_2106
Participant
February 4, 2026

Hi Peter, it fails on multiple projects published to the server.

Peter Grainge
Community Expert
Community Expert
February 4, 2026

Do you mean if you publish About RoboHelp to the server, that too fails? If you do, then the issue is your server.


My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Community Expert
February 3, 2026

Usually when something works locally but not on the server, it is one of two things

  1. The configuration of the server
  2. Not everything has been correctly uploaded.

If the answer to ​@Jeff_Coatsworth is that this is new, then checking 2 is worthwhile. Otherwise 1 is more likely and unless ​@Jeff_Coatsworth has any suggestions on that, then I suggest for this one you need to go to Adobe Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

 

First though it may be worth upgrading to the latest version which is 2022.6. You will need to download that from https://helpx.adobe.com/robohelp/kb/robohelp-downloads.html rather than trying Help > Check for Updates.

 


My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Jeff_Coatsworth
Community Expert
Community Expert
February 3, 2026

Was this project able to work before in this location OR is this something new that’s happening?

michelle_2106
Participant
February 4, 2026

It worked before. I have DevOps looking to see if anything has changed with the Azure Blob Storage settings