Try removing the project CPD file and reopen. Do you still get the issue?
Is there any more information in the error message?
I removed the CPD file but when I reopen the project it comes back. I even selected the "Clear project cache (.cpd) before opening any project" option in RH Tools. Even with a smaller CPD file I get the same message.
CPD file is a "Cache Project Database" file. It helps with RoboHelp HTML functions. There is no way to do without it. The thing is, sometimes one needs to "clear" it by deleting it. Once it's gone, RoboHelp will bake up a fresh one on the spot.
- I've been having the same problem for months, and have just entered this as a bug report (11/1/2013).Your suggestion did not work for me. I deleted the CPD file, opened the project from Source Control, and generated the WebHelp. The critical error dialog box still appears.
- The dialog box also gets hidden behind the RH window. To see it, I reduce the size of the window, enabling me to grab the dialog box and click OK.
- The error does not impede generation of the Help. However, the Generating message box (success/failure dialog is not fully active--"Click View Result to view: index.htm"--until you click OK in the error dialog box.
I continue to get the same problem, and there is no additional information in the dialog box.
During troubleshooting sessions with Adobe TCS Support, I've deleted the CPD file a few times. That has not solved the problem.
Furthermore, after closing the message box, I can continue to generate SSLs, but cannot check any files out of Source Control (Visual Studio & TFS 2010) until I close and re-open RoboHelp (currently RoboHelp 2015).
My environment is Windows 7 Experience SP1, 64-Bit, 8-GB RAM. Same problem occurred with 32-Bit OS and RoboHelp 11.
We're seeing the same error when we double-click a skin in the Skin Editor. In some cases, after closing the message box and making a change to the skin, RoboHelp crashes when you try to save the changes.
Thanks. I'd seen this article. However, since my hard drive crashed a couple of months ago and had to be rebuilt, with a new profile, and since this problem has been occurring for well over a year, I don't think this is the solution. I believe there is some faulty behavior between the Provider and RoboHelp.
Has anyone found a solution to this yet? I've been having the exact same problem for a year. My coworker (same setup) does NOT have this issue. It seems to be centered on my setup. Any advice?