IPTC/XMP standard for metadata

Does anybody know if iPhoto will ever become compatible with the IPTC/XMP standard for metadata?

No
And if they did they would not say
this is a user to user discussion forum and speculation on future Apple products is expressly forbidden by the TOS that you read and agreed to when you signed up to use these forums
LN

Similar Messages

How About Some Standard Standards For Keyword Hierarchy?

After reading Wolf Eilers post in the "Respect Keyword Hierarchy when importing" thread, I tried his example and exported a RAW file with the "Outdoor>Landscape" example he gave and then re-imported the jpeg. It came back in with Landscape as the parent of Outdoor, that is backwards from what I intended. Go figure.
If LR respects ">" as indicating a parent-child relationship between keywords it is fine with me. However, Microsoft decided to use "/" because there is apparently no XMP standard for keyword hierarchies. Wouldn't it be nice if Adobe, Microsoft, and Apple too got together and set a defacto standard for keyword hierarchies. As it is now, I can create a keyword "Outdoor/Landscape" in LR and have it appear in Vista Photo Gallery with Landscape as a child of Outdoor. However, if re-imported into LR it comes in as "Outdoor/Landscape". Can't we just all get along?

Absolutely no. A completely pointless exercise. As there can be no standard for such a thing. As people have so many, very different ways of filing things. It like suggesting that we all use the same folder tree for filing on our computers. Our relationship to keywords and their meaning will change.
Take Brad Pitt, would you put him under Actor, celebrity or relative. His mum would file him under Son/Family.
What about places. I use UK, Europe, Asia, Africa...as top level domains. Now someone who lives in Japan would have Japan as home and the UK as Europe/UK. Some people may like to file musical acts by city of origin, others by genre, neither is wrong and both are correct for the right person. Being able to do both would be even better.
You just design a heirachy that suits yourself. Adobe just has to find a way of respecting that and allowing you to transfer that heirarchy intact between apps.
Someone else posted this example of heirachy. Which will work well for some, but not for others. Plus, in context of what you ask, remember everyone's family structure is different so how can you possibly have a 'standard' heirachy.
http://www.flickr.com/photo_zoom.gne?id=98612897&size=o
In your example above, I wouldn't use Outdoor and Landscape as Landscape. As for my filing I simply do not have an inside and outside category. I probably wouldn't even have a landscape category either, I would file them under location in a heirachical tree like UK/Wales/West Glamorgan/Gower/Rhosilli/Headland. I may add Landscape as a key word, but would not use it as a category as the heirachy tree above makes more sense to me as I can remember where things are.
I also file everthing by date in my OS as I can remember when I took things reasonably well and that ensures I have a coherent filing system onto which I can apply a database.

XMP Schema for WAV files

Hi,
I am planning to use XMP metadata for WAV files and I would like to create a Schema for the same. I know that that XMP has schemas for other Formats like TIFF and EXIF. If there is a XMP schema for WAV already(probably the Adobe Audition uses it), I would like to use it; else, I have to create a custom XMP WAV schema.

Greetings,
Since a WAVE file is actually a simple RIFF file format, I think it should fit into my proposal for embedding XMP data in RIFF files (I already posted it somewhere else in this forum). (For WAVE schemas, thats another story)...
p.s: I have not had any comment from Adobe on this proposal, either they don't read this forum or they don't care...
Comments?
I have the same proposal for IFF files (AIFF/ILBM etc) if you wish to have it?
Here follows the specification:
Embedding XMP data into IBM-Microsoft RIFF file formats
=====================================================================
This proposal permits adding XMP compatible metadata to standard
RIFF files. A RIFF file is composed of chunks of data; each of
the chunks precedeed by a header giving the type of data that
follows, as well as the length of the data in the chunk. For
more information on the RIFF file format, consult the specification
"Multimedia Programming Interface and Data Specifications 1.0"
Including XMP data in an RIFF compatible file is a matter
of adding a subchunk to the INFO LIST chunk. The subchunk
ID for this type of date shall be "IXMP".
Guidelines for RIFF writers
If the XMP packet is to be used, the software can optionally
write out all other INFO LIST registered (from the standard),
assuming the following mapping:
IRSC dc:creator
ICRD dc:date
ICMT dc:description
ICOP dc:rights
IKEY dc:subject
INAM dc:title
IGNR dc:type
IARL dex:source
In the case where they are written, for better validation by reader
software, the XMP packet should also contain the xmp:MetadataDate
property.
For better portability, and to easily modify the embedded
XMP data, the following guidelines should be followed by
the RIFF writer:
- The XMP packet should contain the full packet signature;
this permits easier searching for tools that do not
understand the RIFF file format.
- The XMP packet should be encoded in UTF-8.
- As specified in the XMP specification, an XMP packet
should be filled with blank spaces for easier updating of
the XMP packet without rewriting the entire file.
A suggested size of an XMP chunk is 4096 or 8192 bytes.
- Only one "IXMP" chunk should be present in the INFO LIST
chunk. Preferrably, there should only be one INFO LIST
chunk per file.
Guidelines for RIFF readers
If an XMP packet is present in an RIFF file, then one of
the following options can be used to retrieve the
metadata from the file:
If the existing metadata chunks are also present,
then, one of the following solutions can be used:
a) Compare the xmp:MetadataDate property with the
file modification date to determine which chunk to use
: either the IXMP subchink or the other info subchunks.
(If the file modification date is greater than
xmp:MetadataDate, it is probably safe to assume that
the standard metadata chunks might have been updated
by software that does not
understand XMP packets).
b) Simply ignore these chunks and use the XMP
packet for the metadata.
c) Simply ignore the XMP chunk , and use the
other chunks for getting the metadata of the file.

Import tags for metadata

It could be useful to have a list of EXIF/filename info tags that can be inserted in a metadata import template to import/export images.
For example the {filename} tag could be expanded in the original filename (DSC002345.NEF) to be inserted in a Notes field on IPTC metadata. Or a {colorspace} tag could be expandede in AdobeRGB or sRGB depending on the camera settings in EXIF. In this way the IPTC fields could be filled with info. Now, as I saw, metadata templates can only contain handwritten data.

This functionality is available in most other import software and it is strange why at least a basic subset isn't present in LR. For example, I usually insert the original filename into the title field in the IPTC/XMP data during import. I can't do this during a LR import. I can't even do it later within LR.
The tokens are already exposed during the import process to handle file renaming, e.g., {filename»}. Why can't they also be available in the metadata templates?
Is this basic capability hidden somewhere under the covers? Has anyone discovered a way to do this?

XMP output for multiple files

Is it possible to generate separate xmp files containing metadata from several images without having to open each one manually? I'd think it could be done using something like a Ps action run via Bridge, but doesn't look like that's possible.
Thanks,
Zolt

Yes it's possible..
Run the following code from ExtendScript Toolkit. Make sure you select the files in Bridge first.
The xmp files will be created on the desktop.
#target bridge
var sels = app.document.selections;
for(var a in sels){
sourceFile = new Thumbnail(sels[a]);
var Name = decodeURI(sourceFile.name).replace(/\.[^\.]+$/, '');
var md = sourceFile.synchronousMetadata;
var outFile = new File("~/desktop/"+Name+".xmp");
outFile.open('w');
outFile.encoding = 'UTF8';
outFile.writeln(md.serialize());
outFile.close();

Standard form metadata adherence

Is the following statement correct?
"For projects that are interested in adhering to standard form metadata, the one and only proper method of retrieving data from an AW is through the Java OLAP API."
For example, imagine a custom program that uses the Java OLAP API to discover the metadata, but then uses a custom OLAP DML program to retrieve the actual data. Does this violate the spirit of the standard? Does adhering to the principles of standard form metadata refer only to the creation and modification of AWs?

YES!
finaly somebody who say the same.
If ORACLE provides OLAP only with database, must make shure that all standards are available, like in relational DB.
It seams that ORACLE OLAP follows:
for each tool we will find a fo...
Regards,

Synchronize Folder - Scan For Metadata Updates

Can anybody explain to me, what exactly is supposed to happen when I am synchronizing folders and have "Scan for metadata updates" checked?
What kind of metadata is searched
(I notice that keywords are not synchronized)
What action is supposed to be taken
(write metadata to image, read metadata into catalog, any prompt before updates?)
The manual isn't really specific about this, and by trying I haven't really found out what to expect.
Thanks for any suggestions.
Beat Gossweiler
Switzerland

Basically, the folder is scanned for new or changed images. The metadata changes will include new or updated IPTC, Keywords, ratings, labels, develop adjustments, which will have been applied in an external app such as Bridge/Camera Raw. If the folder contains new images these will be identified as such. If an image has been removed from the folder but still remains in the catalog you will be notified and given the choice of removing it.
Synchronise Folder does NOT save anything back to the actual files. If you have made a change to a file in Lightroom that change will NOT be applied to the actual file when Sync Folder is run. It reads the folder for externally applied changes/additions/omissions and subject to user choice will update the catalog accordingly.

XMP property for a page object not predefined and no extension schema...

In attempting to make PDF/A-1b files, I get the Preflight error "XMP property for a page object not predefined and no extension schema present."
Every page reports the same Trigger values:
=> Property exists in predefined schema (XMP 2004): is not true
=> Extension schema is present in XMP: is not true
By following the suggestions in the Acrobat 9 Help page "Edit document metadata" I can save existing metadata to an external .xmp file, but I cannot change the XMP metadata to solve the Preflight error.
I would be grateful for suggestions re how to solve the Preflight error.
Thanks,
Raphael

There is still that same problem.
Pictures what needed to converted tot PDF/A
My situation is large JPEG's.
My workaround to print it out with adobe pdf printer with the options
1) papiersource on base of pageformat PDF
2) If needed use adjusted paperformat

Filter or Collection for Metadata State

When trying to save metadata, LR sometimes reports a conflict about a file having been changed by another program or other error. It is almost impossible to track down those conflicts as the only indicator of which images have the problem is the small indicator on the thumbnail.
I would like a filter or collection for metadata states. I am particularly interested in a) conflicts where LR believes the file was changed by another program, b) metadata not yet written to disk, c) any metadata errors.

And since some of these conflicts put the images in a state of constantly flipping between a metadata state of "Up to Date" and "..." and thus producing a memory leak, I too would love to easily isolate these images. If I sort them by edit time this more than likely will find the conflicts (which are completely false by the way since I do not edit or even view the DNG files in any other program) more quickly but the last time it was of no help. I have had to turn off the automatically writing of XMP to stop the memory leak and remember to save after each session.

Xmp specs for "description" field

To whom it may concern (or to whoever may be able and willing to help;-):
In INDD I am able to enter xmp data into the description field as long as i want (which is also not cropped after saving), however the data is cropped to a certain number of cyphers/letters whenever in eported pdfs (no matter what export preset). I googled quite a while to turn up xmp specs regarding this, but could not turn up any. If anyone could tell my, why the cropping occurs or could turn up a workaround for it, i`d be grateful.
Kind regards and thanks ahead,
Aurel

Aurel and Carl,
I'm a little late here, but I want to thank Aurel for posing the questions, and Carl for explaining so much; I particularly appreciate his explaining the metadata consequences of Acrobat's "Save" vs. "Save As", and warning that changes in metadata embedding for CS5 applications [still] do not apply to Acrobat.
On a side issue, Aurel wrote:
> Also this pdf has all metadata visible upon vista explorer right click
> "file properties", which i cannot reproduce for my current files, but
> thats yet another problem. grrr. thanks anyways.
On my Vista64 machines, Explorer loses the PDF tab I see in on my 32-bit machine. However, that tab come back when I run Vista64's 32-bit version of Explorer. I use a one-line batch file with the line "%windir%\SysWOW64\explorer.exe /separate, /root, c:" as discussed in Adobe's Reader forum.
Like Aurel, I'm no programmer. Still, I managed to make a custom XMP panel for IDCS4 for adding PRISM publication metadata to the journal articles I work on (using the generic models in the XMP SDK 4.1). The PRISM metadata is fairly esoteric, but I've also been trying to convince the editors I work with that we should be embedding basic metadata, including Keywords, in PDFs to be made available electronically. Thus I was more than a little surprised to read in one of Carl's post:
> One search engine for journal articles looks as PDF Doc Info
> metadata, most search engines avoid all forms of metadata.
That would seem to fly in the face of WWW folk wisdom (for example, at InDesign Secrets), so I'm must be missing something.
I see XMP SDK 5.1 has been released and I expect to upgrade my CS4 suite one of these days. However, it's tempting to wait until Acrobat's handling of XMP metadata catches up. As things stand now, I'll probably continue to send editors screen grabs to proof custom metadata. Otherwise I'd have to port my modest custom panel to XMP 1 for Acrobat, convince the editors to buy the full version, and then show them how to install the panel -- effort that I assume the next Acrobat will make redundant.
Thanks again,
David

IPTC/XMP Toolkit Wrapper in C#

I wanted an extremely easy C# wrapper for the toolkit. One that would compile in Visual Studio 2005 and 2008 upon install, as well as have a class with simply had property values for each of the IPTC/XMP data. I hired someone to do this and it works beautifully. It's been released in DBGallery, a photo database system (www.grrsystems.com/DBGallery).
If anyone is interested in purchasing this wrapper you may contact me at [email protected]
Regards,
Glenn Rogers, PMP
GRR Systems, Inc.

The XMP Toolkit C# Wrapper mentioned above has been recently updated to:
- Use the XMP Toolkit CS6
- Support additional fields, such as GPS
- Support UTF8
- Includes a sample project which uses .Net 4.0
- Compiles in Visual Studio 2012
Regards,
Glenn Rogers, PMP
Project Manager for DBGallery: Photo Management Database System

I have had adobe creative suit 6 design standard for 2 years and all of the sudden it would not open. I do not have the windows disc anymore however i still have the product code, number and serial number. is there anyway to get my photoshop back?

I have had adobe creative suit 6 design standard for 2 years and all of the sudden it would not open. I do not have the windows disc anymore however i still have the product code, number and serial number. is there anyway to get my photoshop back?

uninstall, clean and reinstall per Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
for the installation file(s):
Downloads available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 12 | 11, 10 | 9, 8, 7
Photoshop Elements: 12 | 11, 10 | 9,8,7
Lightroom: 5.5 (win), 5.5 (mac) | 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5
Contribute: CS5 | CS4, CS3
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

How to sort out error downloading perpetual license of the CS6 Design Standard for MAC: JRun Servlet Error 413 Header Length too Large?

How to sort out error downloading perpetual license of the CS6 Design Standard for MAC: JRun Servlet Error 413 Header Length too Large?
Just bought the perpetual license online - student-teacher version. Received email confirming my eligibility and followed all instructions to a 't', but still got this 413 error message, and cannot continue.
Would anyone be able to help me?
Or how can I get in touch with Adobe themselves?
How do you get to the chat? I bought it with their help, but cannot remember how to get there again. Took me ages to find the chat.
Cheers!!! Thanks a million! Any help is welcome!!!!

Make sure you have cookies enabled and clear your browser's cache before you try downloading. If it continues to present that error try using a different browser.
As far as getting to a chat link goes, it can be hit or miss... Start Here If after selecting relevant responses you are unable to find a solution, choose "Still need help? Contact us." and the chat contact option.

Can i get a new serial number for Adobe CS6 Design Standard for Students and Teachers?

I have had to re-install my Adobe CS6 Design Standard for students and teachers after having problems with my computer (MacBook Pro)
I am wondering if there is a way to access my old serial number from when I originally installed CS6, or do I have to start over again and get a new serial number?
Help is greatly appreciated!!

You normally use the same serial number that you are first issued. If you registered your product when you first installed it then you should be able to find your setial number available thru your Adobe account online.

IPTC/XMP standard for metadata

Similar Messages

Maybe you are looking for