This means that your .NET Framework install has become corrupted. The best way to solve this is to run the .NET Cleanup Tool.

More information here: http://blogs.msdn.com/b/astebner/archive/2006/05/30/611355.aspx

This means that your Windows Temp folder is full and needs to be emptied. This should not be an issue with Doc-To-Help 2011 V1 and later releases.

To clean out your Temp folder, follow these instructions:

http://pcsupport.about.com/od/maintenance/ht/manualtempvista.htm

First, check to see what version of Word you have installed. If you have 64-bit Word 2010 SP 1, then it is an issue with that specific version. For the time being, roll back to the pre-SP 1 version of Word. We have fixed this issue in 2011 V2, which will be released on 8/30/11.

If you do not have 64-bit Word 2010 SP 1 installed, check your Process in Task Manager and make sure that you do not have multiple instances of WINWORD.EXE running. If you do, there is probably an issue with your anti-virus software and that executable. Most likely, you have AVG installed.

Go into your security settings and allow WINWORD.EXE to run.

You need to attach either the C1H_NOMARGIN or C1H_NORM template to your document.

See the attached animated GIF for steps on how to attach the template.

You need to add the two templates to your STARTUP folder. That folder is located here:
C:UsersAppDataRoamingMicrosoftWordSTARTUP

If the templates are there, then you will need to add them/attach them in Word. Follow the steps in the attached animated GIF (made using ComponentOne DemoWorks) to add/attach.

It seems to me an issue with the user rights and permissions for the registry. that might be you don’t have access to the registry licenses key “No Read permissions to licenses key”

To examine the user permissions, follow these steps:

1) Log on to the problem computer as an Administrator.

2) Click Start, click Run, type regedt32, and then click OK.

3) Select the \HKEY_CLASSES_ROOTLicenses key.

4) On the Security menu, click Permissions.

5) Make sure that the necessary users and groups have at least Read permissions to the key.

6) Close Registry Editor and restart the computer.

You need to either provide yourself Admin rights or to install the software under the specific user, which was an administrator, and not under the local administrator of the machine.

1. On the Doc-To-Help Home tab, use the Select Target drop down to choose your Manual Target.

