Skip to main content
Participating Frequently
February 5, 2020
Question

Error 15044

  • February 5, 2020
  • 4 replies
  • 1056 views

I frequently keep getting error '15044 - FrameMaker encountered a serious error'.  Adobe Tech Team took my app log by e-mail but couldn't ascertain the reason for the error.  This error appears randomly, not specifically after any action, and closes FrameMaker and all my unsaved work is lost.  Previously a file was corrupted and I could not open or retrieve any data from the file. Appreciate any info on how to avoid this.

This topic has been closed for replies.

4 replies

pulkitn
Adobe Employee
Adobe Employee
February 14, 2020

Hi Jospeph ,

As per you .dmp file , I would recommend you to update the FrameMaker by Help-->Update .

If you face any issue while updating then you can contact TCS support at (tcssup@adobe.com)

 

-Pulkit

Jeff_Coatsworth
Community Expert
Community Expert
February 6, 2020

Now that you have a lead on what's causing it, I'd log a bug in the Tracker and describe what causes it and give them your error logs and the graphic that can trip the error.

Participating Frequently
February 13, 2020

Thanks, I'm not sure how to log a bug in the Tracker. Last time I raised a ticket contacting customer service. Is there a link for the Bug Tracker?

Community Expert
February 13, 2020

Hi,

 

In the Adobe Tracker you can log bugs or suggest new features.

Just open this website and describe your issue: https://tracker.adobe.com/#/home 

When you are not logged in automatically, log in with your Adobe ID.

 

Best regards

 

Winfried

Participating Frequently
February 6, 2020

I just realised today that when I import a large image and use Object Catalog to resize it, this error occurs. I am not sure to whom this information will be helpful. I will save the file before I do this action next time.

Jeff_Coatsworth
Community Expert
Community Expert
February 5, 2020

Since no one has found what's causing it yet, I'd just take steps to mitigate it - run as Admin, save frequently, keep patched up, maybe MIF-wash your files, and see if there's some common set of actions that seem to bring it on.