Skip to main content
D
Danguy
Participating Frequently
March 24, 2014
Question

Robohelp 9 Compiler/Single Source Layouts are dead

  • March 24, 2014
  • 1 reply
  • 310 views

Hi

We are using Robohelp 9 on Windows 7 and after working on the same project for 2 years now, all of a sudden, the project will not close down without crashing it from the Task Manager, and also we select compile HTML file and it just does nothing.

We cannot compile any single source layout. We also cannot create a new single source layout - system just ignores all commands.

We tried deleting part of the project - thinking it was maybe too big, but that is not the case.

We tried copying the project to another computer thinking maybe the installation is corrupt.

We also tried deleting the cpd - no luck.

Can anyone put light on this matter - why do these things always happen just before a deadline?

Thank you

Melanie

This topic has been closed for replies.

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
March 26, 2014

First we need to ascertain if this is machine or project specific?

Did the copy work OK on the other machine?

What happens with one of the sample projects on the problem machine? Click Open on the RoboHelp Starter page and then click Samples in the ribbon on the left.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
D
DanguyAuthor
Participating Frequently
March 26, 2014

Thank you for your reply.

The file was on the TFS source safe. I removed it and was still experiencing the same problem.

I did everything you suggested, opened samples, all other files work, all other projects that were not on the TFS open.

The strange thing is that once we removed it from TFS, the same file did work on other machines, but on mine would not close and would not compile.

After a lot of analyzing i saw an odd file that must have come from the TFS with an ext .ldb.

I am wondering if this originally caused the problem.

For now we have recreated and reconstructed the file by slowly importing folder by folder of topics into the project trying to isolate problematic topics. 

Thank you

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