Skip to main content
hba_chs2012
hba_chs2012
Participant
September 27, 2017
Question

Server Busy error after pulling from version control

  • September 27, 2017
  • 1 reply
  • 751 views

I have a project maintained in version control via SharePoint that I need to pull down into my now-updated RoboHelp 2017. I'll get all the way through setting up my local path and have the files pulled down. However, once I click the .xpj file, it acts like it's going to open and hits me with a "Server busy, switch to busy program to activate and close it."

When you try to do so, though, it only brings up the start menu and doesn't actually take you to a program to close. Any time you click away, it brings you back. Eventually, I have to open Task Manager to kill RoboHelp.

I did already try this registry fix on another computer (I have two and am receiving the same error on both): Msscci with RoboHelp – michal.Log

No dice. I also tried these fixes on the chance they worked: Server Busy error when launching or using Lightroom on Windows

No dice there, either. I have also uninstalled and reinstalled using fresh packages for RoboHelp and SQL Compact Server. Winmerge is up to date. I do not have TFS but I do have Visual Studios 2010 for Office.

Anyone have any ideas? Thank you!

Full error text: "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem."

This topic has been closed for replies.

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
October 3, 2017

I have seen this error in the past (long time ago) but not in connection with RoboHelp. As far as I can recall, a reboot fixed it.

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.
hba_chs2012
hba_chs2012Author
Participant
October 3, 2017

I'd have to check with my lead who actually fixed the issue, but I think part of it was tied to ridiculously long file names. She spent the weekend redoing file names and breaking the context-sensitive help (which our application doesn't use anyways).

Thanks!

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
October 3, 2017

Interesting. It would be useful if you could confirm that.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices