Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: November 03, 2017, 02:04:33 PM 
Started by vkurnovsky - Last post by Derek Read
Try generating output for the same deliverable type using File > Generate Output for DITA Topic. You should see the same issue in this case (the DITA Open Toolkit is launched the same way in both cases).

This particular error means that a portion of the application is failing to run. That might be because a file is corrupted or missing. Reinstalling the software should generally correct that. If not, please contact XMetaL Support as they will need to gather more information about your system. Windows permissions might be blocking some part of the application from running (or stopped it from installing), or an anti-virus application might be interfering, or some other 3rd party software might be involved. If generating output has never worked for you then that would probably be due to a problem installing the software in the first place, which is usually due to a lack of permissions or the software becoming corrupted during or after installation (hard drive failure, or some 3rd party software making changes to XMetaL).

 on: November 03, 2017, 09:04:26 AM 
Started by vkurnovsky - Last post by vkurnovsky
There is an error displaying when trying to load page preview in XmetaL 10: Error code: -2147024156. DitaRenditionsImpl...loadBatEngine:

Please help.

 on: November 02, 2017, 12:04:05 PM 
Started by megl - Last post by Derek Read
A dialog will display this message:

All licenses are currently in use.

 on: November 02, 2017, 10:29:15 AM 
Started by megl - Last post by megl
We are running concurrent licenses of XMetaL 10 Essentials. What is the error message that users will see if the number of licenses is exceeded?

 on: October 31, 2017, 03:05:58 PM 
Started by bholtam - Last post by tonys
You can start the TopLeaf workstation, open the partition and select Unlock from the Commands menu. If you're using the XMetaL integration you can start the workstation by pressing Launch TopLeaf from the Edit deliverable type dialog.

If you are still having problems you contact

 on: October 30, 2017, 02:16:58 PM 
Started by bholtam - Last post by bholtam
I've never had this error before, and it came up suddenly. Now I cannot build PDFs through our TopLeaf transform. Using XMetaL Author Enterprise with TopLeaf.

C:\PROGRA~3\SoftQuad\XMetaL\Shared\DITA_OT\build_topleaf.xml:136: API exec error: putdata: An API call has failed because a previous (or simultaneous) API call to the composition engine has locked the partition. (1031)

Any suggestions on how to get this fixed? I found something about unlocking an API through the command line, but I didn't have any success with it. I can generate other outputs, but nothing through the TopLeaf transform. I get the same error each time when trying with many different maps and topics.


 on: October 27, 2017, 01:25:42 PM 
Started by scott44 - Last post by Derek Read
You can't submit files directly through the support page. Submit a case, that will open the case and log it into the support system, the system will email you and you can reply anything you need to send.

 on: October 27, 2017, 12:57:51 PM 
Started by scott44 - Last post by scott44
Hello Derek,

I have excerpts from our schema and sample XML ready to send. I do not see an upload capability on the Support page.  What is the best way to submit the files?


 on: October 23, 2017, 06:32:02 PM 
Started by C4 - Last post by C4
Thanks - that works.

 on: October 23, 2017, 06:01:49 PM 
Started by C4 - Last post by mag3737
Ok, I think the answer is that before you do the RemoveContainerTags() you need to verify that after doing MoveToElement() your range/selection is actually located inside the element whose tags you want to remove. Otherwise, if it so happens that the tags of the resulting location can also be validly removed, they will be.

Try this:

var rng=ActiveDocument.Range;
rng.MoveToElement("autovalue", true);
if ((Selection.CanRemoveContainerTags) && (Selection.ContainerName == "autovalue")) {

As a side note, you might consider doing the rng.Select() after the tags are removed, instead of before. This should work just as well, with the bonus(?) effect that the cursor will not move unless some tags actually do get removed (i.e. if the code performs a no-op, the user's cursor will remain where it was):

var rng=ActiveDocument.Range;
rng.MoveToElement("autovalue", true);
if ((rng.CanRemoveContainerTags) && (rng.ContainerName == "autovalue")) {

Pages: « 1 2 3 4 5 6 7 8 9 10 »