Internal Errror when saving as a png

Hello,
I use Fireworks to create a map with some special information. I have three layers, one contains the map itself (3 pictures), one contains a lot of circles (vectors, round about 40) and the third contains the additional text. Till now everything is fine. But when a place one more circle (vector) and I want to save my project (as png) I get the error message "Internal Error". That's it, no hint or something like that what the problem is. Does Fireworks only supports a maximum count of vectors? Or some problems with the memory, maybe the ram is to low... (Can I configure I much ram fireworks should use?)
I work with Fireworks CS 4, Windows 7 on an Intel i7 with 8 GB ram. Thanks for your help.

7251 x 8054 pixels? Wow. This is what causes the issue...
Fireworks is mainly a tool for screen design. It handles pretty well files of approx. 2000-3000 px (width and/or height), but not much larger than that.
In my personal experience, I can say that Fireworks is pretty fast and stable when file is under 2000-3000 px in size, but if once you make the file larger than 4000-5000 px, Fw can become a bit slow, sometimes unstable. After 6000 px, I rarely can work normally -- the biggest file I was ever able to edit and successfully export was ~ 9000x6000 px, but at this point Fw becomes too unstable and slow...
Do you need such large size? Are you preparing something for screen? Maybe you can split the file into 2-3 smaller files?
HTS

Similar Messages

Internal error when saving

if i open a new FW document and attempt to save (with the
intention of this being a template) with a customised canvas size,
i get internal error. i am only opening a document with a
customised canvas colour and size, no fonts involved, or any thing
else in the document.
system specs: winxp pro sp2, 1g ram, 99g HD space.
i have opened FW on another computer running the same OS and
left default settings in the "new document window" and was able to
save correctly. when i changed the settings, it to responded with
internal error.
this only seems to happen if i use png format, is there a way
around this (or must i use an alternative format?)
thanks in advance

kate161 wrote:
> if i open a new FW document and attempt to save (with
the intention of this
> being a template) with a customised canvas size, i get
internal error.
What is the customized canvas size?
Linda Rathgeber [PVII] *Adobe Community Expert-Fireworks*
http://www.projectseven.com
Fireworks Newsgroup:
news://forums.projectseven.com/fireworks/
CSS Newsgroup: news://forums.projectseven.com/css/
Design Aid Kits:
http://www.webdevbiz.com/pwf/index.cfm

Internal error when saving Frame file

I recently got the following message when trying to save some files on the network:
"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 had never seen this error before. When I try to update the book, I get the following error:
"Cannot save one or more files in the book. Open each file on the desktop. Check the permissions of the file on the disk, and then save the file manually."
This was never a problem before--this occurred all of a sudden. I checked the permissions and it hasn't changed. When I work on the book files locally, I can save the files just fine. I only get the errors when the files are on the network.
Any suggestions?
Thanks in advance,
Michelle

Michelle,
Some setting in your network configuration is messing with FM. If it
works locally, then bring your files down to your local drive, do your
work, and then re-upload them to the network outside of FM.
FM and networks don't always get along. If you're using UNC naming for
the network path, try to create a network drive instead.

Gaps in-between livepaint shapes when saving to PDF

Im using CS6 and when saving to PDF my live paint objects have a slight gap inbetween the shapes in the live paint object. They do not appeare in the illustrator file or when saved as jpeg, png, etc only PDFs. I have been using Illustrator for a couple years now and this has not happened in previous versions I've worked with (CS3, 4, and 5)
Thanks

The thin lines around the rings are an artifact in pdf preview. Thi si the saem problem http://helpx.adobe.com/indesign/kb/thin-white-dark-lines-stitching.html
You may be able get rid of them by changing your acrobat settings such as turn off smooth line art.

Error message when saving a PDF to PNG: Error attempting to write file.

I get an error message when saving a PDF to PNG. JPG and TIFF works, but no PNG.
Disk space is sufficient! 100GB of 250
A few weeks ago it was no problem to save as PNG. But now! (Perhaps from last update?)
Messages:
When clicking "Ignore":
Adobe Acrobat XI Standard
Version 11.0.09

I have this issue too, but my colleagues do not have this issue(we have same Acrobat Pro 11.0.09). I am sure this issue happens only you updated to 11.0.09, because when you use Windows Restore back to 11.0.08, no issues.

Bug when saving transparent png

I just saved a few pngs with transparent backgrounds and somehow the icons for those new images are being merged or overlaid with previously saved jpgs in my photo stream. When I open them, I see the picture I expect so there's no damage occurring, just funky icons. When I viewed the same images from the photo stream on my iPhone 4 and AppleTV2, the same behavior occurred with those transparent png files as well.

Hi Ignacio,
Well I sort of owe you guys an apology as it appears to be an iPad/iOS issue actually. Apparently I've never tried sending a transparent png to either my iPhone or iPad until learning/using Photoshop Touch (which I'm really enjoying btw).
But to answer your questions anyway, I was opening them on my iPad/iPhone in the Photos app and on my AppleTV in the Photostream there.
I made a quick transparent png from my Photoshop CS3 as well as downloading one from a Google search, all which had the same overlapping results.
I grabbed a screen shot for you, and blurred out the icons of images I think you'd rather not see ;-). Weird thing though too, which also points to this being an Apple issue, is that by accident, my first image, I saved as a png but with the background layer unlocked (being layer zero) and when I dragged it into this email, it overlaid the picture over the body of the email so that the black areas where transparent. So I dragged it out, resaved as a jpg but now I can't repeat the problem with the png, as I was going to create a screen shot of that for you as well. Either way, the icons on my desktop behave as normal and the images all open as normal. They all just get goofed up when displaying them in iOS as icons before actually opening the pictures.
So in this capture, there are six images with overlapping icons where the intended transparent png is on top of some random image pulled from the photostream.
Thanks again,
Eric

When saving out transparent web pngs, they are showing up 'dirty' in other applications (like Gimp). Help?

I've linked one of the images in question; a 16x16 px icon for a settings page we're using. When this image is opened in another program (Gimp, in this case- the dev team does not have Photoshop), they are finding 'dirty pixels'. Specifically, if you are looking at the image, just above the base row of blue, where it should be white, it's showing up as a 10% transparent blue row all the way across. This does not appear in Photoshop, nor can I remove this area by deleting, etc.
I assume the issue is either how it's being saved out, in which case, is there a best way of saving out small transparent web images? Or, the issue is with Gimp (which I would be happy with), I am just not familiar with the application to know. Or, I am just creating the images wrong.
Thanks!

This what i see in gimp
Maybe this is what they talking about, that there is some blue areas that should not be there, yet are after filling in the alpha channel (transparency channel in photoshop)
Same as doing Layer>Layer Mask>From Transparency in photoshop.
Upon opening in gimp
After filling in the alpha (transparency) channel
Which version of photoshop and operating system did you use?
When i tried several different variations in photoshop cc 2014.1, i always had visible pixels that shouldn't have been there after saving as a png
Doing the same in photoshop 6 yielded the expected results of what was there before, was there after saving and no more.

Colour loss when saving PNGs.

Hi there,
I'm fairly new to photoshop and am having a few difficulties when saving a PNG.
I'm using a Mac Book Pro.
I'm using Photoshop CS6.
The problem I'm encountering is when I save a PNG file I'm losing a lot of colour saturation. It goes from a vibrant red to a dull red colour.
The workspace is RGB 8bit.
I'm using the SAVE AS function because I don't want it for web I need it for print and I need the transparent background too.
The only way I've managed to get the full colour is by using the save for web option and selecting PNG-24.
Any help would be greatly appreciated.

I'm using the SAVE AS function because I don't want it for web I need it for print and I need the transparent background too.
Then I see no reason for using png but think you should use psd.
The workspace is RGB 8bit.
Workspaces are something completely different in Photoshop (and concern Panels, Menus etc,) and RGB is not a Color Space but a Color Mode.
What is the image’s Color Space or if it isn’t embedded what is your RGB Working Space (Edit > Color Settings)?

Color Profile issues / Colors darken when saving as png/jpg

Hello Adobe Community!
I got a problem with the color settings / profiles in Photoshop and I hope someone can help me.
For the record: I Am working an a PC (Windows 7) with Photoshop CS4.
I work on a digital painting in Photoshop and to keep track of my progression I save frequently as pngs.
I noticed that the colors don't match and are much darker as you can see in the picture below:
I tried the things suggested in many forums, checking and converting my color profiles. For many that seemed to fix it, but not for me.
In the source space you can see the Profile I am using.
Many suggested when saving for web and devices one should untick the "convert to sRGB" checkbox, but for me, that didn't change anything and the colors were still messed up.
I hope someone has a solution for this problem. After trying so many things I'm getting quite desperate!

always CONVERT to sRGB (if not already there) when saving for the web and unmanages apps
there are both pros and cons for tagging/untagging images for the web
the slight darkening and saturation difference i see in in your posted image is expected between managed and unmanaged apps, but you didn't embed a profile so it is my guess what you are seeing there
to duplicate the phenomenon, in Photoshop, open your tagged sRGB image, then
View> Proof Setup: Monitor RGB (be sure to turn it back off)
the shift you see there is the difference between sRGB and your monitor profile (Photoshop is in essence stripping the sRGB profile and sending the RGB numbers straight through to the monitor with no changes)
as you probably know, Photoshop normally transforms (changes) the source colors to the monitor profile...

User Exit or BADI when saving Internal Orders

Hello, I need a user exit or BADI when saving a Internal Orders to shoot a workflow
REGARDS
Dayana

Hi
Why do you need a user exit or BADI.
Create a Custom Business Object(SWO1) and Create a New Event(SW01) and link it to the B.O. Or you could also create a CO Validation and use it for triggering a Validation and as a last resort you go for User Exit or Abap code.
Check if you have some workflow expertise in your tech team and you should be fine.
Thanks,
Praveen

Streaking across PNGs when saved to PDF.

I'm seeing some streaking/banding across PGN images when I save a PAGES2.0.2 doc to PDF...
Have others onticed this?
Is there a FIX?
The layout is fine and shows no "streaking/banding " in the PNGs in the Pages202 Project itself. Only when saved to a PDF do they appear...
thanks

I was working in Photoshop, flattening/merging layers as I go and dragging across the flattened/merged layer w/alpha into Pages202 from the open Photoshop project.
Seemed like a good way to work since Pages202 doesn't auto-update any corrected art/files saved out of Photoshop it might be using/linked to. If I needed to modify/correct an image, I did it on the spot in PS-CS2 and simply dragged it across to replace the ones in Pages202 I wanted to update.
Sometimes I saved the PS files as PNGs (because I need the alpha transparency) and imported them into Pages202 directly. They all exhibit the banding problem when the project is Exported/Printed to PDF from Pages202.
It's still odd, however, that if I drop the exported Pages202 PDF back into Photoshop and re-export as a PhotoshopPDF--the banding isn't there.
It only is visible when looking/printing from a Pages202 PDF in Preview or Acrobat.
I'll see how the PNG-24 method goes (though it changes overall color saturation of the picture, which I'll have to compensate for) It would be great if pages202 could "update" it's imported image files automatically...
Thanks.

When I save a PNG file at 300 ppi, it opens at 299.999

This is driving me nuts. When I save a photoshop file as a .png at 300 ppi, when I open it it is 299.999 ppi.
I wouldn't mind for my personal use, but these are digital files I sell. Believe me, I will get emails about it.
Even when I open the .png file and change the ppi to 300, if I open it again it's once again 299.999!
I am saving files with a transparent background with compression no interlacing. I'm using save as, not save for web.
Here's the interesting thing.
1. This started happening when I got my new iMac with Lion and installed CS6. Did both at the same time.
2. My assistant, this happens with my assistant who is on PC with Photoshop CS5.
What's going on and how can I fix this?

I did find this article.
"Most other programs do store and use the correct scaled resolution value in PNG files. PNG stores resolution internally as pixels per meter, so when calculating back to pixels per inch, some programs may show excessive decimal digits, perhaps 299.999 ppi instead of 300 ppi (no big deal)."
I don't know why this has started happening in CS6 though. Didn't happen in CS5. Hmm. Actually, I do have CS5 installed. Maybe I should try doing my pngs in it again.
Just searched around the web. I guess this is a common occurance. I'll just have to put it in my support FAQS that this is normal and doesn't affect the image.

Errors when saving to SMB mounts (a thorough examination)

Several of the users I support have reported the following issue when trying to save files to the network from Photoshop. I have found several threads about this on both the Adobe forums and the Mac forums. However, in most of the threads the information provided is incomplete or does not control for enough variables. And the result is that Adobe seems to blame Apple, and Apple seems to blame Adobe. So blame aside, here is information that I hope helps Adobe solve the issue at hand.
When saving to a mounted SMB point, users report one of two errors:
Could not save <filename> because of a program error
Could not save <filename> because write access was not granted
I can replicate the issue on:
Lion 10.7.X with Photoshop CS 5
Lion 10.7.X with Photoshop CS 5.1
Snow Leopard 10.6.X with Photoshop CS 5
Snow Leopard 10.6.X with Photoshop CS 5.1
Details:
We have only seen this error in Photoshop. << Adobe has seen the same problems in several other applications >>
I have not tested out whether the issue applies to any other products in the CS suite.
At first I thought the issue might have to do with permissions, but it does not. I have reapplied permissions and the issue persists. And it affects all users, including Domain Admins, such as me, who have no R/W restrictions at any level.
The issue only occurs when Finder is in a view that shows a thumbnail/preview of the image.
Switching Finder to list mode resolves the error in all scenarios
So far I can replicate this with any file on any mount on any of our servers
It only occurs on mounted network points (ie - if I move the files locally, no errors are encountered)
For the following tests, presume the following:
Source folder: smb://example/source/folder
Target folder: smb://example/source/folder
Target sub-folder: smb://example/source/folder/sub
Here are the steps I tested:
Opened the file problem_file.psd.
A warning pops up prompting me to resolve a font vector issue, I chose "Update"
Note: that this error does not pop up for every file, just the original file I worked with, but this warning has nothing to do with the errors being received
Moved a layer so that there would be a change to save
Clicked save
Received the error: "Could not save <filename> because of a program error" << probably related to the known MacOS bug on SMB, or a known Finder/thumbnailing bug >>
The original file, problem_file.psd, is *DELETED* (very problematic) << Known MacOS bug in SMB service, Apple is working on it >>
Then I tested with multiple variations of the following to conrol for things such as layers or font issues:
To eliminate the source file being the issue, I used a .png file that I had created locally with the OS-X screen shot keyboard command. This eliminated layers and fonts as issues.
In step 2 I chose to not update the font vector issue
In step 4 I tried saving as different file types (.jpg, .png, .gif)
Prior to step 6 I flattend the image to eliminate fonts and layers. This eliminated layers and fonts as issues.
Prior to step 6 I flattened the image, duplicate the image, closed the original (without saving), and attempted to save the new duplicate. This eliminated layers and fonts as issues.
Each variation still resulted in "Could not save <filename> because of a program error" and resulted in the deletion of the source file.
Next I controlled for saving image previews:
Photoshop -> Preferences -> File Handling
Under File Saving Options -> Image Previews, I set it to "Never Save" previews
Now when I repeated the tests from aobve, I receved the error "Could not save <filename> because write access was not granted".
Next I controlled for .DS_store files:
Disabled .DS_Store file creation on remotely mounted points.
Deleted the .DS_Store file for the source folder
Verified that .ds_store files were not being created on remotely mounted points
Ran the tests above, and the issue persisted: "Could not save <filename> because write access was not granted"
Now I decided to test sub-folders:
Created a target sub-folder.
Repeated the test above, and its variations, but saving the problem_file.psd to the target sub-folder.
Still received one of the two errors, depending on the variation, but the source file is no longer deleted. This make sense because saving in another directory is really a "save as", and one would not expect safe saving (talked about more later) to affect source files in this scenario.
Sort of a Solution:
Open the file from Finder
Depending on the Finder view, Finder shows a thumnail of the image
Go back to Finder and select a different file
Make changes to the file
Save the file
No error is received
This is when I discovered that the error only occurs when Finder is in a view that shows a thumbnail/preview of the image. Further testing of Finder show that in Cover Flow the error only occurs for the selected image. For example:
Cover flow shows thumbnails/previews of files: A, B, C, D, E
Open A
In Cover Flow select file B
The thumnails of of files A, B, C, D, E are still visible
Make a change to the open file
Save the change
No error is received
This shows that Finder is treating the thumbnails/previews of unselected files different than selected files.
An Interesting Twist:
If from the last scenario with Cover Flow...
Open file A
Go back to Finder and select a different file
Then make a change and attempt to save to the target sub-folder
Receive the error "Could not save <filename>" because of a program error.
Discussion:
Photoshop does something called safe saving.
Photoshop saves the current document to a temporary file with a unique name
Photoshop deletes the original file << this is incorrect >>
Photoshop moves the temporary file to a file with the name of the original file that was deleted in step 2 << incorrect: the temp file replaces the original with an OS call to a function that is supposed to be an atomic operation >>
However, you can see that "safe saving" is misnamed, because while the original is deleted, Photoshop does not appear to be correctly ensuring that permissions exist to allow the temporary file to be ranemd or that the temporary file was renamed without error. Photoshop is either:
Not checking for the error << yes, it is >>
Checking for the permissions and not catching the error << incorrect >>
Checking for the permissions and giving an error to generic to discern the exact problem from. << also incorrect >>
Somewhere there is a conflict (perhaps a race condition) between:
Photoshop creating the temporary file
The server applying permission to the newly created temporary file
OS-X reporting the file has been created
Photoshop deleting the original file
Photoshop saving the new file
Finder updating the thumbnail of the file
As I've shown here, the problem doesn't seem to reside fully with Apple or fully with Adobe. Hopefully this post provides enough information for some clever engineer to create a fix.
My information about safe saving is from an Adobe mod on a previous thread regarding this issue << and copied incorrectly, plus added bad assumptions>>. He detailed the process and also explained that Photoshop uses OS APIs to create and delete the files during safe saving. If his details are accurate, it seems that a temporary fix would at least change the safe saving process to the following:
Photoshop saves the current document to a temporary file with a unique name
Photoshop moves the original file to a temporary backup file (original-file-name.original-extension.bak)
Photoshop moves the temporary file to a file with the name of the original file moved in step 3
Photoshop checks to make sure that the temporary file has been succesfully renamed
If the temporary file has successfully been renamed, it deletes the backup file from step 2 OR if the temporary file has failed to be renamed, the backup is returned to its original file name
The appropriate error message, if any, is displayed
A Few Sources:
http://adobe.hosted.jivesoftware.com/message/4016324
http://forums.adobe.com/thread/732422
https://discussions.apple.com/thread/3380971?start=0&tstart=0

You got several details wrong.
And it sounds like you are describing 2 known MacOS bugs:
1) The OS fails when creating or swapping files on SMB servers, and this happens more often on files that have a resource fork.
2) The Finder/QuickLook/Thumbnailing holds a file busy when it should not, causing program errors or file is busy errors.
We did as much as we could to work around these issues in Photoshop CS6 - after spending a lot of time debugging the OS issues and working with Apple.
Apple is still working on proper fixes within the OS.

While using a drop-down menu i.e. File, edit, image, or even when saving as and choosing the file type; the list appears and I am able to highlight what i want but cannot click on anything.

While using a drop-down menu i.e. File, edit, image, or even when saving as and choosing the file type; the list appears and I am able to highlight what i want but cannot click on anything. This is becoming incredibly frustrating. It happens at random time and a restart of the computer is all that helps, then with out any notice it starts to do this again. Mac Book Pro i7 2.2 16 GB 1333 Ram, (2) 450GB SSD both internal to machine. At this point I am losing file because I am unable to save in the file type I need. Does anyone out there know how to solve this issue?
Thanks
phil

I haven't been unify photoshop much in the past month, but I did try your suggestion and it seemed to work for a while. Today when i went to save a document the same thing happened: click on file>save at this point I can not click on save even though it is highlighted. Tryed to use command s that brings up the save dialogue box, but when I try to change file type I again cannot select it from the drop down menu.

Inserting Pricing condition in Sales order when saving the sales order

Dear ABAPers,
My customers requirement is when saving the sales order new pricing condition has to be updated in the line item.for this i am using the User Exit 'USEREXIT_SAVE_DOCUMENT_PREPARE' ( MV45AFZZ).While saving the Sales order i am calculating the Price and updating in the Pricing conditions.
In XKOMV internal table i am appending the pricing condition.But the problem is ,it is not calculating the taxes and it is Updating in VBAK and VBAP.
How to do this.
Thanks & Regards,
Ashok.

Dear ABAPers,
I have Solved this Problem.
Thanks & Regards,
Ashok.

Internal Errror when saving as a png

Similar Messages

Maybe you are looking for