Font licensing error when Saving?

I use Illustrator CC and get a licensing error when saving designs with downloaded fonts.
The designs look fine on my computer and fine when I open them from my drop box account.
The problem comes when others open the design, the fonts change to Arial in most cases, which is causing design issues.
This is even happening when the design is saved as a PDF.
How do I solve this problem?
Can I get licenced fonts?
Where are they available?
Many thanks for reading.

You can have your other contacts download and install the same fonts
or
you can select all the text in your document and create outlines of the fonts, printers often ask for this option.
or
You can purcahse fonts from say Adobe and if I am not mistaken you can have those installed on five work stations, I do not know if you are allowed to consider a colleague as legal user of the fonts. And I do no recall if the number of seats for the fonts have changed but it used to be five seats. As I recall.
or
you can purcahse from My Fonts as well http://www.myfonts.com but again the other contacts ave to have the fonts installed as well check out how many seats for the fonts ypoouare entitled to and if that includes remoe sites for the seats.

Similar Messages

Error when saving

Hello BW Experts,
I am getting this error while saving a query in Bex.
'The query could not saved due to a problem in transport'.
I am actually creating a test query production. I am not sure why it is refering to the transport. From what i understand there is nothing to deal with transports.
Anyone experienced a similar problem before.
Suggestions appreciated.
Thanks,
BWer

OSS NOTE 194051
Symptom
An error occurs when you save a query:
Error when saving
"The query could not be saved due to a problem in transport".
Other terms
Business Explorer, query, transport, save, R9 124
Reason and Prerequisites
There are 4 possible reasons for this problem:
1. The BEx default transport request or the development class-dependent transport request is not maintained or released in the Administrator Workbench.
2. The system is set to "cannot be changed". Refer to Note 337950 (as of 2.0b SP 11), which describes how query objects can be edited in systems that cannot be changed.
3. You are not authorized to write to Workbench requests.
4. The BEx default transport request or the development-class-dependent transport request in the Administrator Workbench has another target system than the query (the transport destination of the query is determined via the transport layer of the query's development class (as of 3.0: of the package)).
The error only occurs for query objects which already have a development class, that means, which were already placed on a transport request.
Solution
Solution for Cause 1:
a) Start the Administrator Workbench
b) Choose 'Goto' to change to Transport connection
c) Choose "Request BEx" or "BEx development classes" in the toolbar.
d) Create a (new) request.
e) All changes in the BEx are now written to this request.The end user is no longer confused by 'Transport' dialog boxes.
Solution for Cause 2:
See Note 337950
Solution for Cause 3:
Authorize user to write to Workbench requests.
Solution for Cause 4:
Create a request for each target system. Assign the request suiting the target system of the transport layer of the development class (of the package) to each development class (as of 3.0: to each package) used for BEX objects.
If this does not change the situation, further information is useful for error analysis.
Go to Transaktion SE16, Table RSZCOMPDIR. In field COMPID, select the technical name of your query. Read the COMPUID of your query.
Go to SE37, function module rso_elem_get_related. Parameter I_IOBJNM is set to the COMPUID, and parameter I_OBJVERS (object version) is set to A. Only the export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT are of interest.
These entries are then entered in function module rs_tr_objects_check_insert in import parameter I_T_TR_OBJECT. In this parameter, fill field PGMID fixed with 'R3TR' and field OBJECT fixed with 'ELEM'. Field OBJ_NAME is filled with the contents of field OBJNM from export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT. The other fields are not relevant.
The export parameters of this function module are required for further error determination. Add this information to your OSS message. The table of messages E_T_MSG is important in particular.

Permission error when saving as pdf

I am using 10.6.7 on a Mini and I get a error when saving a documetn as a PDF. It says I don't have permission to save the file.

Hi Arnis,
I have also posted this separately.
Following is the ditamap i am using to create the PDF. This has booktitle, front matter, toc, chapter and backmatter. I am able to generate a PDF (complete with title page, toc, chapter, backmatter, index) using fop 0.25. However, when I try to create a pdf in FM 9.0, I get only the chapter. How can get the others through FM 9.0. Please provide a solution.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap.dtd" [

<?Fm Validation Off?>

]>
<?Fm Condition DITA-Topicref Blue NO_OVERRIDE show?>
<?Fm Condition FM8_SYSTEM_HIDEELEMENT AsIs NO_OVERRIDE hide?>
<?Fm Condition FM8_TRACK_CHANGES_ADDED Forest%20Green SINGLE_UNDERLINE show?>
<?Fm Condition FM8_TRACK_CHANGES_DELETED Red STRIKETHROUGH show?>
<?Fm BoolCondExpr "" State 0?>
<?Fm TrackChange Off PreviewState PREVIEW_OFF_TRACK_CHANGE?>
<bookmap
    xmlns:ditaarch = "http://dita.oasis-open.org/architecture/2005/">
<booktitle><mainbooktitle>Management</mainbooktitle>
<booktitlealt>Version 4.0</booktitlealt>
<booktitlealt></booktitlealt></booktitle>
<frontmatter><notices></notices>
<booklists><toc navtitle = "Contents"/></booklists>
<preface id = "preface">
<topicref navtitle = "Preface" href = "nm\concepts\nm_Preface.xml"
    type = "concept"><?Fm Condstart DITA-Topicref?><?Fm Condend DITA-Topicref?></topicref></preface></frontmatter>
<chapter navtitle = "Management" href = "nm.ditamap"
    format = "ditamap" id = "chapter"><?Fm Condstart DITA-Topicref?><?Fm Condend DITA-Topicref?></chapter>
<backmatter><booklists><indexlist navtitle = "Index"/></booklists></backmatter></bookmap>

OS 10.6.8, Macbook Pro 3.1 error when saving monitor calibration, cannot save.

Macbook pro 3.1 OS 10.6.8, error when saving monitor calibration profile. Tried to name new profile, or save as an older profile, still got error when attempting to save.

Try a NVRAM reset, and then go through the monitor calibration again.
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the third time.
Release the keys.

Error when saving an Outlook attachment eg. Word Doc after opening it.

we made the group policy change which was giving an error when saving from opened attached files.
But for 1 particular RDS user the error still seems to be occurring. i've tried the following,
1. recreating outlook.
2. recreating user profile.
3. deleted the group policy history from the registry.
4. tried removing outlook add-ins.
your help would be really appreciated.
kind regards

Hi,
What is the error? Does outlook crash? Would you please also detail the group policy change?
We can try cleaning out the Temporary Outlook Files folder to check the result.
We can refer to the following link for the detailed steps to locate and find the temp folder:
http://www.howto-outlook.com/faq/securetemp.htm
Then we need to use OutlookTempCleaner to clean the folder:
http://www.howto-outlook.com/products/outlooktempcleaner.htm
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Melon Chen
TechNet Community Support

Error when Saving Files ID=-39

We are using CS5 on iMac and get the following error when saving:
Can't save preview, but all other information was saved successfully. The file ended unexpectedly. Try using a backup copy. ID = -39
Generally after receiving this error the file is corrupt.
What can we do? Do you need more info? I am not sure what to do with this error.

Most probably that is your problem.
Try if saving to your hard disk solves your problem.

Invalid image error when saving to pdf

I keep getting an invalid image error when saving a MS Publisher file as a pdf. Can anyone help with solving this issue?

You need to provide system and version info and explain how you actualyl produce the PDF. Unless you use the Acrobat PDF printer, I don't see how Adobe software would be involved in any of this, as recent versions of MS Office products can save PDFs natively...
Mylenium

APP-AR-11526 ERROR WHEN SAVING ADJUSTMENT IN AR RECEIPTS FORM

