Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Lin Sims]

It happens on both, actually. The last 6 months or so I've been working on
my local drive because the network drive server is now remote instead of
on-site and the lag was really annoying. At least it wasn't bouncing.

On Thu, May 18, 2017 at 9:54 AM, Alan Houser  wrote:

> Just to mention a possibility ... FrameMaker is rather intolerant of
> network latency. If you are saving to any sort of networked drive (even a
> Dropbox folder), try saving to a local drive.
>
> I've had more than one client drastically reduce random FrameMaker crashes
> by moving from network to local file storage.
>
> -Alan
>
>
> On 5/18/17 7:55 AM, Lin Sims wrote:
>
>> Corporate standard (and, I think, our CMS) requires use of SVGs, partially
>> because it lets people search for text in the graphic once the PDF is
>> created. Those of us not working in DITA embed graphics because (again)
>> it's a corporate standard based on the fact that we don't share files
>> across servers/directories, so referring to them is a non-starter.
>>
>> Alison, that sounds like it's a "might work". I'll have to explore that.
>> Thanks!
>>
>> And I just realized I forgot to provide what may be a very pertinent piece
>> of info. The crash ONLY happens when I'm saving the file as part of a
>> "Save
>> all Files in Book" operation. None of the other files trigger this, and a
>> couple are even larger. One of my "workarounds" is to save the other files
>> first and then save the problem file. That will often work for a bit, but
>> it's a PITA not being able to use the book-based save all.
>>
>> 
>>
>
> --
> Alan Houser
> Group Wellesley, Inc.
> Consultant and Trainer, Technical Publishing
> arh on Twitter
> 412-450-0532
>
>
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com
> Visit the list's homepage at  http://www.frameusers.com
> Archives located at http://www.mail-archive.com/fr
> amers%40lists.frameusers.com/
> Subscribe and unsubscribe at http://lists.frameusers.com/li
> stinfo.cgi/framers-frameusers.com
> Send administrative questions to listad...@frameusers.com
>



-- 
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Alan Houser]

Just to mention a possibility ... FrameMaker is rather intolerant of 
network latency. If you are saving to any sort of networked drive (even 
a Dropbox folder), try saving to a local drive.


I've had more than one client drastically reduce random FrameMaker 
crashes by moving from network to local file storage.


-Alan


On 5/18/17 7:55 AM, Lin Sims wrote:

Corporate standard (and, I think, our CMS) requires use of SVGs, partially
because it lets people search for text in the graphic once the PDF is
created. Those of us not working in DITA embed graphics because (again)
it's a corporate standard based on the fact that we don't share files
across servers/directories, so referring to them is a non-starter.

Alison, that sounds like it's a "might work". I'll have to explore that.
Thanks!

And I just realized I forgot to provide what may be a very pertinent piece
of info. The crash ONLY happens when I'm saving the file as part of a "Save
all Files in Book" operation. None of the other files trigger this, and a
couple are even larger. One of my "workarounds" is to save the other files
first and then save the problem file. That will often work for a bit, but
it's a PITA not being able to use the book-based save all.




--
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532

___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Lin Sims]

Corporate standard (and, I think, our CMS) requires use of SVGs, partially
because it lets people search for text in the graphic once the PDF is
created. Those of us not working in DITA embed graphics because (again)
it's a corporate standard based on the fact that we don't share files
across servers/directories, so referring to them is a non-starter.

Alison, that sounds like it's a "might work". I'll have to explore that.
Thanks!

And I just realized I forgot to provide what may be a very pertinent piece
of info. The crash ONLY happens when I'm saving the file as part of a "Save
all Files in Book" operation. None of the other files trigger this, and a
couple are even larger. One of my "workarounds" is to save the other files
first and then save the problem file. That will often work for a bit, but
it's a PITA not being able to use the book-based save all.

On Wed, May 17, 2017 at 5:32 PM, Craig, Alison <acr...@bkultrasound.com>
wrote:

