Skip to main content
B
bille0906
Known Participant
March 28, 2017
Question

Framemaker crashes during save as PDF with windows 7 event log report MSVCR100.dll exception code 0xc0000417

  • March 28, 2017
  • 4 replies
  • 4563 views

I am attempting to create a PDF from several Framemaker book files. Framemaker version is 2015 (13.0.5.547). Each time I try to build the PDF, Framemaker pops up a window saying it has encountered a problem and will then abort the operation without any message to indicate where it occurred or why. Windows 7 (x64) event log consistently shows:

Faulting application is Framemaker.exe version 13.0.5.547

Faulting module name: MSVCR100.dll version 10.0.40219.325

Exception code: 0xc0000417

Faulting module path: C:\windows\system32\MSVCR100.dll

This fault is occurs consistently each time I attempt to build the PDF using File > Save As PDF, and is preventing me from doing my job.

Has anyone encountered this problem and what must be done to resolve it?

This topic has been closed for replies.

4 replies

FabianK007
FabianK007
Known Participant
May 18, 2022

Hey,

Also having "MSVCR100.dll" as faulty module while my FM publishing server tries to create PDFs, I stumbled upon your post.
The issue only occurs when FM is trying to access "AppData\Local\Temp". Changing the environment variable or clearing the folder resolved the issue.
I hope this helps anyone who may stumble upon this page as I did.

Kind regards,

Fabian

Be.eM
Be.eM
Inspiring
May 19, 2022

Fabian,

you mean changing the environment variable for the Temp folder, i.e. pointing it to a different folder solves the problem? We have this problem here with a few documents, reproducible on several FM2015 installations in Win7/64 Pro. Finding a solution would be perfect…

Bernd

FabianK007
FabianK007
Known Participant
May 20, 2022

Hi Bernd,

We found the solution because we could not reproduce the issue when operating the PC via RDC. When accessed remotely, the user uses a subfolder, in our case "\Temp\2".
We had the choice between finding what's causing the issue in Temp, or changing the environment variable, or deleting everything in Temp.
We opted to delete everything.

Regards

Fabian

Matt-Tech Comm Tools
Matt-Tech Comm Tools
Community Expert
April 6, 2017

Pardon me if this has already been suggested, but this thread is getting LONG...

Have you saved a .ps file using the Adobe PDF driver?

I occasionally need to go the .ps route with large files. Not only have I always gotten it to work (eventually), it cuts down the time to restore Fm editing capability to no more than a minute or two.

In sharp contrast, I've often been locked out of editing for hours with the Save As PDF route, even when the processing of the PDF via Distiller takes only a few minutes.

-Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant
B
bille0906Author
Known Participant
April 6, 2017

Hi Matt,

Maybe this thread is getting long because this problem is not resolved. There is no root cause, there is no workaround, thus far; there is no answer. When there is an answer to the issue, I will glve proper attribution to the person who has the correct answer and the thread can be closed.

Hope that's okay.

Bill

D
daveg42240029
Participating Frequently
April 6, 2017

Bill -

I am currently working with Adobe.  The error that EventViewer kicks out about MSVCR100.dll  is bogus.  Adobe told me that FM kicks out an error, and the error code just happens to match up with that error message. He said that FM doesn't even use that dll.

Sure enough, I temporarily rename the dll to dll_keep and rebooted.  When it started up, a few programs complained that the dll was missing, so I know nothing was seeing it.  I ran FM on my book, it died at 2.1G, and kicked out the same error about that dll.

Adobe sent me a trial FM17 to test if it has trouble converting the book.   If it works, then they will work on a fix. I'll keep you posted.

M
Community Manager
Mayank_MehCommunity Manager
Community Manager
March 31, 2017


Hi Bille0906,

I am from Adobe FrameMaker support team and would like to connect with you for the crash issue you are facing. I just sent you a private message. Kindly reply back so that we can look into the issue.

Regards,

Mayank

    B
    bille0906Author
    Known Participant
    March 31, 2017

    Hi Mayank,

    Thanks for reaching out. I am currently working with Shashank Shekhar on this issue. Are you working with him as well?

    I would gladly work with you, but do not want to discard the data collection and work that Shashank has invested in helping me to resolve this issue. Please confirm where you are coming in to this case, as a next step after Shashank, or; in parallel.

    Thanks,

    Bill Eshbach

    D
    daveg42240029
    Participating Frequently
    March 31, 2017

    Bill - I'm following alone on this.  Please share with me what you find out.  Just a FYI, guys here with Windows 10 converting the same book are just fine.   In the end, I may need to go that way.

    Thanks, Dave

    Matt-Tech Comm Tools
    Matt-Tech Comm Tools
    Community Expert
    March 28, 2017

    Hi bille0906, sorry to hear you're having trouble...

    Here's the list I put together to prevent crashes, and to speed PDF generation.

    Let me know if it solves your problem.

    FrameMaker PDF Tips and Tricks - Tech Comm Tools

    -Matt

    -Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant
      B
      bille0906Author
      Known Participant
      March 28, 2017

      Matt,

      Thanks (if for nothing else, at least commiserating with me). I checked the PDF properties and all seemed in order, except for the font business. I'll give this a try. Problem is that I have 20 folders containing books, 2 or 3 Framemaker documents, and images that are being built into one big textbook. When the build fails, I then need to turn around and remove lck files from every folder. I will try your suggestions when I go to Save As PDF, which may be tomorrow.

      D
      daveg42240029
      Participating Frequently
      March 29, 2017

      Bille -- Did you resolve this?  I'm seeing the exact same issue.  If the temp postscript hits 2.1G, it aborts with the same error. If I modify the FM file and remove a little data, and temp postscript is just over 2G and runs fine.  Seems the 2.1G is a problem, but I'm running on a 64bit machine with 8G of memory.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices