Skip to main content
Inspiring
April 26, 2017
Answered

RoboHelp 2015 .xpj Files Crashing RoboHelp 2017

  • April 26, 2017
  • 4 replies
  • 3153 views

Recently upgraded from RoboHelp 2015 to RoboHelp 2017. Normally, a project created in the older version updates automatically simply by opening the .xpj file in the newer version. However, RoboHelp 2017 hangs in both Windows 7 and Windows 10 when trying to open the .xpj file created in RH2015.

I've tried all the old stand-bys: rebooting the computer, giving the project hours to open in case it's trying to update, attempting to open projects with a smaller number of files, re-installing RoboHelp on the computer, and installing RoboHelp on a different computer. The end result has been the same. After about 3 seconds, the Starter screen freezes and dims slightly, and RoboHelp continues to churn until I kill it in Windows. I've noticed two messages in the status section at the bottom of the screen: either "loading xxx.xpj" or "Loading DB info."

I also tried deleting the .cpd file and opening from the .hhp file. Same outcome.

One other observation: Typically when updating a project to a new version of RoboHelp, a pop-up displays saying that the project was created in an older version and offers the option to update in the new version. No popup displays before the system hangs.

I am able to create a new project in RoboHelp 2017, so the app seems to be working as long as it's not updating older files.

Anybody else encountered this issue and come up with a work-around?

Thanks,

Steve

This topic has been closed for replies.
Correct answer SJL_Amplify

Indeed, this was a bug, and Adobe fixed it in Release 2017.2.

4 replies

SJL_AmplifyAuthorCorrect answer
Inspiring
October 4, 2017

Indeed, this was a bug, and Adobe fixed it in Release 2017.2.

Inspiring
December 20, 2017

I am trying to open a 2015 project in a new trial version of Rh 2017 (13.0.0.257) (Windows 10). The project is locally hosted.

I am having the same problems as described in this thread. I have deleted the CPD file, edited default.css to leave only one entry for font-face, uninstalled and rebooted and reinstalled, tried opening using various methods (launch the .xpd file, select File > Open), and it hangs and hangs.

At one point I was able to open the project but none of the topics or TOCs were present. I started to create new folders and import the topics manually, but Rh eventually crashed. I opened the project a second time and the folders/topics were not there. A second attempt to manually import the topics resulted in a crash.

Now I can't open the project at all.

Is this a problem that shows only with the trial license?

Please advise…

Peter Grainge
Community Expert
Community Expert
December 20, 2017

Note, this is a quick reply without having read through the thread. I'll look tomorrow, late here.

The obvious point is that the marked as correct answer was with Update 2 applied. You can, and should, apply updates to the trial version.

The trial version is not crippled in any way.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Inspiring
May 1, 2017

To anybody who might be interested, I tracked down the culprit. We have been using @font-face in default.css to embed custom fonts in our output. Removing @font-face from default.css resolves the issue of RH2017 hanging when trying to open a project that opens in RH2015. Unfortunately, it also removes the custom font. Looks like I'll be opening a new question and, potentially, filing a bug report.

Peter Grainge
Community Expert
Community Expert
May 1, 2017

To be clear, that worked in 2015 but fails in 2017 or just fails the

upgrade but then works again?

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Inspiring
May 1, 2017

The @font-face code in default.css worked in 2015 and crashes 2017. If I remove the @font-face code from default.css, the project successfully opens in 2017. If I re-add the @font-face code in 2017 to default.css after opening the project successfully, the project crashes and won't reopen.

Inspiring
April 27, 2017

It looks as though it might be related to some customizations I made to default.css. I took the sample project that worked in RH2017, pasted our custom default.css into the project folder, and tried to reopen the project. It didn't open. So I pasted in the default.css from one of the sample projects, and then the project opened. Has something changed in the way RH2017 parses that file? Odd that 2015 would open fine, but default.css would cause 2017 to hang.

Captiv8r
Legend
April 27, 2017

Hmmm, I'm not a member of the RoboHelp development team so I can't say for certain.

I suppose one way to know for certain would be to take a project that you have created that does NOT have the CSS, open it in RoboHelp, then attempt to import the CSS into the project and see if it makes 2017 Release gag.

If so, I'd consider it's likely a bug and should be reported to adobe using the link below.

Click here to report a RoboHelp bug

Cheers... Rick

Inspiring
April 27, 2017

That's exactly what I did, and that's precisely what happened. A bug report it is!

Thanks Rick!

Peter Grainge
Community Expert
Community Expert
April 26, 2017

You don't get a warning because projects can be opened in either version.

See The RoboHelp Tour on my site for more about that. (You mustn't edit the

new layouts if you revert to 2015.)

RoboHelp opens OK but it hangs when you try to open a project, correct?

Is it the same with the sample projects?

Did you have admin rights when installing?

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Inspiring
April 26, 2017

Yes, RoboHelp 2017 opens, but it hangs when I try to open a project created in RH2015. It doesn't have a problem with .xpj files created in RH2017.

I did have admin rights when installing, and I also tried running as an administrator to see if there'd be a different outcome. There wasn't.

Peter Grainge
Community Expert
Community Expert
April 26, 2017

It shouldn't make a difference which version it was created in.

Are you basing your statement that projects created in 2017 open OK on

trying the samples or one you created?

Are the 2015 projects local?

Do you still have a machine with 2015 installed?

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