> Instead of simply removing the 18 files, save just the current FM file
> under another name then remove everything from the new file except the
> images.
>
> Then remove them from your working file.
>
> That way, the images will maintain their Conditions and you *should* just
> be able to copy each one back in to its repsective place, without any
> hassle (any *further* hassle?).
>
> FYI: I used to save Visio files to PDFs but now I save them to WMF.
> Neither format has ever caused any problems.
>
> Alison Craig
> Technical Documentation Specialist
> BK Ultrasound | acr...@bkultrasound.com
>
> From: Framers [mailto:framers-bounces+acraig=bkultrasound.com@lists.
> frameusers.com] On Behalf Of Lin Sims
> Sent: Wednesday, May 17, 2017 2:02 PM
> To: An email list for people using Adobe FrameMaker software.
> Subject: Re: [Framers] Crash with Internal Errors: 13054, 21985197,
> 21967009, 21686210
>
> Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the
> same habit of adding colors to the catalog with them, too. Not sure if the
> rename (of only Black!) has any bearing, but it struck me as odd so I
> mentioned it.
>
> Robert: Not sure if removing the graphics would help, since the crashes are
> intermittent and I sort of need them to refer to while working. :(
>
> I was thinking of maybe removing them until I have to create a review or
> release, but the idea taking out and putting back in 18 figures (with an
> assortment of conditions) is making me cringe.
>
> On the other hand, that might be the only recourse. Sometimes I miss FM8.
> 
>
> On Wed, May 17, 2017 at 3:49 PM, Robert Lauriston <rob...@lauriston.com
> ><mailto:rob...@lauriston.com%3e>
> wrote:
>
> > What if you temporarily remove the 18 embedded figures?
> >
> > On Wed, May 17, 2017 at 11:51 AM, Lin Sims <ljsims...@gmail.com> ljsims...@gmail.com%3e> wrote:
> > > Anyone know what these errors refer to? I have a file that frequently
> > > crashes Frame, and this was the latest series of internal errors it
> gave
> > me.
> > >
> > > I did do a MIF wash and noticed one odd thing: Frame has renamed the
> > color
> > > Black to fm_gen_## when I save to the MIF file. If I edit those
> > > definitions back to Black in the MIF file and resave as Frame, the
> > > definitions stay the same in the MIF file, but Frame once more renames
> > the
> > > color to fm_gen_## (different numbers this time). It also renames
> the
> > > color in one (but only one) of the condition tags it's used in.
> > >
> > > The file is a large one (18.4 Mb) and has 18 figures embedded in it
> (not
> > my
> > > choice, but there is no choice), several of which are affected by
> > > conditions, 16 tables, conditions galore (18), and loads of
> > > cross-references. It's been giving me fits for several months now, to
> the
> > > point where I literally created a new Frame file and copied and pasted
> > all
> > > the text as plain text and reformatted it, and reimported all the
> > graphics.
> > > It behaved for about 2 months and is now crashing all over again.
> > >
> > > I expect to be working with this set of files daily for the next 6
> months
> > > at least. I cannot afford to lose the time it takes to crash, recover,
> > > mif-wash, etc., etc., etc., that this is taking up.
> > >
> > > Suggestions gratefully (and exhaustedly) received.
> > >
> > > Pertinents:
> > >
> > > Windows 7, all patches applied
> > > FrameMaker 2015, latest patches applied
> > > Plugins: AutoText, TableCleaner (DLL, not sc

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Craig, Alison]

Instead of simply removing the 18 files, save just the current FM file under 
another name then remove everything from the new file except the images.

Then remove them from your working file.

That way, the images will maintain their Conditions and you *should* just be 
able to copy each one back in to its repsective place, without any hassle (any 
*further* hassle?).

FYI: I used to save Visio files to PDFs but now I save them to WMF. Neither 
format has ever caused any problems.

Alison Craig
Technical Documentation Specialist
BK Ultrasound | acr...@bkultrasound.com

From: Framers 
[mailto:framers-bounces+acraig=bkultrasound@lists.frameusers.com] On Behalf 
Of Lin Sims
Sent: Wednesday, May 17, 2017 2:02 PM
To: An email list for people using Adobe FrameMaker software.
Subject: Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 
21686210

Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the
same habit of adding colors to the catalog with them, too. Not sure if the
rename (of only Black!) has any bearing, but it struck me as odd so I
mentioned it.

Robert: Not sure if removing the graphics would help, since the crashes are
intermittent and I sort of need them to refer to while working. :(

I was thinking of maybe removing them until I have to create a review or
release, but the idea taking out and putting back in 18 figures (with an
assortment of conditions) is making me cringe.

On the other hand, that might be the only recourse. Sometimes I miss FM8.


On Wed, May 17, 2017 at 3:49 PM, Robert Lauriston 
<rob...@lauriston.com><mailto:rob...@lauriston.com%3e>
wrote:

> What if you temporarily remove the 18 embedded figures?
>
> On Wed, May 17, 2017 at 11:51 AM, Lin Sims 
> <ljsims...@gmail.com><mailto:ljsims...@gmail.com%3e> wrote:
> > Anyone know what these errors refer to? I have a file that frequently
> > crashes Frame, and this was the latest series of internal errors it gave
> me.
> >
> > I did do a MIF wash and noticed one odd thing: Frame has renamed the
> color
> > Black to fm_gen_## when I save to the MIF file. If I edit those
> > definitions back to Black in the MIF file and resave as Frame, the
> > definitions stay the same in the MIF file, but Frame once more renames
> the
> > color to fm_gen_## (different numbers this time). It also renames the
> > color in one (but only one) of the condition tags it's used in.
> >
> > The file is a large one (18.4 Mb) and has 18 figures embedded in it (not
> my
> > choice, but there is no choice), several of which are affected by
> > conditions, 16 tables, conditions galore (18), and loads of
> > cross-references. It's been giving me fits for several months now, to the
> > point where I literally created a new Frame file and copied and pasted
> all
> > the text as plain text and reformatted it, and reimported all the
> graphics.
> > It behaved for about 2 months and is now crashing all over again.
> >
> > I expect to be working with this set of files daily for the next 6 months
> > at least. I cannot afford to lose the time it takes to crash, recover,
> > mif-wash, etc., etc., etc., that this is taking up.
> >
> > Suggestions gratefully (and exhaustedly) received.
> >
> > Pertinents:
> >
> > Windows 7, all patches applied
> > FrameMaker 2015, latest patches applied
> > Plugins: AutoText, TableCleaner (DLL, not script)
> > 2 home-brewed scripts: save all files in book to selected MIF formats;
> add
> > Table Continuation variable to all tables in a file
> >
> ___
>
> This message is from the Framers mailing list
>
> Send messages to 
> framers@lists.frameusers.com<mailto:framers@lists.frameusers.com>
> Visit the list's homepage at http://www.frameusers.com
> Archives located at http://www.mail-archive.com/
> framers%40lists.frameusers.com/
> Subscribe and unsubscribe at http://lists.frameusers.com/
> listinfo.cgi/framers-frameusers.com
> Send administrative questions to 
> listad...@frameusers.com<mailto:listad...@frameusers.com>
>



--
Lin Sims
___

This message is from the Framers mailing list

Send messages to 
framers@lists.frameusers.com<mailto:framers@lists.frameusers.com>
Visit the list's homepage at http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to 
listad...@frameusers.com<mailto:listad...@frameusers.com>


___

This message is from the Framers mail

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Robert Lauriston]

Rather than deleting the figures you could just substitute
placeholders long enough to determine whether those are the problem.
You can't refer to the SVGs in some other program?

I had various problems with Visio graphics which all went away when I
started placing them as EMFs.

On Wed, May 17, 2017 at 2:02 PM, Lin Sims  wrote:
> Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the
> same habit of adding colors to the catalog with them, too. Not sure if the
> rename (of only Black!) has any bearing, but it struck me as odd so I
> mentioned it.
>
> Robert: Not sure if removing the graphics would help, since the crashes are
> intermittent and I sort of need them to refer to while working. :(
>
> I was thinking of maybe removing them until I have to create a review or
> release, but the idea taking out and putting back in 18 figures (with an
> assortment of conditions) is making me cringe.
>
> On the other hand, that might be the only recourse. Sometimes I miss FM8.
> 
>
> On Wed, May 17, 2017 at 3:49 PM, Robert Lauriston 
> wrote:
>
>> What if you temporarily remove the 18 embedded figures?
>>
>> On Wed, May 17, 2017 at 11:51 AM, Lin Sims  wrote:
>> > Anyone know what these errors refer to? I have a file that frequently
>> > crashes Frame, and this was the latest series of internal errors it gave
>> me.
>> >
>> > I did do a MIF wash and noticed one odd thing: Frame has renamed the
>> color
>> > Black to fm_gen_## when I save to the MIF file. If I  edit those
>> > definitions back to Black in the MIF file and resave as Frame, the
>> > definitions stay the same in the MIF file, but Frame once more renames
>> the
>> > color to fm_gen_## (different numbers this time). It also renames the
>> > color in one (but only one) of the condition tags it's used in.
>> >
>> > The file is a large one (18.4 Mb) and has 18 figures embedded in it (not
>> my
>> > choice, but there is no choice), several of which are affected by
>> > conditions, 16 tables, conditions galore (18), and loads of
>> > cross-references. It's been giving me fits for several months now, to the
>> > point where I literally created a new Frame file and copied and pasted
>> all
>> > the text as plain text and reformatted it, and reimported all the
>> graphics.
>> > It behaved for about 2 months and is now crashing all over again.
>> >
>> > I expect to be working with this set of files daily for the next 6 months
>> > at least. I cannot afford to lose the time it takes to crash, recover,
>> > mif-wash, etc., etc., etc., that this is taking up.
>> >
>> > Suggestions gratefully (and exhaustedly) received.
>> >
>> > Pertinents:
>> >
>> > Windows 7, all patches applied
>> > FrameMaker 2015, latest patches applied
>> > Plugins: AutoText, TableCleaner (DLL, not script)
>> > 2 home-brewed scripts: save all files in book to selected MIF formats;
>> add
>> > Table Continuation variable to all tables in a file
>> >
>> ___
>>
>> This message is from the Framers mailing list
>>
>> Send messages to framers@lists.frameusers.com
>> Visit the list's homepage at  http://www.frameusers.com
>> Archives located at http://www.mail-archive.com/
>> framers%40lists.frameusers.com/
>> Subscribe and unsubscribe at http://lists.frameusers.com/
>> listinfo.cgi/framers-frameusers.com
>> Send administrative questions to listad...@frameusers.com
>>
>
>
>
> --
> Lin Sims
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com
> Visit the list's homepage at  http://www.frameusers.com
> Archives located at 
> http://www.mail-archive.com/framers%40lists.frameusers.com/
> Subscribe and unsubscribe at 
> http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
> Send administrative questions to listad...@frameusers.com
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Lin Sims]

Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the
same habit of adding colors to the catalog with them, too. Not sure if the
rename (of only Black!) has any bearing, but it struck me as odd so I
mentioned it.

Robert: Not sure if removing the graphics would help, since the crashes are
intermittent and I sort of need them to refer to while working. :(

I was thinking of maybe removing them until I have to create a review or
release, but the idea taking out and putting back in 18 figures (with an
assortment of conditions) is making me cringe.

On the other hand, that might be the only recourse. Sometimes I miss FM8.


On Wed, May 17, 2017 at 3:49 PM, Robert Lauriston 
wrote:

> What if you temporarily remove the 18 embedded figures?
>
> On Wed, May 17, 2017 at 11:51 AM, Lin Sims  wrote:
> > Anyone know what these errors refer to? I have a file that frequently
> > crashes Frame, and this was the latest series of internal errors it gave
> me.
> >
> > I did do a MIF wash and noticed one odd thing: Frame has renamed the
> color
> > Black to fm_gen_## when I save to the MIF file. If I  edit those
> > definitions back to Black in the MIF file and resave as Frame, the
> > definitions stay the same in the MIF file, but Frame once more renames
> the
> > color to fm_gen_## (different numbers this time). It also renames the
> > color in one (but only one) of the condition tags it's used in.
> >
> > The file is a large one (18.4 Mb) and has 18 figures embedded in it (not
> my
> > choice, but there is no choice), several of which are affected by
> > conditions, 16 tables, conditions galore (18), and loads of
> > cross-references. It's been giving me fits for several months now, to the
> > point where I literally created a new Frame file and copied and pasted
> all
> > the text as plain text and reformatted it, and reimported all the
> graphics.
> > It behaved for about 2 months and is now crashing all over again.
> >
> > I expect to be working with this set of files daily for the next 6 months
> > at least. I cannot afford to lose the time it takes to crash, recover,
> > mif-wash, etc., etc., etc., that this is taking up.
> >
> > Suggestions gratefully (and exhaustedly) received.
> >
> > Pertinents:
> >
> > Windows 7, all patches applied
> > FrameMaker 2015, latest patches applied
> > Plugins: AutoText, TableCleaner (DLL, not script)
> > 2 home-brewed scripts: save all files in book to selected MIF formats;
> add
> > Table Continuation variable to all tables in a file
> >
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com
> Visit the list's homepage at  http://www.frameusers.com
> Archives located at http://www.mail-archive.com/
> framers%40lists.frameusers.com/
> Subscribe and unsubscribe at http://lists.frameusers.com/
> listinfo.cgi/framers-frameusers.com
> Send administrative questions to listad...@frameusers.com
>



-- 
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Robert Lauriston]

What if you temporarily remove the 18 embedded figures?

On Wed, May 17, 2017 at 11:51 AM, Lin Sims  wrote:
> Anyone know what these errors refer to? I have a file that frequently
> crashes Frame, and this was the latest series of internal errors it gave me.
>
> I did do a MIF wash and noticed one odd thing: Frame has renamed the color
> Black to fm_gen_## when I save to the MIF file. If I  edit those
> definitions back to Black in the MIF file and resave as Frame, the
> definitions stay the same in the MIF file, but Frame once more renames the
> color to fm_gen_## (different numbers this time). It also renames the
> color in one (but only one) of the condition tags it's used in.
>
> The file is a large one (18.4 Mb) and has 18 figures embedded in it (not my
> choice, but there is no choice), several of which are affected by
> conditions, 16 tables, conditions galore (18), and loads of
> cross-references. It's been giving me fits for several months now, to the
> point where I literally created a new Frame file and copied and pasted all
> the text as plain text and reformatted it, and reimported all the graphics.
> It behaved for about 2 months and is now crashing all over again.
>
> I expect to be working with this set of files daily for the next 6 months
> at least. I cannot afford to lose the time it takes to crash, recover,
> mif-wash, etc., etc., etc., that this is taking up.
>
> Suggestions gratefully (and exhaustedly) received.
>
> Pertinents:
>
> Windows 7, all patches applied
> FrameMaker 2015, latest patches applied
> Plugins: AutoText, TableCleaner (DLL, not script)
> 2 home-brewed scripts: save all files in book to selected MIF formats; add
> Table Continuation variable to all tables in a file
>
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Bernard Aschwanden (Publishing Smarter)]

Do you have PNG files in the doc? I find that SOME of them (not all, that
would be almost too easy) get scanned by FM and the colors added to the
catalog.

I hate PNG for that reason. Is it justified hate? Maybe not. However, it's
hate regardless.

Sometimes I just save files as PNG so that I can bulk Shift+Delete them on
my computer.

Bernard



-Original Message-
From: Framers
[mailto:framers-bounces+bernard=publishingsmarter@lists.frameusers.com]
On Behalf Of Lin Sims
Sent: Wednesday, May 17, 2017 2:52 PM
To: Frame Users
Subject: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009,
21686210

Anyone know what these errors refer to? I have a file that frequently
crashes Frame, and this was the latest series of internal errors it gave me.

I did do a MIF wash and noticed one odd thing: Frame has renamed the color
Black to fm_gen_## when I save to the MIF file. If I  edit those
definitions back to Black in the MIF file and resave as Frame, the
definitions stay the same in the MIF file, but Frame once more renames the
color to fm_gen_## (different numbers this time). It also renames the
color in one (but only one) of the condition tags it's used in.

The file is a large one (18.4 Mb) and has 18 figures embedded in it (not my
choice, but there is no choice), several of which are affected by
conditions, 16 tables, conditions galore (18), and loads of
cross-references. It's been giving me fits for several months now, to the
point where I literally created a new Frame file and copied and pasted all
the text as plain text and reformatted it, and reimported all the graphics.
It behaved for about 2 months and is now crashing all over again.

