Website Deliverables - webworks.com Previous Next Index Print
Common Word Errors

Common Word Errors

Last Modified: October 6, 2006

ePublisher Pro

The purpose of this article is to provide users with a troubleshooting procedures that have previously resolved the 3 common Word errors below.

"Cannot duplicate document '[docname.doc]' to '[path]\preview.docwif' and apply settings."

“Unable to create WIF document.”

“Adapter "Word" failed in method "GenerateXML" at step "2: Word.GenerateXML".”

These are general errors that are being thrown for one of two reasons: either ePublisher cannot communicate with Word or there is something corrupt in the source document (.doc) or source document template (.dot).

Before you begin troubleshooting

1)

Take note of the results as you go through the following steps, so that our support team can help you isolate the problem if you are not able to resolve it using these techniques.

3)

We recommend that before making any of the changes suggested below to your system setup, that first, you close Microsoft Word, Outlook and WebWorks ePublisher, and verify that no WINWORD.EXE processes are running.

*

To verify that none of these processes are still running, use the (Ctrl+Alt+Delete) shortkey command to open the Task Manager. Verify that the Processes tab is selected, and if you see any processes that say WINWORD.EXE or wpubword.exe, select them and choose End Process.

Troubleshooting

If you are using a custom template, often Word can embed references to missing paths to the template. To verify, open the source document that is causing these problems. Go to Tools > Macro > Visual Basic Editor and then go to Tools > References. There should be a list of Available References starting with the references that are checked. If you see a reference that is checked and says “Missing” in front of it, uncheck this reference and then save and close Word.

If not, there is something in your documents that is causing the crash and you will need to open a support case with the entire ePublisher project directory as well as a reduced version of the source document and custom template (if applicable) that will recreate the issue. In addition, please be prepared to answer the questions listed in this article.

Earlier versions of SnagIt that are older than SnagIt 8 have caused problems in ePublisher in the past. There are currently no known issues with SnagIt 8. If you are using earlier versions than SnagIt 8, you will need to disable these in Word.

To disable SnagIt 7, you will need to uninstall SnagIt and then reinstall. When you reinstall, you will be asked to specify what features of SnagIt you want to install. Be sure when you get to this step to disable the SnagIt Add-In for Word as illustrated in the screen capture below.

Disabling SnagIt 7 Word Add-In

To disable SnagIt 6, close all instances of Word and then open SnagIt. Go to Tools > Program Preferences > Addins and then disable the Word Add-In.

Due to limitations in McAfee, Norton Anti-Virus and Norton SystemWorks, you may encounter problems when attempting to create and generate output from a WebWorks ePublisher project if you are running one of these products on your machine.

If you are running Norton Antivirus, make sure that you have scripting enabled, Norton has a script-blocking feature that prevents WebWorks Publisher from making some necessary calls to the system.

First, close all other applications (especially Outlook or other e-mail software), and ensure that no WINWORD processes are running, see Step 3 in "Before you Begin Troubleshooting". Then close Norton Anti-Virus or Norton SystemWorks, and try creating your project or generating your output. If closing the Norton product does not resolve the problem, we recommend you implement the workaround described in the following Microsoft KnowledgeBase article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q243579

Check the Macro security in Word (Tools -> Macros -> Security). If the Security Settings are set to High or Very High, try changing them to Medium. Before doing this, please be sure that you have ended all WINWORD processes, see Step 3 in "Before you Begin Troubleshooting", otherwise the security settings change may not take effect. Then, try creating a project again.

Often users who have their files located on a network or shared drive will encounter these errors. Users may be able to modify these files over a network drive; however, ePublisher accesses these files differently and depending on how your system administrator setup your security settings, you may not have sufficient privileges to access these files from a program like ePublisher even though you have access to modify the files directly. To verify, create a project on your local C: and add documents that are also located on your local C:. If you are then able to generate properly, you will need to get with your system administrator to setup the appropriate security settings.

It never hurts to check to make sure the source files were not set to Read Only. Double check by right-clicking on your source document and verify that you have read/write access privileges to the file.