제품 : FIN_AR
작성날짜 : 2003-04-25
APP-AR-11526 ERROR WHEN SAVING ADJUSTMENT IN AR RECEIPTS FORM.
==============================================================
PURPOSE
Problem Description
Receipt화면에서 Adjustment를 하고 Save버튼을 누를때,
APP-AR-11526 arp_process_adjustment.insert adjustment exception ORA-20001
위와 같은 에러 발생.
Workaround
select taxable_amount
from RA_CUSTOMER_TRX_LINES_ALL
where customer_trx_id = 문제가되는 transaction id
and line_type='TAX';
NULL
Update RA_CUSTOMER_TRX_LINES_ALL
set taxable_amount = transaction의 원래 금액
where customer_trx_id = 문제가되는 transaction id
and line_type='TAX';
Solution Description
RA_CUSTOMER_TRX_LINES_ALL의 taxable_amount값이 NULL인 경우,
invoice 금액 adjustment시 오류가 발생한다.
Reference Documents
-------------------

Pl see if MOS Doc 341469.1 (Adjustment Entry: APP-AR-96027: Tax accounting not defined for the tax code or tax location assigned to this invoice) can help.
HTH
Srini

Unresponsive Script Error when Saving Changed Set in Flickr Organizer

I'm getting an unresponsive script error when saving a changed set in the Flickr organizer.
The problem started when using Firefox 3.6.8 or maybe an earlier version. It persists in Firefox 3.6.12
I've noticed the error only appears in the Organizer and only when saving a changed set or saving after deleting a set.
It does indeed save the changed set correctly before crashing.
It is not intermittent and happens every time I perform this save.
The error does not occur in Chrome or Safari.
Examples of the error messages can be found at
http://www.flickr.com/photos/blazer8696/4897580573/
and
http://www.flickr.com/photos/blazer8696/4897656175/

Upgrading to 4.0.1 has corrected this problem.

HUH? Error when saving

We are getting a HUH? Error when saving certain files. Once this error shows up, it will save the document, but will a
lways come up when you resave. It only happens on some documents
We are on a network and share files, but everyone is working in CS4

I have been having this issue on one system. I get an "Unexpected Error cannot save file" when trying to save in any format.
This happens when saving across the network or locally.
(CS3 Vista)
We have been living with this problem since the beginning. We simply do not work on this computer in Illustrator for this reason.

'Font contains bad/Widths' and 'Cannot find/create font' errors when saving pdf as Other Reduced Size PDF

I am exporting .indd files from within Indesign as pdf files, opening in Acrobat Pro XI. I have no trouble creating the initial pdf file, however, when I go to Save Other > Reduced Size PDF I get error messages. Depending on the file, I receive either the message, "The font (Myriad Pro) contains bad/Widths" replacing the text with dots or "Cannot find or create the font (Helvetica) Some characters may not print or display properly" replacing text with dots or boxes.
My confusion is that the file is exporting to pdf from Indesign without error, it is only when I try to Save Other> Reduce Size PDF that the error occurs.
Also, it is only occurring on five out of 120 pages. These same fonts are on other pages and I have no trouble at all with exporting or Reduce Size PDF.
More frustrating is that I have never had this problem occur in all my previous versions of Acrobat using the same process and typefaces.
I am reaching deadline on this and cannot find a solution other than to reload Acrobat 9 and ditch this upgrade.
Any help would be greatly appreciated.

I, too have experienced this issue. Upon export from INDD CS6, I see the error message "The font 'IXWIPX+SourceHanSansSC-Bold' contains bad \Widths."
The only items on the single-page InDesign document I'm trying to export are copies of a one-page PDF (which was extracted from a longer PDF, arranged into a cover format). I can provide all files as necessary. The longer document that the one page came from also experienced an error when I tried to print to Adobe PDF. While I still get a PDF of the cover on export, despite the "bad \widths" message, it won't print from certain machines. I get nothing (not even an empty shell file) from the attempt to print the larger document (where the cover elements came from) to PDF.
I can deal with these issues with a few unorthodox workarounds, but wanted to offer comments or volunteer to help test fixes if possible.
For the record, I'm really not enjoying Acrobat XI. It doesn't seem to have much by way of new features (at least not that I use), and some of those I used most in version X are gone or less functional. Common fonts like Times New Roman are often not found (even though they are definitely on my system); I have a much harder time editing text through the new interface, and I have a few other small gripes—some that I don't have time to get into, others that wouldn't really matter, except that they weren't a problem until I "upgraded." Just sayin'.
Thanks for listening.

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.

Unknown Error When Saving with CS6

I am receiving an unknown error when trying to save my document. I have tried to take off the PDF convertable part, and tried saving it legacy style, but it's still not working. I have a doc open I need to save and won't be able to shut my computer down until I fix this... What could be the issue? Is there a fix for it?
Thank you!!!!!!
Henri

After nearly ripping my eyeballs out and chucking my laptop out the window, I finally fixed the problem!
For some reason I didn't have a CMaps folder in my Adobe - Common Files - Font folder:
C:\Program Files\Common Files\Adobe\Fonts\Reqrd\CMaps
So I made the "CMaps" folder and copied and pasted the files "Identity-H" and "Identity-V" from an "Adobe Reader" CMap folder, and now I can save text in an *.ai file with PDF Compatibility checked.
It's pretty strange Illustrator was working for 2 years without this folder, and now all the sudden it needed it. Also, this is a very obscure fix.
Hopefully the programmers at Adobe have fixed these bugs in newer versions.

Error when saving Crystal report to BW

Hi,
I'm getting an error when save a report to BW (without push to BOE). I received the error messages as following:
This syntax cannot be used for an object name
An error occurred while saving and/or publishing. The return code 220 was returned from the server
c
Please help!
Thanks.
KS

Hi ingo,
thanks for your response.
can you save a report directly to the BOE Server ?
Yes, I can publish the report by "Save as" to BOE.
did you can configure all the publishing in transaction /crystal/rptadmin ?
Yes, I've followed all the steps by links below.. The RPC destination is working.
Publishing part 1
/people/ingo.hilgefort/blog/2008/09/23/businessobjects-and-sap--publishing-of-crystal-reports-part-1-of-3
Publishing part 2
/people/ingo.hilgefort/blog/2008/09/24/businessobjects-and-sap--publishing-of-crystal-reports-part-2-of-3
Publishing part 3
/people/ingo.hilgefort/blog/2008/09/24/businessobjects-and-sap--publishing-of-crystal-reports-part-3-of-3
Still, I received the error as mentioned.
Below is the detailed error after attempt to save the report to BW:
Message no. TK103
Diagnosis
The syntax of the transferred objects is incorrect. R3TR XLWB made this check.
This could be caused by the following:
The object type R3TR XLWB is unknown
The syntax of the object name is incorrect
The object is a component of a system object
System Response
The function terminates.
Procedure
Correct the syntax.
I am not sure what is going wrong. Please help..
thanks.

Error when saving a default format for a date field in 11g

Getting this error when attempting to save the default for a date field in 11g:
The current xml is invalid with the following errors: Bad xml instance! <?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""Retrospectives"."Time Dim"."Two Months Ago""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:custom" customFormat="MMMM dd, yyyy" displayTimeZone=""/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
Line:2, Col:608, Attribute 'displayTimeZone' is not declared for element 'dataFormat'
Thoughts and suggestions?

I have a Support Request open with Oracle right now (it's taking a few weeks to resolve) but here's the update:
OBIEE 10g handles DATE types differently than 11g. Both the support rep and I can't figure out how, but they are different. If you bring the column in as a DATETIME in your Physical Layer you can't save it system-wide, even if you do set a time zone for your account (My Account -> Preferences -> Time Zone). If you bring the column in as DATE you can save it system-wide but you can't display the hours/mins/secs, only the M/D/Y. This has been tested on a 9i and 10g database and produced the same thing on both. The problem never occurred with those same columns using OBIEE 10g.
Oracle support has not fully admitted this as a bug, but the rep working on this SR said this will probably be fixed in the next release- 11.1.1.4, which is due out late Jan/early Feb of this year. He is trying to reproduce this so he can log it as a bug (which we all are hoping for!) so Oracle can address it.
For now, I've found that you are stuck with two options: 1) bring the column in as a DATE, display it system-wide as a saved format, but you can't show the time, and 2) don't save that date value with a system-wide formatting and set it manually on every report you need a custom format (don't forget to set your time zone).
If I hear anything more back from Oracle support I'll update this thread.
Sorry guys, looks like we're all stranded on this one...

Font licensing error when Saving?

Similar Messages

Maybe you are looking for