Catalog is not working in XMetal 6.0 on Windows 7, while the same setup is worki

[rakesh]

Hello Derek,

We are using XMetal 6.0 with our own customization.

Our xml contains URI in doctype which is not resolved at local system, only resolved with in the Citrix environment. For this we have build a catalog file in XMetal's with in the Rule folder.

All is working fine on Windows 10 OS but the same setup and customization is not working on Windows 7. When trying to open the xml file on Windows 7, the XMetal stops working and crashed.

Below is our doctype

Below line show the catalog setting

—
Default Catalog for Template and other files

— entries for urteil dtd —
PUBLIC “-//MBO//DTD urteil 1.0//DE” “urteil.dtd”

— entries for gesetz dtd —
PUBLIC “-//MBO//DTD gesetz 1.0//DE” “gesetz.dtd”

W3C DTDs and entity sets
—

We are really in trouble, we have licensed for XMetal 6.0 and Windows 7 but we are not able to use XMetal's Page Preview at our end.

Please suggest a work around.

Thanks & Regards
Rakesh

Reply

[Derek Read]

It seems odd that XMetaL 6 (I'm not sure which product) is running on Windows 10 without issue as that version (all products) was not tested on that operating system. All of the XMetaL version 6 products were released 5 years before Windows 10 was released. If anything I might expect the opposite of what you describe.

Please submit any files necessary to reproduce the issue to XMetaL Support together with detailed description where the files are placed, any specific configuration steps, an XML sample file, etc, so they can try to help.

Keep in mind that version 6 is not supported. It was tested on Windows XP but as Microsoft no longer supports that OS we cannot either. The first version to support Windows 7 was version 8. The first version to support Windows 8 was version 9. And the first version to support Windows 10 was version 11.

I'm not sure what any of this has to do with Page Preview, so if that is important please also include information about that in the description of the problem when you submit files to XMetaL Support.

Reply

[rakesh]

Hi Derek,

Yes XMetal 6.0 is working fine on Windows 10. I have attached a screen of “About XMetal Author Enterprise deilog” for your review.

My only concern is when I am opening a xml file (attached) that have a public URI say “', the XMetal  stops working and crashed. I am using Windows 7.

I have used catalog file (attached) to ignore doctype from xml but it is not working.

I am using the same setup of XMetal on Windows 10 with the catalog file and it is working fine. XMetal ignore the doctype.

I want to open the attached xml file into my XMetal 6.0.

Regards
Rakesh

Reply

[Derek Read]

I don't see any obvious issues with your catalog file that would trigger a crash. My guess is that something else being loaded is triggering the issue.

I do see that the XML file references a DTD on an HTTP server:

XMetaL Author will attempt to download the DTD, RLX or XAC file from that location together with any other files that XMetaL Author is able to obtain (CSS, CTM, MCR, possibly others). If XMetaL Author does find the DTD (or RLX or XAC file) it isn't going to use any entries from the catalog file. If it doesn't locate the DTD (or RLX or XAC) then it will use the entry in your catalog file to load the urteil.dtd from the same location as the catalog file, which will typically be in the Rules subfolder of the XMetaL Author installation.

Check to see that the DTD or other files do not exist at the HTTP server above if you don't want XMetaL Author to use that copy.

If you want thorough testing to be done on this, the files needed to reproduce the issue will be needed. That would include an XML sample (which you have provided here) but also the DTD, CSS, CTM, MCR, and any other files that the software is loading. Your issue could be due to the loading of the XML file itself, the DTD, any files that DTD references (entities, etc), the CSS properties interacting with the document, CTM settings or scripts, a script in the MCR file or a DLL that the MCR file references, maybe an XFT form, or perhaps some third party software the MCR or DLL code calls, possibly something else.

Please submit a support case to XMetaL Support here: https://xmetal.com/contact-support/

Note: That form does not accept file attachments. Once a case has been opened you can either send attachments via email. If email will not work for the files you need to send then XMetaL Support will let you know how to share them.

If 3rd party software is required to reproduce the issue (such as a CMS integration or some other software that modifies the XMetaL Author Enterprise installation to extend its functionality) please also let XMetaL Support know those details.

Please keep in mind that testing on version 6 cannot be done as it is an unsupported release. Testing will need to be done on a recent version. Issues are generally only corrected in the current release (right now that's 14) though exceptions are made for clients that must use a slightly older version that one of our partners requires in order to function with their software.

From the install-readme for XMetaL Author Enterprise 6 SP1 (released Jan 2010):

• Microsoft Windows XP, Vista, 7* or 2008 Server
* Windows 7 support is pending as only preliminary testing has been completed to date. Although no problems have appeared with XMetaL Author Enterprise under Windows 7, please use XMetaL Author Enterprise at your own risk.

Reply

[Author]

Posts