2. Open the Help Targets dialog box (click the dialog box launcher on the Home tab, Target ribbon group.

3. Go to the Fix Numbered Lists drop-down and choose Always. Click OK.

4. Rebuild your Manual Target.

Sabine Kamprowski

This exception can be raised when trying to build NetHelp target. This may be caused because occasionally, system problems can erroneously unregister one of the essential Windows components: Windows Script Host.

For resolving this issue, you need to re-register VBScript.dll. Refer to following link for the same.

http://helpcentral.componentone.com/nethelp/d2h2011i/#!documents/errors1720and2738.htm

This exception is raised when trying to add/sort Glossary Terms in Glossary document using "Add Glossary" and "Sort Glossary" toolbar buttons of D2H tab.

This is a known issue with some of the Word 2010 Versions. This issue has been fixed in D2H Build 735 of 2012 V3.

This build can be downloaded from the following link: D2H Build 735 .

- With the target set to Manual, the build gets stuck at 70% and hangs there forever. This is critical for our organization
- Help 2.0 crashes with error "Could not execute Help Compiler HxComp.exe"
- HTML Help appears to work! Great, HTML Help is one we need!
- JavaHelp doesn’t work at all – required files missing
- NetHelp works but we don’t need it
- WinHelp crashes with "fatal Word error: Division by zero" when attempting to adjust left indents (after generating RTF…)

Any suggestions?

For the errors with Help 2.0, JavaHelp, and WinHelp, there are support files that you need to download to build these outputs. If you do not need to use these outputs, then I wouldn’t worry about the fact that you can’t build them. The Manual build issue seems like the critical one.

More information on the support files you need to build those outputs:

http://helpcentral.componentone.com/nethelp/d2h2012/WordDocuments/doctohelpoutputsanddeliverables.htm

Regarding the Manual target build issue, I have some questions:
1. What version of Word do you have installed (including service pack and whether it is 32-bit or 64-bit)?
2. Do you have the target set to build as a .doc (97-2003 format) or .docx (2007-2013 format)?
3. Is the Generate PDF Target checkbox checked in the Help Targets dialog box?

1. Word version: 14.0.6129.5000 (32 bit)
2. It was .doc – I changed it to .docx
3. It wasn’t checked – I have now checked it (and it produces a .pdf)

After those changes the Manual output completes with a warning that it failed to update page references. The layout is wrong though and tables muddled. I’m guessing this is to do with templates we had in the XP user profile for D2H 2007. I’m experimenting with the templates…

If you’re looking to create Help 2.0, check the Notes on Microsoft Help 2.0 section in the Doc-To-Help Outputs and Deliverables topic that I linked to in my previous post. That will let you know what you need to download/install/adjust in order to build Help 2.0. It is also very helpful to have Visual Studio 2005 installed on the computer that you’re trying to build Help 2.0 on.

For the Manual, it sounds like you were able to build it, which is good news.

For the formatting issues, I would recommend updating the default template for Doc-To-Help 2012 (C1H_PRNOMARGIN for most projects, but you may have an A4 template) with your cover sheet and styles.

1. In Doc-To-Help, go to the home tab, choose the Manual target, and select Edit Template from the Target Template dropdown.
2. Do a Save As for that template under a custom name (like TOHTORI_PRNOMARGIN.DOT).
3. Make any necessary changes to the cover page, headers, and footers. More information on how to do that here: http://our.componentone.com/2009/09/26/customizing-the-cover-of-a-manual-in-doc-to-help/
4. Use the Organizer in Word to copy your styles from your old template to the new template. I attached a document to this post called UsingTheOrganizer.docx that will show you how to do this.

One other thing to keep in mind: Given your location, you might want to use one of our A4 templates instead of the default PRNOMARGIN template. We’ve found that Europeans like the A4 format, which is why we added the PRNOMARGIN_A4 template in 2011. If you want to use the A4 format, edit that template and save it under a custom name (ie TOHTORI_PRNOMARGIN_A4.dot).

Hope this helps!
Brad

SP1 (64-bit). I am an Administrator for the workstation.

When trying to produce a NetHelp project, Doc-to-Help stops at 37% and issues a "FATAL ERROR OCCURED: ABORT" message:

Reading project data…
Guide.doc
Processing fields…
Processing list paragraphs…
Converting lists to text…
Converting image map pictures…
Saving preprocessed document…
Preparing HTML file…
Processing HTML file…
** Fatal error occurred: Abort.
** Build Failed.
1 Error(s)
0 Warning(s)
0 Broken Link(s)

Is this a known issue, is there a fix?
Any idea what I can tweak or where I can do to solve this issue?

Thanks,
Claude

The most likely cause of this issue is that you have Internet Explorer 9 installed and that version doesn’t support IE 9. I would recommend either upgrading to 2011 V1 (Build 627) or uninstalling IE 9 and installing IE 8.

Here’s the download link for that version:

http://download.componentone.com/pub/HelpAuthoring/doctohelp2005/Updates/DocToHelp2011-1-Build627-Setup.exe

If you’re not sure if you have access to this version, send an e-mail to bradk@componentone.com with your serial number and I’ll confirm whether or not you have access to 2011 V1.

Hope this helps!
Brad

It looks like some versions of Office (mostly 2013) aren’t clearing their values in the registry when they uninstall.

http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/08f13e9d-895c-4102-b6d9-e327af8cf8c0/

http://stackoverflow.com/questions/12957595/error-accessing-com-components

In order to fix the issue, you would need to go into the registry and delete the unnecessary values.

- Restart the computer.
- Run regedit.exe
- Find this key for 32-bit Windows and 32-bit Office or 64-bit Windows and 64-bit Office:
HKEY_CLASSES_ROOTTypeLib{00020905-0000-0000-C000-000000000046}
or this key for 64-bit Windows and 32-bit Office:
HKEY_CLASSES_ROOTWow6432NodeTypeLib{00020905-0000-0000-C000-000000000046}
- The following subkeys should be there for installed versions of Word:
8.4 – if MS Word 2007 is installed
8.5 – if MS Word 2010 is installed
8.6 – if MS Word 2013 is installed
- Remove the subkeys for *uninstalled* Word versions. For example if you have uninstalled Word 2013 then remove subkey “8.6?.
The subkeys for installed Word versions only should be remain.
- Launch Word, then close it.
- Launch Doc-To-Help

I attached an animated GIF (FindTypeLib.gif) that shows you how to do this. Your registry should look like mine (with just the 8.5 value in the subkeys) if you have Word 2010 installed.

(I should note that I’ve used Robohelp for years prior to Doc-To-Help, and with RH you can just import .pdfs as "baggage files" and link to them from .htm topics in the help project…Doc-To-Help has numerous other advantages, though. It would be nice if Doc-to-Help provided a similar "baggage file" capability.)

Please let me know if you have any other ideas – we really could use the .pdf content that we have for our project. Thanks a lot.

You should just be able to make a link to a file (either using the Hyperlink button on the Insert tab in Word or creating an External link in the built-in editor) on your computer.

When you build your NetHelp target, any files you’ve linked to will get placed in the LinkedDocuments folder in your NetHelp folder. Wherever you place that folder, the LinkedDocuments folder will go with it, so your links should always work and shouldn’t dead end.

Hope this helps!
Brad

I followed the steps and everything worked fine. Thanks a lot for your help!

Wayne