I expect to be working with this set of files daily for the next 6 months at
least. I cannot afford to lose the time it takes to crash, recover,
mif-wash, etc., etc., etc., that this is taking up.

Suggestions gratefully (and exhaustedly) received.

Pertinents:

Windows 7, all patches applied
FrameMaker 2015, latest patches applied
Plugins: AutoText, TableCleaner (DLL, not script)
2 home-brewed scripts: save all files in book to selected MIF formats; add
Table Continuation variable to all tables in a file


--
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com Visit the list's homepage at
http://www.frameusers.com Archives located at
http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Peter Gold]

As far back as I can remember, the lore was that those error numbers only
had meaning to whomever created the message. There were no specific fixes.

My old troubleshooting mind remembers when tweaking some resource settings
in early Windows releases sometimes helped fix application problems. I
don't know if Windows 7 offers any such options.

Also, although it's an FM error, perhaps there's a Windows system failure
log message that could offer some information about the cause.

If you haven't tried uninstalling and selectively reinstalling plug-ins
one-by-one, it might be worth a try.

HTH


On Wed, May 17, 2017 at 1:51 PM, Lin Sims  wrote:

> Anyone know what these errors refer to? I have a file that frequently
> crashes Frame, and this was the latest series of internal errors it gave
> me.
>
> I did do a MIF wash and noticed one odd thing: Frame has renamed the color
> Black to fm_gen_## when I save to the MIF file. If I  edit those
> definitions back to Black in the MIF file and resave as Frame, the
> definitions stay the same in the MIF file, but Frame once more renames the
> color to fm_gen_## (different numbers this time). It also renames the
> color in one (but only one) of the condition tags it's used in.
>
> The file is a large one (18.4 Mb) and has 18 figures embedded in it (not my
> choice, but there is no choice), several of which are affected by
> conditions, 16 tables, conditions galore (18), and loads of
> cross-references. It's been giving me fits for several months now, to the
> point where I literally created a new Frame file and copied and pasted all
> the text as plain text and reformatted it, and reimported all the graphics.
> It behaved for about 2 months and is now crashing all over again.
>
> I expect to be working with this set of files daily for the next 6 months
> at least. I cannot afford to lose the time it takes to crash, recover,
> mif-wash, etc., etc., etc., that this is taking up.
>
> Suggestions gratefully (and exhaustedly) received.
>
> Pertinents:
>
> Windows 7, all patches applied
> FrameMaker 2015, latest patches applied
> Plugins: AutoText, TableCleaner (DLL, not script)
> 2 home-brewed scripts: save all files in book to selected MIF formats; add
> Table Continuation variable to all tables in a file
>
>
> --
> Lin Sims
> ___
>
> This message is from the Framers mailing list
>
> Send messages to framers@lists.frameusers.com
> Visit the list's homepage at  http://www.frameusers.com
> Archives located at http://www.mail-archive.com/
> framers%40lists.frameusers.com/
> Subscribe and unsubscribe at http://lists.frameusers.com/
> listinfo.cgi/framers-frameusers.com
> Send administrative questions to listad...@frameusers.com
>
>
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Lin Sims]

Other fun stats:

I have 104 crash log files since last July
I had 14 crashes in 1 day this February
So far today, I've had 3 crashes

Seriously, this is getting OLD. And my nearby coworkers are gaining new
"respect" for my ability to curse and swear.

On Wed, May 17, 2017 at 2:51 PM, Lin Sims  wrote:

> Anyone know what these errors refer to? I have a file that frequently
> crashes Frame, and this was the latest series of internal errors it gave me.
>
> I did do a MIF wash and noticed one odd thing: Frame has renamed the color
> Black to fm_gen_## when I save to the MIF file. If I  edit those
> definitions back to Black in the MIF file and resave as Frame, the
> definitions stay the same in the MIF file, but Frame once more renames the
> color to fm_gen_## (different numbers this time). It also renames the
> color in one (but only one) of the condition tags it's used in.
>
> The file is a large one (18.4 Mb) and has 18 figures embedded in it (not
> my choice, but there is no choice), several of which are affected by
> conditions, 16 tables, conditions galore (18), and loads of
> cross-references. It's been giving me fits for several months now, to the
> point where I literally created a new Frame file and copied and pasted all
> the text as plain text and reformatted it, and reimported all the graphics.
> It behaved for about 2 months and is now crashing all over again.
>
> I expect to be working with this set of files daily for the next 6 months
> at least. I cannot afford to lose the time it takes to crash, recover,
> mif-wash, etc., etc., etc., that this is taking up.
>
> Suggestions gratefully (and exhaustedly) received.
>
> Pertinents:
>
> Windows 7, all patches applied
> FrameMaker 2015, latest patches applied
> Plugins: AutoText, TableCleaner (DLL, not script)
> 2 home-brewed scripts: save all files in book to selected MIF formats; add
> Table Continuation variable to all tables in a file
>
>
> --
> Lin Sims
>



-- 
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

[Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[Lin Sims]

Anyone know what these errors refer to? I have a file that frequently
crashes Frame, and this was the latest series of internal errors it gave me.

I did do a MIF wash and noticed one odd thing: Frame has renamed the color
Black to fm_gen_## when I save to the MIF file. If I  edit those
definitions back to Black in the MIF file and resave as Frame, the
definitions stay the same in the MIF file, but Frame once more renames the
color to fm_gen_## (different numbers this time). It also renames the
color in one (but only one) of the condition tags it's used in.

The file is a large one (18.4 Mb) and has 18 figures embedded in it (not my
choice, but there is no choice), several of which are affected by
conditions, 16 tables, conditions galore (18), and loads of
cross-references. It's been giving me fits for several months now, to the
point where I literally created a new Frame file and copied and pasted all
the text as plain text and reformatted it, and reimported all the graphics.
It behaved for about 2 months and is now crashing all over again.

I expect to be working with this set of files daily for the next 6 months
at least. I cannot afford to lose the time it takes to crash, recover,
mif-wash, etc., etc., etc., that this is taking up.

Suggestions gratefully (and exhaustedly) received.

Pertinents:

Windows 7, all patches applied
FrameMaker 2015, latest patches applied
Plugins: AutoText, TableCleaner (DLL, not script)
2 home-brewed scripts: save all files in book to selected MIF formats; add
Table Continuation variable to all tables in a file


-- 
Lin Sims
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com