Strange, but had just the same issue this morning with one of my Captivate files. Checking the path where CP wanted to put the Word-document, it was a very weird path. Several months ago I had once copied the CP-file to a content collection on our LMS, and apparently this had got frozen in the memory of CP (??) and it wanted to publish the document over there. I just changed the path to my PC, and it worked all right.
It is worthwhile to check the path, one never knows that your CP has the same memory glitch???
Hi, thanks for your reply. When I click File/Export a dialog box appears in which I have tried to select a few different locations (my desktop, the C: drive).
Unfortunately that isn't doing the trick. Is that what you meant by path?
Yes, Michele, that is what I meant. Sorry to hear that this solution did not work for you.
Here is the fix for this problem:
You may receive the following error:
Word cannot start the converter mswrd632.wpc
This error is cause because of f the security update for Windows XP, Windows 2000, and Windows Server 2003 on December 8, 2009.
You may experience mail merge issues write files are parsed but no message is shown.
To fix this, a registry change has to be done. Although you might have tried steps from KB973904 which states
To resolve this issue, an affected user can unregister the mswrd632 converter by editing the registry as follows:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc
On the Edit menu, click Delete.
Exit Registry Editor.
This change will effectively unregister the converter and disable it for third-party applications and for Microsoft Office. Microsoft Office will use its own text converters to open these kinds of files.
You can also fix this issue with applying the registry fix, but less secure.
It worked like a charm for me. I can now export and import captions with Word with no errors.
Vernon . . .
I was having this problem as well. so thank you so much for a solution! Editing the registry worked, BUT this is really still a problem because it only fixed the problem on my own computer. Other people I'm working with who try to access these files get the same error message. And, honestly, most of them are not tech savvy enough to mess with editing their registry. Is there some way that Captivate can export to Word differently? Or can we get Microsoft to issue a new security update that fixes this?