Pages: « 1 2 3 4 5 6 7 8 9 10 »
 11 
 on: August 03, 2018, 08:21:29 AM 
Started by jpcain429 - Last post by jpcain429
Greetings,

I have XMetaL Author 12 (64-bit) installed along with the Documentum integration on a newly built Win7 64-bit machine.  After fresh installs, opening XMetaL Author 12 yields the following error which only started showing up after installing the Documentum integration:

Run-Time Error
Line 4, Column 2
Description: Automation server can't create object

Are .NET libraries required?  Below is all I see in release notes.  I have no issues on my Win10 laptop, but need to get this to work on a Win7 machine as well.

System requirements:
Microsoft Windows Vista, 7, 8, 8.1, 10 or 2008/2012 Server
Pentium 133 MHz processor
256 MB of available RAM (512 MB recommended)
Color display with a minimum resolution of 1024 x 768 or higher
Minimum 615 MB of disk space (800 MB recommended)
Additional memory may be required to generate some types of output using the DITA Open Toolkit.
Microsoft Internet Explorer 10 or newer
MSXML3.dll 8.0.7820.0 or newer (MSXML 3.0)
MSXML6.dll 6.20.5002.0 or newer (MSXML 6.0)

 12 
 on: July 12, 2018, 01:55:16 PM 
Started by smm735 - Last post by Derek Read
The order definitely does not matter. It would be useful if you were able to submit the files you are using to XMetaL Support so they can have a look and try to reproduce the issue.

 13 
 on: July 12, 2018, 11:59:33 AM 
Started by smm735 - Last post by smm735
Thanks,

We have actually resolved the issue by reordering our DTD elements. 

Previously the parent element was defined before the Table elements in our DTD.  Relocating the parent element to follow the Table elements resolved the issue.  I'm not sure why we only started seeing the issue in Xmax 11 and not in Xmax 7.  I wasn't aware that the element declaration order mattered in a DTD...

 14 
 on: July 12, 2018, 11:55:26 AM 
Started by smm735 - Last post by smm735
Thanks Derek, we are reaching out to the sales department but do you have any ideas/suggestions on what may be causing the issue?

Can you tell me what IsSpellChecker() is actually doing?  What does it look for?  I'm assuming it must be looking for something specific in the registry since the files are present on the filesystem but can you provide more details so we can see if the problematic machines are actually missing information?

Thanks,
Sean

 15 
 on: July 12, 2018, 11:09:00 AM 
Started by smm735 - Last post by Derek Read
Please contact the JustSystems sales people.

In general you need to go through them to get any XMetaL software other than the current release of XMetaL Author Enterprise which runs in trial mode by default, so it's used for evaluations (licenses are still provided by the sales team). There is no trial mode for XMAX so we do not make it readily available.

 16 
 on: July 11, 2018, 01:24:18 PM 
Started by smm735 - Last post by Derek Read
Please contact the JustSystems sales department to obtain any version of any XMetaL software. They will provide everything: EULA, download, and license file.

 17 
 on: July 11, 2018, 10:05:00 AM 
Started by smm735 - Last post by smm735
Thanks Derek,

Just curious how I would get the latest release/build of XMax?  The website seems to indicate that XMax 11 is the latest release.  We were provided with 11.0.0.084 but you mentioned using 11.0.0.091 and I'm not sure how to obtain different binaries.  The Downloads page has 2 options - both for XMetaL Author, nothing for XMax.

I see that XMetal Author is at v13 but we are not using Author - just XMax.


 18 
 on: July 11, 2018, 08:40:39 AM 
Started by smm735 - Last post by smm735
Hello,

We have just upgraded from Xmax 7 to XMax 11.0.0.084 and are using Windows 10 Enterprise workstations.

We install xmax as follows:  xmforactivex.exe" /s /v"/qn ALLUSERS=1

Following installation we see that the Writing Tools are installed in the Corel/Shared/XMetaL/Writing Tools/10 directory, however on some systems the call to IsSpellCheckerInstalled returns true and on others it returns false.

We previously installed v7 using the same logic and did not see this issue.  We have also tried running our application as Admin, however the issue does not go away

I saw other posts regarding the spellChecker not working that indicated a Windows 10 update #1803 may be causing the issue, however this update does not appear to be installed on any of the machines, either working or not working.

Can you offer any hints as to why we might be getting this inconsistent behavior?  I would try to get a newer version of XMax to test with but I'm not sure where to obtain the software - the Downloads page seems to include only XMetal Author Enterprise 13 Trial software...

Thanks,
Sean

 19 
 on: June 30, 2018, 05:23:40 AM 
Started by dduburon - Last post by Wolcott
This explains it. I just recently started using XMetaL again after a long break and I wondered the same thing. I guess I'm going to update. Cheers Derek.

 20 
 on: June 27, 2018, 02:48:52 PM 
Started by smm735 - Last post by Derek Read
My first recommendation would be to try the current release.

If this was a bug in 11.0.0.084 I think it must require a specific setup to reproduce. I am unable to reproduce the issue in 11.0.0.084, 11.0.0.091 and 13.0.0.033 (current release).

Here is my test script:

Code:
//XMetaL Script Language JScript:
Selection.InsertCALSTable(2, 2, "table", true, false);
ActiveDocument.Host.Alert(ActiveDocument.xml);

This also gives me the expected results:

Code:
//XMetaL Script Language JScript:
Selection.InsertCALSTable(2, 2, "table", true, false);
if (Selection.InContextOfType("TABLE")) {
  if (Selection.MoveToElement("table",false)) {
    Selection.SelectElement();
    ActiveDocument.Host.Alert(Selection.Text);
  }
}

As does switching to Plain Text view and viewing the XML source.
Selecting the table, copying it to the clipboard, and pasting that into a text editor also gives me the correct results.

What do you see in Plain Text view?

Presumably in your case XMAX is also giving you validation errors?
If not, does the schema define an @Desc?


I'm trying to figure out which API is causing the problem for you: ActiveDocument.xml or InsertCALSTable.
Ultimately we will need to reproduce this though.

If you can reproduce this issue with 13 please let XMetaL Support know. The issue does not appear to be reproducible with a schema that supports the standard CALS table model, so if it requires a specific DTD or XSD to reproduce the issue please provide the files needed when you submit the support case.

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