Known Participant

Question

FrameMaker 2019 crashes every time when using Edit->References

Forum|Forum|7 years ago
November 14, 2018
3 replies
1870 views

I am using Windows 7. The crash essentially prevents me from change preferences on the menu.

Error

This topic has been closed for replies.

pulkitn

Adobe Employee

This could have happened due to.Net update on your system.

Kindly uninstall .Net Framework and Framemaker from your system.

Re-install Framemaker( It will automatically install dependent .Net compatible and needed).

Further Support team will be reached to you if you need further help.

-Pulkit

-FM Engg.

Matt-Tech Comm Tools

Community Expert

It sounds like a preference file is corrupted. In your Roaming directory ( "C:\Users\{user_name}\AppData\Roaming\Adobe\FrameMaker\15"), try renaming your 15 directory to 15-old and restarting FrameMaker 2019.

-Matt

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant

anlongliAuthor

Known Participant

Renaming 15 directory to 15-old and restarting FrameMaker 2019 did not work.

Jeff_Coatsworth

Community Expert

Did you reach out to Amitoj as he requested?

Jeff_Coatsworth

Community Expert

32 or 64 bit version? All patches applied?

anlongliAuthor

Known Participant

64-bit

Windowns 7 Professional, Service Pack 1

Jeff_Coatsworth

Community Expert

Yes there are a bunch of files generated when it crashed a few minutes ago in "C:\Users\{user_name}\AppData\Roaming\Adobe\FrameMaker\15". One of the file is "FrameLog_18.11.15_08.18.03_meta" with the following content:

=== Header Begin ===

Internal Error: 15004

FrameMaker 15.0.0 for Intel

Build: 15.0.0.393

Window System: MSWindows

Operating System: Windows NT 6.1 (major.minor.build: 6.1.7601 Service Pack 1)

Generated on: Thursday, November 15, 2018 8:18:03 AM

To file: C:\Users\anlong.li\AppData\Roaming\Adobe\FrameMaker\15\FrameLog_18.11.15_08.18.03_meta.txt

Locale: English

Current Mode: Structured FrameMaker

Current View: WYSIWYG View

=== Header End ===

== Open Window List Begin ===

# not implemented

=== Open Window List End ===

=== Recent Commands Begin ===

=== Recent Commands End ===

=== Recent API Calls Begin ===

# not implemented

=== Recent API Calls End ===

=== Last few fcodes Begin ===

0x318,0x305,0x305

=== Last few fcodes End ===

Only the Adobe engineers how to make sense of the crash logs - you can fire it off to them at the fmerror e-mail mentioned in the crash message to help them gather data, but you should expect any response unless they find you've got something interesting to them. Try contacting tcssup@adobe.com about the issue.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded