FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-25 Thread Brian Weis
Hello, Dov.

I did not expect a personal response from Adobe. And I decided against going
through their Tech Support until I absolutely had to. That decision is based
on past experience with their version of Support.

And thank you for your comments regarding copy/paste. Your point is well
made.

--
Brian


--
From: Dov Isaacs <isa...@adobe.com>
Date: Fri, Jun 20, 2008 at 4:41 PM
Subject: RE: FrameMaker Internal Error -- Visio and "...lost image data"
To: Brian Weis , "framers at frameusers.com" <
framers at frameusers.com>


For better or worse, if you simply mailed in the report to Adobe,
don't expect a personal if any response. That mechanism is not
Adobe Tech Support.

For future reference, regardless of what program you publish with
copy-and-paste is about the worst way to set yourself up for disaster
in case your document get lost or mangled.

   - Dov


> -Original Message-
> From: Brian Weis
> Sent: Friday, June 20, 2008 7:36 AM
>
> Hi folks:
>
> Yesterday, I encountered this error in FM:  "An internal error occurred
> while writing imported graphics in this document. The file has been saved,
> but has lost some image data. Please report this error to Adobe Technical
> Support."
>
>
> I close the error dialog, and then try to close the file ... but I am
> prompted once again to save it before closing. I am now in a loop until I
> break the cycle by clicking "No" in the save prompt. Contrary to the error
> message's statement that the file has been saved, I find that none of my
> changes, text or otherwise, are in the file. With a little more work, I am
> able to determine that a Visio object must be the culprit.
>
> How do I know this?
>
> In the directory where my source Frame doc is located, I see a set of
> "garbage" files -- that is, files that my system does not recognize by
> filename extension. I recognize them as copies of my source doc ... but
with
> different extensions (e.g., .BE7, .75F). These files have date/time stamps
> right around the time I was trying to save my changes. Right clicking on
one
> of these files, and specifying FrameMaker to open it, I find a version of
my
> document with the most recent set of changes ... but the Visio object is
now
> grayed out in its inline frame.
>
> Just to be clear, I am using "Visio object" to refer to an graphic that I
> have inserted by copying the elements from the original Visio drawing and
> then pasting them into an inline frame in FrameMaker. I did not use the
> "Import File" option.
>
> I did some more testing with a copy of my now-recovered source document.
> While playing with different ways to insert/paste the Visio work, and
> accessing Visio work in other documents by right-clicking them and
selecting
> "Visio Object" from the pop-up menu, Framemaker eventually "detected a
> serious problem" and had to quit. This error dialog called out a FrameLog
> file (an error log) and instructed me to send the file and a description
of
> what I did to fmerror at adobe.com.
>
>
> I have been using the paste method with Visio objects successfully for
> almost two years. I realize it is not recommended, but I have never had an
> issue until now. And it looks like my previous documents that have one or
> more Visio objects inserted in this fashion will suffer the same problem.
At
> least, all such files I have tested exhibit the same problem -- even just
> opening a file that has a Visio object will subject it to this problem.
>
> I sent all the info and the error messages (a longer summary than I've
> posted here) to Adobe around 6pm last night. I have not heard from them,
and
> I probably should not expect to. I have searched Adobe Support for info on
> Visio, "Internal Error 7204", and other things, but have not found
anything
> helpful. So I come to you in the Frame using community. Has anyone here
> copy/paste Visio into Frame? Have you ever come across this problem? Do
you
> know a solution?
>
> Thanks in advance.
>
> --
> Brian Weis


FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Brian Weis
Hi folks:

Yesterday, I encountered this error in FM:  An internal error occurred
while writing imported graphics in this document. The file has been saved,
but has lost some image data. Please report this error to Adobe Technical
Support.


I close the error dialog, and then try to close the file ... but I am
prompted once again to save it before closing. I am now in a loop until I
break the cycle by clicking No in the save prompt. Contrary to the error
message's statement that the file has been saved, I find that none of my
changes, text or otherwise, are in the file. With a little more work, I am
able to determine that a Visio object must be the culprit.

How do I know this?

In the directory where my source Frame doc is located, I see a set of
garbage files -- that is, files that my system does not recognize by
filename extension. I recognize them as copies of my source doc ... but with
different extensions (e.g., .BE7, .75F). These files have date/time stamps
right around the time I was trying to save my changes. Right clicking on one
of these files, and specifying FrameMaker to open it, I find a version of my
document with the most recent set of changes ... but the Visio object is now
grayed out in its inline frame.

Just to be clear, I am using Visio object to refer to an graphic that I
have inserted by copying the elements from the original Visio drawing and
then pasting them into an inline frame in FrameMaker. I did not use the
Import File option.

I did some more testing with a copy of my now-recovered source document.
While playing with different ways to insert/paste the Visio work, and
accessing Visio work in other documents by right-clicking them and selecting
Visio Object from the pop-up menu, Framemaker eventually detected a
serious problem and had to quit. This error dialog called out a FrameLog
file (an error log) and instructed me to send the file and a description of
what I did to [EMAIL PROTECTED]


I have been using the paste method with Visio objects successfully for
almost two years. I realize it is not recommended, but I have never had an
issue until now. And it looks like my previous documents that have one or
more Visio objects inserted in this fashion will suffer the same problem. At
least, all such files I have tested exhibit the same problem -- even just
opening a file that has a Visio object will subject it to this problem.

I sent all the info and the error messages (a longer summary than I've
posted here) to Adobe around 6pm last night. I have not heard from them, and
I probably should not expect to. I have searched Adobe Support for info on
Visio, Internal Error 7204, and other things, but have not found anything
helpful. So I come to you in the Frame using community. Has anyone here
copy/paste Visio into Frame? Have you ever come across this problem? Do you
know a solution?

Thanks in advance.

--
Brian Weis
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Art Campbell
If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

Or you can convert the Visio objects to PDF, PNG, or other graphic
files and import them by reference.

May want to nag Microsoft some, if you think that would have an effect. ;- )

Of course, if you're not using XP and haven't installed SP3, something
else is at work, but I didn't see any system or FM version details in
your post. Which would be important in solving the problem if it is
something else.

Art

On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis [EMAIL PROTECTED] wrote:
 Yesterday, I encountered this error in FM:  An internal error occurred
 while writing imported graphics in this document. The file has been saved,
 but has lost some image data. Please report this error to Adobe Technical
 Support.


 I close the error dialog, and then try to close the file ... but I am
 prompted once again to save it before closing. I am now in a loop until I
 break the cycle by clicking No in the save prompt. Contrary to the error
 message's statement that the file has been saved, I find that none of my
 changes, text or otherwise, are in the file. With a little more work, I am
 able to determine that a Visio object must be the culprit.


-- 
Art Campbell [EMAIL PROTECTED]
 ... In my opinion, there's nothing in this world beats a '52 Vincent
and a redheaded girl. -- Richard Thompson
 No disclaimers apply.
 DoD 358
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Rene Stephenson
OK, so to tie in with another thread: if you go with a PC so you can run FM 
current version in native OS, stick with XP SP2...? Gotcha.

 
Rene L. Stephenson



- Original Message 
From: Art Campbell [EMAIL PROTECTED]

If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

...Art
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Lise Bible
I had similar error messages with Frame files with OLE links to Excel
spreadsheets, but mostly randomly--sometimes I had the Excel file open by
mistake, and that might have triggered it, I'm not sure. I could never find
the exact cause. Was running Frame 7.1 on XP, SP2.

A colleague told me she got those errors all the time (same OLE links to
Excel files). She's going to be upgrading to Frame 8, but she's getting a
new computer as well, so there are too many variables there to narrow down
one cause if it ends up fixing her problem.

Have upgraded to Frame 8, still XP, SP2. Haven't had it that long, but I
haven't had any error messages so far. Doesn't mean that the upgrade fixed
the problem, though.

Using PDF's or graphics isn't a good fix for me, because we're linking to
parts lists that appear in the product manual and a separate parts book for
the entire product line. The advantage of OLE links to the Excel files is
that it's always linked to the latest and greatest version.

So thanks for the heads-up about SP3. I don't know if our IS dept. will be
rolling that out soon or not. Fortunately, I don't believe there are any
imminent plans to upgrade us to Vista.

-Lise

On Fri, Jun 20, 2008 at 10:16 AM, Art Campbell [EMAIL PROTECTED]
wrote:

 If you search back through the archives and/or visit the Frame user's
 forum on Adobe.com, you'll see that this has been a pretty common
 topic since Microsoft released SP3 for XP. They included some security
 fixes to OLE that have effectively broken it, at least as far as
 managing objects in Frame go.

 Only reported fix is backing out of SP3.

 Or you can convert the Visio objects to PDF, PNG, or other graphic
 files and import them by reference.

 May want to nag Microsoft some, if you think that would have an effect. ;-
 )

 Of course, if you're not using XP and haven't installed SP3, something
 else is at work, but I didn't see any system or FM version details in
 your post. Which would be important in solving the problem if it is
 something else.

 Art

 On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis [EMAIL PROTECTED]
 wrote:
  Yesterday, I encountered this error in FM:  An internal error occurred
  while writing imported graphics in this document. The file has been
 saved,
  but has lost some image data. Please report this error to Adobe Technical
  Support.
 
 
  I close the error dialog, and then try to close the file ... but I am
  prompted once again to save it before closing. I am now in a loop until I
  break the cycle by clicking No in the save prompt. Contrary to the
 error
  message's statement that the file has been saved, I find that none of my
  changes, text or otherwise, are in the file. With a little more work, I
 am
  able to determine that a Visio object must be the culprit.
 

 --
 Art Campbell [EMAIL PROTECTED]
  ... In my opinion, there's nothing in this world beats a '52 Vincent
 and a redheaded girl. -- Richard Thompson
  No disclaimers apply.
  DoD 358
 ___


 You are currently subscribed to Framers as [EMAIL PROTECTED]

 Send list messages to [EMAIL PROTECTED]

 To unsubscribe send a blank email to
 [EMAIL PROTECTED]
 or visit
 http://lists.frameusers.com/mailman/options/framers/rentagoodbook%40gmail.com

 Send administrative questions to [EMAIL PROTECTED] Visit
 http://www.frameusers.com/ for more resources and info.

___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Brian Weis
I just wanted to express my thanks to Art Campbell. I removed SP3 from my
machine and I once again have full Visio pasting functionality.

I did post a comment on Microsoft's website under the SP3 write-up regarding
this issue. It's not a nag, but at least I let them know their update was
causing problems.

Thanks again, Art!

--
Brian Weis


--
From: Art Campbell [EMAIL PROTECTED]
Date: Fri, Jun 20, 2008 at 11:16 AM
Subject: Re: FrameMaker Internal Error -- Visio and ...lost image data
To: Brian Weis [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]


If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

rest of message snipped for brevity
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


RE: FrameMaker Internal Error -- Visio and ...lost image data

2008-06-20 Thread Dov Isaacs
For better or worse, if you simply mailed in the report to Adobe,
don't expect a personal if any response. That mechanism is not
Adobe Tech Support.

For future reference, regardless of what program you publish with
copy-and-paste is about the worst way to set yourself up for disaster
in case your document get lost or mangled.

- Dov


 -Original Message-
 From: Brian Weis
 Sent: Friday, June 20, 2008 7:36 AM

 Hi folks:

 Yesterday, I encountered this error in FM:  An internal error occurred
 while writing imported graphics in this document. The file has been saved,
 but has lost some image data. Please report this error to Adobe Technical
 Support.


 I close the error dialog, and then try to close the file ... but I am
 prompted once again to save it before closing. I am now in a loop until I
 break the cycle by clicking No in the save prompt. Contrary to the error
 message's statement that the file has been saved, I find that none of my
 changes, text or otherwise, are in the file. With a little more work, I am
 able to determine that a Visio object must be the culprit.

 How do I know this?

 In the directory where my source Frame doc is located, I see a set of
 garbage files -- that is, files that my system does not recognize by
 filename extension. I recognize them as copies of my source doc ... but with
 different extensions (e.g., .BE7, .75F). These files have date/time stamps
 right around the time I was trying to save my changes. Right clicking on one
 of these files, and specifying FrameMaker to open it, I find a version of my
 document with the most recent set of changes ... but the Visio object is now
 grayed out in its inline frame.

 Just to be clear, I am using Visio object to refer to an graphic that I
 have inserted by copying the elements from the original Visio drawing and
 then pasting them into an inline frame in FrameMaker. I did not use the
 Import File option.

 I did some more testing with a copy of my now-recovered source document.
 While playing with different ways to insert/paste the Visio work, and
 accessing Visio work in other documents by right-clicking them and selecting
 Visio Object from the pop-up menu, Framemaker eventually detected a
 serious problem and had to quit. This error dialog called out a FrameLog
 file (an error log) and instructed me to send the file and a description of
 what I did to [EMAIL PROTECTED]


 I have been using the paste method with Visio objects successfully for
 almost two years. I realize it is not recommended, but I have never had an
 issue until now. And it looks like my previous documents that have one or
 more Visio objects inserted in this fashion will suffer the same problem. At
 least, all such files I have tested exhibit the same problem -- even just
 opening a file that has a Visio object will subject it to this problem.

 I sent all the info and the error messages (a longer summary than I've
 posted here) to Adobe around 6pm last night. I have not heard from them, and
 I probably should not expect to. I have searched Adobe Support for info on
 Visio, Internal Error 7204, and other things, but have not found anything
 helpful. So I come to you in the Frame using community. Has anyone here
 copy/paste Visio into Frame? Have you ever come across this problem? Do you
 know a solution?

 Thanks in advance.

 --
 Brian Weis
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Brian Weis
Hi folks:

Yesterday, I encountered this error in FM:  "An internal error occurred
while writing imported graphics in this document. The file has been saved,
but has lost some image data. Please report this error to Adobe Technical
Support."


I close the error dialog, and then try to close the file ... but I am
prompted once again to save it before closing. I am now in a loop until I
break the cycle by clicking "No" in the save prompt. Contrary to the error
message's statement that the file has been saved, I find that none of my
changes, text or otherwise, are in the file. With a little more work, I am
able to determine that a Visio object must be the culprit.

How do I know this?

In the directory where my source Frame doc is located, I see a set of
"garbage" files -- that is, files that my system does not recognize by
filename extension. I recognize them as copies of my source doc ... but with
different extensions (e.g., .BE7, .75F). These files have date/time stamps
right around the time I was trying to save my changes. Right clicking on one
of these files, and specifying FrameMaker to open it, I find a version of my
document with the most recent set of changes ... but the Visio object is now
grayed out in its inline frame.

Just to be clear, I am using "Visio object" to refer to an graphic that I
have inserted by copying the elements from the original Visio drawing and
then pasting them into an inline frame in FrameMaker. I did not use the
"Import File" option.

I did some more testing with a copy of my now-recovered source document.
While playing with different ways to insert/paste the Visio work, and
accessing Visio work in other documents by right-clicking them and selecting
"Visio Object" from the pop-up menu, Framemaker eventually "detected a
serious problem" and had to quit. This error dialog called out a FrameLog
file (an error log) and instructed me to send the file and a description of
what I did to fmerror at adobe.com.


I have been using the paste method with Visio objects successfully for
almost two years. I realize it is not recommended, but I have never had an
issue until now. And it looks like my previous documents that have one or
more Visio objects inserted in this fashion will suffer the same problem. At
least, all such files I have tested exhibit the same problem -- even just
opening a file that has a Visio object will subject it to this problem.

I sent all the info and the error messages (a longer summary than I've
posted here) to Adobe around 6pm last night. I have not heard from them, and
I probably should not expect to. I have searched Adobe Support for info on
Visio, "Internal Error 7204", and other things, but have not found anything
helpful. So I come to you in the Frame using community. Has anyone here
copy/paste Visio into Frame? Have you ever come across this problem? Do you
know a solution?

Thanks in advance.

--
Brian Weis


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Art Campbell
If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

Or you can convert the Visio objects to PDF, PNG, or other graphic
files and import them by reference.

May want to nag Microsoft some, if you think that would have an effect. ;- )

Of course, if you're not using XP and haven't installed SP3, something
else is at work, but I didn't see any system or FM version details in
your post. Which would be important in solving the problem if it is
something else.

Art

On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis  
wrote:
> Yesterday, I encountered this error in FM:  "An internal error occurred
> while writing imported graphics in this document. The file has been saved,
> but has lost some image data. Please report this error to Adobe Technical
> Support."
>
>
> I close the error dialog, and then try to close the file ... but I am
> prompted once again to save it before closing. I am now in a loop until I
> break the cycle by clicking "No" in the save prompt. Contrary to the error
> message's statement that the file has been saved, I find that none of my
> changes, text or otherwise, are in the file. With a little more work, I am
> able to determine that a Visio object must be the culprit.


-- 
Art Campbell art.campbell at gmail.com
 "... In my opinion, there's nothing in this world beats a '52 Vincent
and a redheaded girl." -- Richard Thompson
 No disclaimers apply.
 DoD 358


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Rene Stephenson
OK, so to tie in with another thread: if you go with a PC so you can run FM 
current version in native OS, stick with XP SP2...? Gotcha.


Rene L. Stephenson



- Original Message 
From: Art Campbell 

If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

...Art


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Lise Bible
I had similar error messages with Frame files with OLE links to Excel
spreadsheets, but mostly randomly--sometimes I had the Excel file open by
mistake, and that might have triggered it, I'm not sure. I could never find
the exact cause. Was running Frame 7.1 on XP, SP2.

A colleague told me she got those errors all the time (same OLE links to
Excel files). She's going to be upgrading to Frame 8, but she's getting a
new computer as well, so there are too many variables there to narrow down
one cause if it ends up fixing her problem.

Have upgraded to Frame 8, still XP, SP2. Haven't had it that long, but I
haven't had any error messages so far. Doesn't mean that the upgrade fixed
the problem, though.

Using PDF's or graphics isn't a good fix for me, because we're linking to
parts lists that appear in the product manual and a separate parts book for
the entire product line. The advantage of OLE links to the Excel files is
that it's always linked to the latest and greatest version.

So thanks for the heads-up about SP3. I don't know if our IS dept. will be
rolling that out soon or not. Fortunately, I don't believe there are any
imminent plans to upgrade us to Vista.

-Lise

On Fri, Jun 20, 2008 at 10:16 AM, Art Campbell 
wrote:

> If you search back through the archives and/or visit the Frame user's
> forum on Adobe.com, you'll see that this has been a pretty common
> topic since Microsoft released SP3 for XP. They included some security
> fixes to OLE that have effectively broken it, at least as far as
> managing objects in Frame go.
>
> Only reported fix is backing out of SP3.
>
> Or you can convert the Visio objects to PDF, PNG, or other graphic
> files and import them by reference.
>
> May want to nag Microsoft some, if you think that would have an effect. ;-
> )
>
> Of course, if you're not using XP and haven't installed SP3, something
> else is at work, but I didn't see any system or FM version details in
> your post. Which would be important in solving the problem if it is
> something else.
>
> Art
>
> On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis 
> wrote:
> > Yesterday, I encountered this error in FM:  "An internal error occurred
> > while writing imported graphics in this document. The file has been
> saved,
> > but has lost some image data. Please report this error to Adobe Technical
> > Support."
> >
> >
> > I close the error dialog, and then try to close the file ... but I am
> > prompted once again to save it before closing. I am now in a loop until I
> > break the cycle by clicking "No" in the save prompt. Contrary to the
> error
> > message's statement that the file has been saved, I find that none of my
> > changes, text or otherwise, are in the file. With a little more work, I
> am
> > able to determine that a Visio object must be the culprit.
> 
>
> --
> Art Campbell art.campbell at gmail.com
>  "... In my opinion, there's nothing in this world beats a '52 Vincent
> and a redheaded girl." -- Richard Thompson
>  No disclaimers apply.
>  DoD 358
> ___
>
>
> You are currently subscribed to Framers as rentagoodbook at gmail.com.
>
> Send list messages to framers at lists.frameusers.com.
>
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com
> or visit
> http://lists.frameusers.com/mailman/options/framers/rentagoodbook%40gmail.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Brian Weis
Mae culpa! I am so sorry I did not provide those details. I must not have
copied them over from my message to Adobe. Thanks so much, Art, for pointing
out the omission!

I am using Adobe FrameMaker 7.2b144
Microsoft Office Visio Professional 2003 (11.8207.8202) SP3
and
MS Windows XP ... SP3!

Sometimes I do convert Visio drawings to other formats, but there are times
when the best results come from simply pasting the Visio elements directly
into Frame. So I would like to retrieve that functionality.

Your comments make sense because my machine recently downloaded updates and
restarted. So, it looks like I should try backing out of SP3 today. I'll
probably have better luck with that than with nagging MS. :)

Thanks again!

--
Brian

--
From: Art Campbell <art.campb...@gmail.com>
Date: Fri, Jun 20, 2008 at 11:16 AM
Subject: Re: FrameMaker Internal Error -- Visio and "...lost image data"
To: Brian Weis 
Cc: framers at frameusers.com


If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.

Or you can convert the Visio objects to PDF, PNG, or other graphic
files and import them by reference.

May want to nag Microsoft some, if you think that would have an effect. ;- )

Of course, if you're not using XP and haven't installed SP3, something
else is at work, but I didn't see any system or FM version details in
your post. Which would be important in solving the problem if it is
something else.

Art

On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis 
wrote:
> Yesterday, I encountered this error in FM:  "An internal error occurred
> while writing imported graphics in this document. The file has been saved,
> but has lost some image data. Please report this error to Adobe Technical
> Support."
>
>
> I close the error dialog, and then try to close the file ... but I am
> prompted once again to save it before closing. I am now in a loop until I
> break the cycle by clicking "No" in the save prompt. Contrary to the error
> message's statement that the file has been saved, I find that none of my
> changes, text or otherwise, are in the file. With a little more work, I am
> able to determine that a Visio object must be the culprit.


--
Art Campbell art.campbell at gmail.com
 "... In my opinion, there's nothing in this world beats a '52 Vincent
and a redheaded girl." -- Richard Thompson
 No disclaimers apply.
 DoD 358


FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Brian Weis
I just wanted to express my thanks to Art Campbell. I removed SP3 from my
machine and I once again have full Visio pasting functionality.

I did post a comment on Microsoft's website under the SP3 write-up regarding
this issue. It's not a nag, but at least I let them know their update was
causing problems.

Thanks again, Art!

--
Brian Weis


--
From: Art Campbell <art.campb...@gmail.com>
Date: Fri, Jun 20, 2008 at 11:16 AM
Subject: Re: FrameMaker Internal Error -- Visio and "...lost image data"
To: Brian Weis 
Cc: framers at frameusers.com


If you search back through the archives and/or visit the Frame user's
forum on Adobe.com, you'll see that this has been a pretty common
topic since Microsoft released SP3 for XP. They included some security
fixes to OLE that have effectively broken it, at least as far as
managing objects in Frame go.

Only reported fix is backing out of SP3.




FrameMaker Internal Error -- Visio and "...lost image data"

2008-06-20 Thread Dov Isaacs
For better or worse, if you simply mailed in the report to Adobe,
don't expect a personal if any response. That mechanism is not
Adobe Tech Support.

For future reference, regardless of what program you publish with
copy-and-paste is about the worst way to set yourself up for disaster
in case your document get lost or mangled.

- Dov


> -Original Message-
> From: Brian Weis
> Sent: Friday, June 20, 2008 7:36 AM
>
> Hi folks:
>
> Yesterday, I encountered this error in FM:  "An internal error occurred
> while writing imported graphics in this document. The file has been saved,
> but has lost some image data. Please report this error to Adobe Technical
> Support."
>
>
> I close the error dialog, and then try to close the file ... but I am
> prompted once again to save it before closing. I am now in a loop until I
> break the cycle by clicking "No" in the save prompt. Contrary to the error
> message's statement that the file has been saved, I find that none of my
> changes, text or otherwise, are in the file. With a little more work, I am
> able to determine that a Visio object must be the culprit.
>
> How do I know this?
>
> In the directory where my source Frame doc is located, I see a set of
> "garbage" files -- that is, files that my system does not recognize by
> filename extension. I recognize them as copies of my source doc ... but with
> different extensions (e.g., .BE7, .75F). These files have date/time stamps
> right around the time I was trying to save my changes. Right clicking on one
> of these files, and specifying FrameMaker to open it, I find a version of my
> document with the most recent set of changes ... but the Visio object is now
> grayed out in its inline frame.
>
> Just to be clear, I am using "Visio object" to refer to an graphic that I
> have inserted by copying the elements from the original Visio drawing and
> then pasting them into an inline frame in FrameMaker. I did not use the
> "Import File" option.
>
> I did some more testing with a copy of my now-recovered source document.
> While playing with different ways to insert/paste the Visio work, and
> accessing Visio work in other documents by right-clicking them and selecting
> "Visio Object" from the pop-up menu, Framemaker eventually "detected a
> serious problem" and had to quit. This error dialog called out a FrameLog
> file (an error log) and instructed me to send the file and a description of
> what I did to fmerror at adobe.com.
>
>
> I have been using the paste method with Visio objects successfully for
> almost two years. I realize it is not recommended, but I have never had an
> issue until now. And it looks like my previous documents that have one or
> more Visio objects inserted in this fashion will suffer the same problem. At
> least, all such files I have tested exhibit the same problem -- even just
> opening a file that has a Visio object will subject it to this problem.
>
> I sent all the info and the error messages (a longer summary than I've
> posted here) to Adobe around 6pm last night. I have not heard from them, and
> I probably should not expect to. I have searched Adobe Support for info on
> Visio, "Internal Error 7204", and other things, but have not found anything
> helpful. So I come to you in the Frame using community. Has anyone here
> copy/paste Visio into Frame? Have you ever come across this problem? Do you
> know a solution?
>
> Thanks in advance.
>
> --
> Brian Weis