Skip to main content
C
C_Kerr
Participating Frequently
June 11, 2013
Question

Robohelp hangs when I try to add baggage files to projects

  • June 11, 2013
  • 1 reply
  • 931 views

I have two RoboHelp projects using source control (Visual Studio/Team Foundation Server) in Robohelp HTML version 8. Both service packs are installed.

When I right click the Baggage Files folder and select 'Add to baggage files' the program hangs, and I have to crash out of it. This started happening in both projects at the same time, possibly as a result of me adding image files to the baggage files folder. I've reverted to the project as it was before I made these changes, but the problem persists.

I've started a new test project, not connected to version control, and Robohelp hangs in exactly the same way when I try to

Is there anything you could recommend? I'd be extremely grateful for any ideas. I searched the forum and couldn't find any references to anything like this issue.

Would you recommend resintalling Robohelp, for instance?

Many thanks.

This topic has been closed for replies.

1 reply

Captiv8r
Captiv8r
Legend
June 11, 2013

Hi there

You might try ensuring the file named RHBag.APJ is able to be edited. That's the file that keeps track of your baggage. And since you say you are using Team Foundation Server it strikes me that perhaps this particular file may still be set to read only status and that could be wreaking havoc with RoboHelp and causing the hang when you try to add to baggage.

Cheers... Rick

C
C_KerrAuthor
Participating Frequently
June 11, 2013

Hi Rick,

Thanks for yor speedy reply.

It's a good thought, but I've verified that the rhbag.apj file isn't set to read only. In fact, I tried editing it after the problem started in an attempt to add baggae files manually. That didn't work (I was able to trick Robohelp but not the server...).

Do you have any other suggestions?

Cheers,

Chris

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity Expert
Community Expert
June 12, 2013

Hi Amber,

You were right! Thanks so much, you've saved me a great deal of pain.

I'd recently changed my monitor configuration, so this must have started then. I feel a little foolish...

Best,

Chris


Chalk up another one to the multi-monitor pit of confusion! Good catch @Amebr!

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