WGM error when saving settings

pop-up error while saving preferences in WGM:
*Error while saving record "user group name":
Error: -14006
setup:
OSX server 10.5.5 OD master on a Xserve.
Bind to AD with kerberos.
It worked fine for some time now, but i noticed the roblem while i was going to edit the managed printer setup by editing the users printer list. When i tried to save i received the pop-up message writen above and i choosed "dont save", suddenly the previous managed printer settings was gone. So i also lost the old users printer list even when i dint save the changes. Now, i can not neither add the old or the new printers. And that goes for several other managed preferences. I can edit Mobile account creating, but not the rules. When i tried to edit the dock, after same error, both dock and login preferences got flushed out ...
Do any of you guys have a similar experience and solution for this problem. I really dont want to reinstall the OD server. ...

Hi Volkan,
I faced same problem when i install my first MacOS X Server on my OD/AC integration implementation server.
If you tryed to add user from AD to OD to manage them, then you want to add some rules to those users. Firstly, you will not add them to Od to manage them. Probably you tryed to add rules to users from AC list. You couldn't apply your rules to user, because of you've got an error as you mentioned your post.
I figured out that problem to create a group on OD. Then added users from AC to this OD group. And then i setted some rules from preferences section of WGM. After all that management rules functioned properly.
I thing that, this method is gonna help you to manage your AD users over OD.
Kind Regards..

Similar Messages

Syntax error when saving settings

Hi,
When I try to save settings in the MCM Admin tool, I get the following error message:
"Unknown error occurred: SyntaxError: Unexpected end of input :: 200"
This message is displayed on every page within the MCM Admin --> Settings section. When every change I try to save, the above message is shown.
However, it seems that the changes are saved, despite the error message. Because when I refresh the admin page (F5), the changed entries are shown.
Does anybody have an idea why the above message is displayed?
Thanks for you efforts!
Regards,
Sander Maes

Hi Karsten,
Sorry for the delay in my answer, somehow I'm not recieving any alerts when this post is updated. .
By hereby the requested UI5 version information:
SAPUI5 Version 1.20.5 .
Hope this helps to analyse the error.
Thanks for the efforts!
Regards,
Sander Maes

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.

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.

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.

Upload Center 2010 error when saving Powerpoint 2010 file to SharePoint 2013

I'm experiencing an issue when attempting to save a Powerpoint 2010 file to our SharePoint 2013 farm. If a user opens the file in Edit mode, when saving the file Upload Center 2010 complains the upload failed, and PowerPoint 2010 displays a message
"Upload Failed The server version of this file was updated by another author" and 2 buttons are displayed "Keep My Version" and "Keep Server Version". This is incorrect though, because I confirmed on the server end
the changes have been made. If a user keeps hitting save, sometimes it won't fail during the upload.
If a user opens a file in Read Only mode, then clicks on the Edit button in Powerpoint 2010 and saves the changes, they are then prompted by the error "Refresh Required This file needs to be refreshed with updates. Click Save to refresh
and retry uploading your changes." Once again this is incorrect, as the changes have already been made in SharePoint.
I've recreated this error on multiple workstations, have tried re-installing Upload Center 2010, and have tried complete repairs of Office 2010. The occur continues to persist. This only occurs with Powerpoint 2010 though, and none of the other
Office 2010 products. I feel this is a bug in Upload Center 2010 with SharePoint 2013, because when I save from PowerPoint 2010 through a WebDAV connection over file explorer, it saves fine without any issue.
Has anyone run into this problem before? Below are some screenshots of the errors.
Here's the error when opening in Edit mode:
Here's the error when opening in Read Only mode, and then clicking on Edit in PowerPoint:

Did you try Library -> Advance settings
Opening Documents in the Browser
Specify whether browser-enabled documents should be opened in the client or browser by default when a user clicks on them. If the client application is unavailable, the document will
always be opened in the browser.
Open in client application

Word 2007: Error when saving file that contains equations

Using Microsoft Word 2007, version 12.0.6425.1000 with Service Pack 2
I am a High School Math teacher, and when working on a document that contains a number of math equations. When I try to save the document, Word refuses to save. It displays the following error: "A file error has occurred. <filename>. OK",
and I am unable to save the file.
Reading the forum, I have found this to be a very common issue going back to 2009, but I have not seen a definitive solution or patch.
I have found a workaround:
Creat a new document
Copy and paste from the corrupted doc each page, saving the new document after each page
Until I hit the error, then I know the page that has the issue, and can usually narrow it down to a specific math equation. Nothing fancy just some basic math.
Manually rewrite the equation in the new document and it will successfully save.
But the issue has been occurring more and more frequently now and it is becoming very frustrating. Any help would be greatly appreciated!

There has been a long time known issue with the equation editor. it causes document corruption by "losing" XML tags.
Apparently fixes for some causes of these problems have been rolled out in Windows updates. But the problem still exists. You've got it easy. A lot of people running into this problem are students working on documents, like a thesis, that is on a short
deadline ...
One identified cause of these problems is editing equations
after you created them. DON'T DO THAT!
If you have to change an existing equation, create a new correct one and delete the old one.
Simpler fix. Don't use Word (or Office) for creating equations. Find some other product, like a pencil.
Over in the "Answers" forum there are a couple volunteers, Tony Jollans and Jeeped
, who have been manually fixing this type of error if you post a new question or add a reply to one of the ongoing discussions on this issue.
Sorry.
If you want to invest the time to figure out what your error looks like you may be able to come up with a fix other than copy /paste method.
Can't open Word File because of end tag/start tag mismatch error... XML Tag
- XML Error – Fix It tool - “The name in the end tag of the element must match the element type in the start tag”
This error is caused when Word either “forgets” to write an XML tag, or writes them in the wrong order.
Tony Jolans was the first person that I heard of with home made tool to fix the problem. Now MS has released a Fix It for one specific variation of the problem.
If the tools don’t fix your problem, the file will have to be fixed manually, repairing the tag order.
The Fix It article notes that the document is still in a fragile state. You have to do some addition fixing to avoid repeats of the problem.
https://blogs.technet.com/b/wordonenotesupport/archive/2011/03/24/error-when-opening-a-word-2007-or-2010-document.aspx
http://support.microsoft.com/kb/2528942- FIX IT
This fix it will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied.
Preventative suggestions
<snip Jeeped>
I don't think that anyone can completely stop editing equations, but pre-planning them should avoid unnecessary edits.
While I have no concrete, reproducible evidence that editing equations is a cause, I have made these empirical observations:
I cannot state precisely what many of the DOCX XML tags do, but basic XML syntax rules would suggest that code like:   <m:oMath><m:e><m:ctrlPr/></m:e></m:oMath>
... does nothing at all since it closes everything it opens and offers no content. It looks to me that this is a result of deleting one or more characters from an equation.
While Word 2010 reports these as a problem at: Line: 2 Column: 0 ... Word 2007 will still report the actual position, e.g.:
Line: 2 Column: 2726981 I keep a copy of Word 2007 side-by-side Word 2010 for no other purpose. It's the only Office 2007 program on my computer. This seems like it is actually a step backwards from a resolution since Word 2010 no longer seems
to be able to parse its own error.
Whether the syntax is truly useless and non-effective for any intent or purpose is actually beside the point. The syntax passes conformity tests and the DOCX
should launch. Why an 85 page document is 'broken' due to a few empty XML formatting tags while retaining legal syntax structure is beyond me.
I try to pass along the area that the problem was in and several times people have remarked that the area I report was the place they were last making modifications/deletions to equations (not additions) when the no-load corruption
occurred.
When no indication from the OP is offered on what was worked on last, the Line: 2 Column: 0 corruption often comes within a formula at the very end of the unfinished Word/Document.xml file and it may be inferred
that this was the last place being worked upon.
The corrupt DOCX files I've worked on are very commonly at the last stages of development with a large complex document. While there couldn't be a worse time for a corruption to appear, it would seem that small edits to existing content are causing
it and not large scale new content generation.
Not one of these points is a definitive 'smoking gun', but put together they seem to indicate
formula editing and not formula writing as a cause for the Line: 2 Column: 0 corruption. If it looks like a duck and quacks like a duck, it is most often a duck.
</snip>
Copy “True Autosave Macros for Office” to this place in reply
Let me fix it myself
If you are familiar with editing XML, you can try to fix the problem yourself by correcting the sequence of the mismatched oMath tags in the document. See the following example:
Incorrect tags:
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
<m:oMath>
</mc:AlternateContent>
</m:oMath>
Correct tags:
<m:oMath>
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
</mc:AlternateContent>
</m:oMath>
Note: You will have to use an application such as Notepad to edit the XML.
Manual Technique
<snip> A DOCX document is actually a .ZIP file that contains many internal components. There is an internal folder called word which will always contain a document.xml file. This file is the basis of the document's layout
and content.
Assuming that the DOCX archive structure has not been corrupted, it can be opened in an archive utility. I use
WinRAR for this. Once opened in
WinRAR, you can drill down into the
word folder and see the document.xml file. I use
Notepad++ as a text editing tool and have the .xml file extension associated with this program so i can simply double-click
document.xml in WinRAR to open an editing session.
Notepad++ has cursor positioning in the right-hand side of the status bar and finding the position of the error (supplied by a failed open in Word) is pretty straightforward. I look for empty formatting
tags first and only remove content if removing empty tags does not allow the document to be opened. I try to note existing content in the area that I make modifications in order that I can supply position reference information to the owner of the DOCX.
When editing, I assume the philosophy that kess is more. My target is to get the document to open in Word with as little modification as possible and let the original owner of the DOCX make any necessary adjustments.
I should mention that after making a change to word/document.xml you need to save it in
Notepad++ then go to
WinRAR and acknowledge that you want to update the file in the DOCX archive. Once the archive is updated, you can attempt to open the DOCX in Word to see if your efforts are successful.
WinRAR
Notepad++
</snip>
Further Fixes
The Fix it solution in this article should let you recover your Word document. However, the symptoms will reappear when you make any further edits to the document unless the core problem in the structure of the document is resolved.
To try to correct the core problem, follow one of these workarounds:
Install Office 2010 Service Pack 1
Office 2010 Service Pack 1 resolves this issue for new files. It will also prevent the problem from recurring with any files that were recovered with the Fix it solution in this article.
To download Office 2010 Service Pack 1, follow the steps provided in this Microsoft knowledge base article:
2460049 - Description of Office 2010 SP1
Grouping Objects
The steps provided work best under Word 2010:
After you open the recovered document, turn on the Selection pane. This can be found in the
Home tab of the ribbon. The editing group of the
Home tab has a dropdown button named Select.
Click the Select button, and then click
Selection Pane...
Press the Ctrl button on your keyboard and then click each text box in the selection pane.
Click the Group button under the Format tab. This will group all the objects together.
As soon as you have all objects grouped on each page, save the document under a new name.
Save the document in the .RTF file format
The steps provided work for both Word 2007 and Word 2010:
After you open the recovered document, click File and select
Save (for Word 2007 click the Office button and select
Save As)
In the Save As dialog box, click "Save as type:" dropdown and select
Rich Text format (*.rtf).
Click Save.
Click to view this
blog for more information about this issue.
Bonus tip: Win7 Win8 Math Equation Input Panel / Math input Panel
http://www.lytebyte.com/2009/07/24/guide-to-math-input-panel-in-windows-7/
http://www.7tutorials.com/windows-7s-tablet-input-panel-text-entry-and-handwriting-recognition
http://www.7tutorials.com/training-tablet-input-panel-work-even-better
http://www.7tutorials.com/do-math-easy-way-math-input-panel
Not an answer to the problem, just a bonus that may make it easier to input formula’s in Win7.
Here’s another one of those didn’t-know-it-existed-until-I-clicked-it-by-accident tools in Win7. It’s called the
Math Input Panel.
To access it, simply click Start, and in the Search Box that appears above, type in
Math Input Panel.
The Window should look like this:
Let the fine folks at Microsoft explain what it’s used for:
“Math Input Panel uses the math recognizer that’s built into Win7 to recognize handwritten math expressions. You can then insert the recognized math into a word-processing or computational program. “
Tony Jolan’s Automatic Fix
Download http://www.wordarticles.com/temp/Rebuilder.dotm Microsoft Office Word Macro-Enabled Template (.dotm) and open it.
Click Options button on the Security warning and select Enable this content.
Click the Broken Documents tab at the far right of the ribbon.
Click the Rebuild button in the left-hand side
Locate and open your corrupt document in the file open dialog.
That's it. The process will repair your document if possible and create a new document with (Rebuilt)
appended to the filename. Be patient as it may take a few minutes. If a repair is not possible, you can then post to a public file area and someone here can attempt a manual repair.
Manual Fix
XML Maker V1.1 is free. It will allow you to open the document.xml file and edit it. It also marks errors and warnings.
I just didn’t have much luck working with it.
A poster used XML Maker V2.1 (US$125, 30day free trial, enough for average person to fix a file)
Notepad ++ is a good, free editor for this type of task
Make a copy of the file
Rename the copy from DOCX to ZIP
Open … .ZIP/word/document.xml in notepad
Copy the contents of the file to clipboard
Open Word
Paste a copy of the copied XML into Word
(optional) the XML is one long string too hard to read, you can replace some tags, with that tag plus a para mark to break up the text to make it more people readable.
Open an XML validator, ie this site on the internet:
http://www.w3schools.com/xml/xml_validator.asp
Paste another copy of the XML into the “Syntax Check Your XML” input window
Click on “validate” button
Copy the missing tag, ie </mc:Fallback> (yours will be different)
Return to word Find: mc:Fallback> (without the </ so you find both open and closing tags).
Repeat find until you hit 2 open tags in a row. Then you just have to figure out where to put the closing tag between them.
Look for other tags before and after a proper closing tag so you can match the problem area to a good area.
Discussion by many affected people, a couple in discussions are also fixing problem if Tony’s fix doesn’t work
http://social.answers.microsoft.com/Forums/en-US/wordcreate/thread/581159d0-9ebc-4522-b30c-53e33e8268e1
Document Recovery
http://www.wordarticles.com/Shorts/Corruption/Formats.php
This page has the most readable description of Word file structures, DOC and DOCX, I have seen so far
The logical structure of a Word 97‑2003 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 97‑2003 (.doc) format document:
MyDocument.doc
1Table
*CompObj
Word Document
*SummaryInformation
*DocumentSummaryInformation
The physical structure of the complete file bears little relation to the logical structure; it is, again, of a proprietary design, a compound, or structured storage, file. Briefly, and loosely, the separate logical elements of the file are broken up into
blocks; these blocks are treated as individual units, which units are then organised without regard for their logical arrangement, and catalogued, catalogue and organisation detail being held alongside the blocks themselves, to enable recombination into logical
components when necessary.
Just to give you a flavour, here are some views of three small parts of such a document, viewed in a hex editor:
Views of a Word 97-2003 format Document
The logical structure of a Word 2007 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 2007 (.docx) format:
MyDocument.docx
_rels
rels
docProps
app.xml
core.xml
word
_rels
document.xml.rels
theme
theme1.xml
document.xml
settings.xml
fontTable.xml
webSettings.xml
styles.xml
[Content_Types].xml
As briefly as before, the [Content_Types] file and the _rels folders, along with the subordinate files therein, contain information about the logical structure, and the two files in the docProps folder contain much the same as the two Information files
in the old format. The document.xml element within the word folder holds the bulk of the document content and the other files within that same folder hold formatting details.
So, you might say, the internal structure of a document has changed a little, so what? There are, however, other changes that make a bigger difference. The first is that, although both logical formats are conceptually similar, they are wrapped up in
completely different ways to make a single file. Instead of the proprietary physical structure used for Word 97‑2003 format documents, a fairly standard, and open, Zip Archive format is used for Word 2007 format documents. The second change is that instead
of using obscure binary codes, everything in Word 2007 format documents, well almost everything, is held in XML format.
All data held as XML? In a standard Zip Package? It should be much easier to work with, then? Judge for yourself; here are some views of parts of a Word 2007 format document taken from a hex editor:
Views of a Word 2007 format Document
FreeFileViewer – reads 100+ text, Office, audio, video format file types – Can open some XML tag error files
http://www.freefileviewer.com/formats.html
Can't open Word file due to undeclared prefix, Location: Part: /word/document.xml, Line:91, Column: 49921
The most likely cause of your particular problem is that you are missing a
schema prefix reference within the opening <document ...> XML tag (usually the second one). Different
schema references are required for various types of specialty content. Here is a sample opening <document ...> tag with a large number of various schema prefix codes. If I remove one or two of these, i can reproduce
your error message.
<w:document xmlns:ve="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" xmlns:m="http://schemas.openxmlformats.org/officeDocument/2006/math"
xmlns:v="urn:schemas-microsoft-com:vml" xmlns:wp="http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" xmlns:wne="http://schemas.microsoft.com/office/word/2006/wordml">
It's impossible to blindly say exactly what you are missing but if you post an unadulterated copy of your document to a public file area (as noted above) and post the location back here, someone may be able to help. If you are going to go this route, send
a copy that has not already been subjected to repair attempts.
FWIW, while it may be hard to determine exactly which schema you may be missing, I do not believe that having extras causes any problems.
BTW, you don't actually have to rename the DOCX file extension if you have an archiving program. I use WinRAR and simply
<right-click>, Open With... to expose the archive.

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.

WGM error when saving settings

Similar Messages

Maybe you are looking for