Pages: 1
Print
Author Topic: Upgrade to 6.0, follow Derek's fix, all conrefs broken  (Read 2211 times)
susan_carboni
Member

Posts: 9


« on: November 11, 2011, 09:13:48 AM »

I'm using XMetaL Author Enterrprise 6.0.1. XMetaL has been extremely unstable. I followed Derek's instructions for correcting a known inssue when upgrading to 6.0. Now all the variable references (<data conref=...) are broken. I've uninstalled and reinstalled XMetal and am still seeing the same behavior. When I build a PDF file, the variables appear correctly in the PDF file. When I refresh references in the topic, however, I get this message: "The referenced element may contain content from domains that are not allowed in the referencing element."



The following is Derek's instructions that I followed to attempt to fix the stability issue...


We now know of a potential crash that may be related to the various crashes people are seeing here.

If our suspicions are correct this only affects machines that had an older version of XMetaL Author (Essential or Enterprise) on it before installing XMetaL Author Enterprise 6.0. We think that on such a machine older versions of DLLs used for spell checking were not updated by the 6.0 installer.

Removing these files manually and then forcing the 6.0 installer to restore them using "Repair" should hopefully address this problem.

1. On the machine with XMetaL Author Enterprise 6.0 installed locate the following folder and delete it: C:\Program Files\Corel\Shared\XMetaL\Writing Tools\10.0
This is the path for an English language version of Windows, if you have installed to another language version of Windows the C:\Program Files portion may differ).

2. In the Windows Control Panel launch the "Add or Remove Programs" tool.

3. From the list of installed programs select "XMetaL Author Enterprise 6.0" then click the "Change" button.

4. In the dialog that appears select the "Next" button, then select the "Repair" radio button, then click "Next", then click "Install..." and allow the installer to complete.

We have had one confirmation from a client that this addressed crashes for them as well as an inability in some cases to launch the product.
Logged
susan_carboni
Member

Posts: 9


« Reply #1 on: November 14, 2011, 10:23:56 AM »

fixed - needed to replace our ct_config file...
Logged
Pages: 1
Print
Jump to:  

email us