Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Framemaker 9.0p196 crashes while exporting to xml

Guest
Aug 15, 2012 Aug 15, 2012

Copy link to clipboard

Copied

Hello,

This occurs both with XP Pro SP3 and Win7 iSP 1 . On a XP Pro SP3 without domain connection  the crash does not occur. According to the event log caused  ntdll.dll the crash.

Addendum: The XML is created correctly. this happens to all book projects, new and old. Does anyone have an idea?

Views

607
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Aug 15, 2012 Aug 15, 2012

Copy link to clipboard

Copied

You seem to have missed installing four updatte patches. Try installing those in order and see if this fixes things first.

For the updates see: http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Aug 16, 2012 Aug 16, 2012

Copy link to clipboard

Copied

Hi,

thx for your answer. After installing all four patches step by step there is no improvement.

Actualk version is now 9.0p255. Any other idea?

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Aug 16, 2012 Aug 16, 2012

Copy link to clipboard

Copied

LATEST

You could try checking your version of ntdll.dll (a Windows protected system file) for corruption using the "sfc /scannow" command. This replaces corrupted protected system files with the correct MS ones. Also, you could then check if there are any issues with the DirectX graphics (the drivers could be affecting the FM behaviourr) on your system using the DXDIAG utility.

However, as it seems to happen on two systems, the corruption doesn't seem that likely of a culprit. Are you using FM with the structure or unstructured interface, i.e. is your workflow creating the XML using the Save As XML from unstrucured files or are you exporting the XML from a structured application?

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines