Unsupported character

Hi Guru!
I have a big problem whit a XI graphic-mapping in scenario File -> XI -> IDOC.
Sometimes in my files-data are present specials character, example °.
In these case the mapping don't work and in trace I find error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: b0(:main:, row:209, col:37) at ....
Someone have a suggestion?
Thanks
Alex

Hi Alessandro
You will have to use the ascii representation for special characters. In your case it will be,
°
So your input file should use the above value instead of °
cheers
Sameer

Similar Messages

Error in CBS:Unsupported character: 3f

hi all,
   We've got a serious problem:when I activate an active(create a model,and add some model data types),an error is shown,the whole error is like this,basically it talks about"Unsupported character: 3f" in xlf file.
LoadException: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 3f(file:F:/usr/sap/EPL/JC00/j2ee/cluster/server0/temp/CBS/35/.B/132/DCs/com.htso/dev/somain/_comp/src/packages/com/htso/model/types/Gedatum.dtsimpletype.xlf, row:22, col:119)
[System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:74)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java:693)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java:636)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:217)
[System.err]      at com.sap.dictionary.designtime.DtHelper.check(DtHelper.java:244)
[System.err]      at com.sap.dictionary.designtime.DtSimpleTypeExpanded.localCheck(DtSimpleTypeExpanded.java:381)
[System.err]      at com.sap.dictionary.designtime.DtSimpleTypeExpanded.add(DtSimpleTypeExpanded.java:599)
[System.err]      at com.sap.dictionary.designtime.DtSimpleTypeExpanded.add(DtSimpleTypeExpanded.java:591)
[System.err]      at com.sap.dictionary.designtime.DtSimpleTypeExpanded.expand(DtSimpleTypeExpanded.java:153)
[System.err]      at com.sap.dictionary.designtime.DtSimpleTypeExpanded.<init>(DtSimpleTypeExpanded.java:101)
[System.err]      at com.sap.dictionary.tools.generation.Generation.generatePersistentSimpleType(Generation.java:398)
[System.err]      at com.sap.dictionary.tools.generation.console.GenerationConsole.generate(GenerationConsole.java:148)
[System.err]      at com.sap.dictionary.generation.ant.GenerationAnt.main(GenerationAnt.java:47)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
[System.err]      at com.sap.dictionary.generation.ant.DDGenAntTask.execute(DDGenAntTask.java:219)
[System.err]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[System.err]      at org.apache.tools.ant.Task.perform(Task.java:364)
[System.err]      at org.apache.tools.ant.Target.execute(Target.java:341)
[System.err]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
[System.err]      at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[System.err]      at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:111)
[System.err]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:62)
[System.err]      at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:222)
[System.err]      at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:199)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
[System.err]      at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:112)
[System.err]      at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:44)
[System.err]      at com.sap.tc.buildtool.PluginHandler1.handlePluginCommunication(PluginHandler1.java:111)
[System.err]      at com.sap.tc.buildtool.PluginHandler1.execute(PluginHandler1.java:56)
[System.err]      at com.sap.tc.buildtool.PluginHandler1.build(PluginHandler1.java:50)
[System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:111)
[System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
[System.err]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
[System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
[System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
[System.err] Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 3f(file:F:/usr/sap/EPL/JC00/j2ee/cluster/server0/temp/CBS/35/.B/132/DCs/com.htso/dev/somain/_comp/src/packages/com/htso/model/types/Gedatum.dtsimpletype.xlf, row:22, col:119)(file:F:/usr/sap/EPL/JC00/j2ee/cluster/server0/temp/CBS/35/.B/132/DCs/com.htso/dev/somain/_comp/src/packages/com/htso/model/types/Gedatum.dtsimpletype.xlf, row=22, col=119) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 3f(file:F:/usr/sap/EPL/JC00/j2ee/cluster/server0/temp/CBS/35/.B/132/DCs/com.htso/dev/somain/_comp/src/packages/com/htso/model/types/Gedatum.dtsimpletype.xlf, row:22, col:119)
[System.err]      at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:145)
[System.err]      at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
[System.err]      at com.sap.s2x.S2XDocument.loadRSX(S2XDocument.java:4213)
[System.err]      at com.sap.s2x.S2XDocument.loadRSX(S2XDocument.java:4094)
[System.err]      at com.sap.s2x.S2XDocument.<init>(S2XDocument.java:256)
[System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:42)
[System.err]      ... 47 more
[System.err] Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 3f(file:F:/usr/sap/EPL/JC00/j2ee/cluster/server0/temp/CBS/35/.B/132/DCs/com.htso/dev/somain/_comp/src/packages/com/htso/model/types/Gedatum.dtsimpletype.xlf, row:22, col:119)
[System.err]      at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
[System.err]      at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205)
[System.err]      at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205)
[System.err]      at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
[System.err]      at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.loadLastChar(AdvancedXMLStreamReader.java:108)
[System.err]      at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.scanByte(AdvancedXMLStreamReader.java:162)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1801)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843)
[System.err]      at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
[System.err]      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
[System.err]      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:204)
[System.err]      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
[System.err]      at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
[System.err]      at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:339)
[System.err]      at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
[System.err]      ... 52 more
I don't know how it happens,and how to solve this.
Can somebody help me? points will be rewarded.Thank you~!
Our portal and NWDI is sp11.
(but component com.sap.portal.connectors.ws is only 7.0010,does this matter?)
Best Regards,
delma
Edited by: delma ma on Jun 16, 2008 1:50 PM
Edited by: delma ma on Jun 16, 2008 1:52 PM

Hi,
Thank you for your reply.
Firstly,The all three scas are imported into the track(or the errors are much more....)
our NWDS is SP12.
And yesterday i removed the model and recreate one.And i found the NWDI is abnormal.(it shows error that all java files and xlf filrs are readonly.),and some automatically created files show compile error.
I do think NWDI is abnormal.but i cannot find where is.
Best regards,
delma

ORA-01482: unsupported character set

Hello,
does anybody have an experience with error message "ORA-01482: unsupported character set" which is displayed instead of the content of page region, which is of type select SQL.
The strange thing with this is that e.g. LOVs are rendered/displayed without such error message and they are also of the same type SQL select - no mater how complex.
- APEX version 3.0.1 in Database version 9.2.0.7.
Thank you for helpful info.
Petr

What version of Oracle XE did you install?
-Oracle Database 10g Express Edition (Western European) Single-byte LATIN1 database for Western European language storage.
-Oracle Database 10g Express Edition (Universal) Multi-byte Unicode database for all language deployment.
Give us an example of a query that goes wrong.
Regards, Marc

RH10 - HTML Compiler Error (Unsupported Character)

I'm on RH10, working on a project that I've been working on for several months now, and suddenly I'm having a serious problem. When compile the project as HTML help, I'm receiving the following error message at about 80% complete:
"HTML Help settings has insupported characters for the chosen language. Do you want to continue..."
I've seen a couple of topics in the forums that mention this error, but they seem to be dealing with foreign language settings. In my case, the entire project is in English and does not use any special characters that I know of.
I have WebHelp set as my primary output, but I need to create a CHM file of this project as well.
WebHelp seems to compile without a problem. I only see this error when I attempt to complie as HTML help.
"Warning: The size of stop file has to be limited in 512 bytes.
Warning: Data loss in converting Index data using choosen language.
C:\AMX Docs\AMX-CDI\!SSL!\Microsoft_HTML_Help\!chm_tmp_folder_0\AMX-CDI.hhp
Microsoft HTML Help Compiler 4.74.8702
Compiling c:\AMX Docs\AMX-CDI\!SSL!\Microsoft_HTML_Help\AMX-CDI.chm
AMX-CDI.hhc
Fatal Error: Unexpected error from Microsoft HTML compiler.
Finished compiling HTMLHELP in 138 sec(s)
Compilation complete."
I have tried the tried and true trick of deleting the CPD file, but that hasn't changed anything...
Also tried switching the project language setting from "default" to "English (US)", that didn't affect anything either...
It seems like RH is trying to deal with foreign language characters, but again I am not aware of any ni my project.
Any ideas would be greatly appreciated - thanks!
-lc

Hi LC,
First of all, can you please check the file name of all your topics and verify if you have any special character in the file name or not?
Before trying out any of the steps given below, can you try generating your SSL output on a New Folder at C:/ root (C:/NewFolder) and see if that works, I noticed that in your path you have a special character "-" by the name . (C:\AMX Docs\AMX-CDI\!SSL!\Microsoft_HTML_Help\!chm_tmp_folder_0\AMX-CDI.hhp)
1)      C:\Users\UserName\AppData\Roaming\Microsoft\HTML Help\
Rename the hh.dat file and then try regeneration of help.
2)      Create a New Folder inside the C: Drive (root) and publish your CHM to this New Folder rather than the default path of project inside !SSL! The key here is the CHM should not be buried under multi-level folder hierarchy.
3)      Try running RoboHelp In Admin Mode – Create a new SSL as Microsoft HTML help, set it as Default SSL and Then Regenerate the output.
4)      Make sure the CHM is not generate on network, as it requires Windows registries to generate the CHM< using Microsoft CHM Engine, it is better that you have admin rights as well as work locally, else you might get a “Failed to Navigate data”
Let me know if that persists.
Thanks,
Anjaneai

Unsported character error in message mapping

I use a sender mail adapter to read an xml and then map it to another message type. Most of the time, it's ok. But when there are some special German character such as ö ä ß, then I get the "unsuported character" error.
Anyone could help?
thanks!
com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more

As the mail server provides the correct encoding, the MessageTransformBean does the conversion to UTF-8.
If the encoding was not set by the mail server, then the MessageTransformBean would only set the content type, but not do any conversion.
When you are not sure, if the content type is by the mail server, you can apply the MessageTransformBean twice: First with iso-8859-1, second with UTF-8
I am not sure, why the mapping tool cannot do the conversion, but I think this is because the content type is not application/xml. But this is only a guess.
What happens, when you only apply the MessageTransformBean, but do not change the XML encoding?

Unsupported Media Type

Hi all,
I've created a OData service formulated by the following metadata:
<edmx:Edmx Version="1.0" xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx">
<edmx:DataServices m:DataServiceVersion="2.0" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<Schema Namespace="HanaODataTests.bookstore" xmlns="http://schemas.microsoft.com/ado/2008/09/edm" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<EntityType Name="booksType">
<Key>
<PropertyRef Name="title"/>
</Key>
<Property MaxLength="100" Name="title" Nullable="false" Type="Edm.String"/>
<Property MaxLength="100" Name="ISBN" Type="Edm.String"/>
<Property Name="editions" Type="Edm.Int32"/>
<Property MaxLength="100" Name="author.name" Type="Edm.String"/>
<Property Name="author.birth" Type="Edm.DateTime"/>
<NavigationProperty FromRole="booksDependent" Name="Author" Relationship="HanaODataTests.bookstore.WroteType" ToRole="writersPrincipal"/>
</EntityType>
<EntityType Name="writersType">
<Key>
<PropertyRef Name="name"/>
<PropertyRef Name="birth"/>
</Key>
<Property MaxLength="100" Name="name" Nullable="false" Type="Edm.String"/>
<Property Name="birth" Nullable="false" Type="Edm.DateTime"/>
<Property MaxLength="100" Name="title.title" Type="Edm.String"/>
<NavigationProperty FromRole="writersPrincipal" Name="Titles" Relationship="HanaODataTests.bookstore.WroteType" ToRole="booksDependent"/>
</EntityType>
<Association Name="WroteType">
<End Multiplicity="1" Role="writersPrincipal" Type="HanaODataTests.bookstore.writersType"/>
<End Multiplicity="*" Role="booksDependent" Type="HanaODataTests.bookstore.booksType"/>
<ReferentialConstraint>
<Principal Role="writersPrincipal">
<PropertyRef Name="name"/>
</Principal>
<Dependent Role="booksDependent">
<PropertyRef Name="title"/>
</Dependent>
</ReferentialConstraint>
</Association>
<EntityContainer Name="bookstore" m:IsDefaultEntityContainer="true">
<EntitySet EntityType="HanaODataTests.bookstore.booksType" Name="books"/>
<EntitySet EntityType="HanaODataTests.bookstore.writersType" Name="writers"/>
<AssociationSet Association="HanaODataTests.bookstore.WroteType" Name="Wrote">
<End EntitySet="writers" Role="writersPrincipal"/>
<End EntitySet="books" Role="booksDependent"/>
</AssociationSet>
</EntityContainer>
</Schema>
</edmx:DataServices>
</edmx:Edmx>
and to insert books and writers through a POST request is working but now I'm trying create a link between two entities. For that, I wrote the following request:
POST /HanaODataTests/bookstore.xsodata/writers(name='Test',birth=datetime'2014-07-11T00:00:00.0000000')/$links/Titles HTTP/1.1
Host: xxxxxxxxxx
DataServiceVersion: 1.0
MaxDataServiceVersion: 2.0
Content-Type: application/xml
<uri xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices">
http://xxxxxxx/HanaODataTests/bookstore.xsodata/books('HAPI%20Hana%20Integration%20Test%20Volume%201')
</uri>
and I always get as a response:
<?xml version="1.0" encoding="utf-8" standalone="yes"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message xml:lang="en-US">Unsupported character set: The entity of the request is in a format not supported by the requested resource for the requested method.</message></error>
Or sometimes the response is that the statement cannot be a POST statement because Titles are not an entity.
Anyone have any idea what I'm doing wrong?
Thank you for your attention
Pablo

But to insert a book for example, which is a POST operation, it's working using ATOM format.
I've updated my statement:
POST /HOData/library.xsodata/writers(name='Robert%20Kingst',birth=datetime'2008-04-08T00:00:00.0000000')/$links/Titles HTTP/1.1
Host: xxxxxxx
DataServiceVersion: 1.0
MaxDataServiceVersion: 2.0
Content-Type: application/atom+xml
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<uri xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices">
http://xxxx/HOData/library.xsodata/books('HAPI%20Hana%20Integration%20Test%20Volume%201')
</uri>
only indicating what kind of content it is: Content-Type: application/atom+xml and now the response change for:
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code /><message xml:lang="en-US"><corrupt message></message></error>
Is this arising becouse of the incompatibility of format?
And other question is, if the format had compatibility, my request would be right?
Pablo

SOAP Adapter - Error because of special character (u00FC - Umlaut) in payload

Hello,
We have a SOAP sync scenario.
SAP -> PI 7.0 -> 3rd Party system
We have a special character (ü - Umlaut) as part of the payload.
When the message enters message pipeline in PI, I can see the payload XML till message branching step.
From Message mapping step, i get the message - "The XML page cannot be displayed. An invalid character was found in text content" in SXMB_MONI.
In communication channel monitoring, I see the following error:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)
But, when I pass the same message(with special character) to the 3rd party system using SOAP UI, i get a valid response back.
So, what is going wrong in PI?
Thanks,
Chandra

Hi Gouri,
you are right. My message is successful in SXMB_MONI, and the error is coming from comm channel monitoring with deliverin to target.
My sender is a proxy, and we can not specify any encoding in proxy sender.
I did not specify any encoding in SOAP Receiver aswell.
This is the sequence in comm channel monitoring:
Success: Delivering to channel: CI_SOAP_Receiver_Sync
Success: MP: Entering module processor
Success: MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success: SOAP: request message entering the adapter with user J2EE_GUEST
Error: SOAP: call failed: java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
So, what can i do to fix this?
Thanks,
Chandra
Edited by: Chandra Sekhar H on Mar 3, 2011 12:25 PM

SUPPORT FOR euro WE8ISO8859P15 CHARACTER SET

Hi,
I cannot run Portal home page after 9iAS release 2 installation on Sun Solaris.
On both nodes (infrastructure and middle tier) and in portal DAD I have NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15.
Is it possible to run portal with this character set?
This is the error message:
Error: The servlet produced the following error stack. java.io.IOException: Unsupported character encoding: "ISO-8859-15"
     at oracle.webdb.page.BaseContentRequest.getResponseJavaEncoding(Unknown Source)
     at oracle.webdb.page.BaseContentRequest.getReader(Unknown Source)
     at oracle.webdb.page.PageBuilder.getMetaData(Unknown Source)
     at oracle.webdb.page.PageBuilder.process(Unknown Source)
     at oracle.webdb.page.ParallelServlet.doGet(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:269)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
     at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
Best regards,
Zoran

Hi
You dont need anything special, however the JVM you use must support the encoding you want (unless you are going with a unicode flavor like UTF-8 which all JVM's support). The rest of the i18n stuff like ResourceBundles for messages, date currency formats are handled in your code anyway.
regards
deepak

CHARACTER SET 문제에 대한 CHECK LIST

제품 : ORACLE SERVER
작성날짜 : 1998-04-13
환경 변수들이 모두 올바른 데도 character set 에 문제가 있는 경우
=============================================================
Oracle version 7.2 에서부터 사용되는 환경변수인 ORA_NLS 를 잘못 setting
하면, 다음과 같은 character set 문제가 발생할 수 있습니다.
server version 환경변수
============== =========
7.2 ORA_NLS
7.3 ORA_NLS32
8.0 ORA_NLS33
즉, 다음의 경우에 위처럼 환경 변수 ORA_NLS 가 DB version 과 일치하는
지를 확인해야 합니다.
1) US7ASCII 에서 KO16KSC5601 로 character set 을 변경하기 전에
변경이 되는지 확인하는 조회에서 다음과 같은 에러 발생하는 경우
select convert('a','KO16KSC5601','US7ASCII') from dual;
Ora-1482 "unsupported character set"
2) props$, v$nls_parameters 의 character set 이 서로 다른 값을
가질 경우
3) v$nls_valid_values 에 default value 만 조회되는 경우
(즉, select count(*) from v$nls_valid_values; 의 결과가
4 인 경우 ORA_NLS 가 setting 되어 있지 않기 때문)
4) table 생성시에 ora-911 "invalid character",
ora-904 "invalid column name" 빌생하는 경우
5) NLS_LANG 을 올바로 setting 하였는 데도, 한글이 ??? 로 나오는 경우
$ env | grep ORA_NLS
ORA_NLS=$ORACLE_HOME/ocommon/nls/admin/data
$ cd $ORA_NLS
ls -l boot
-rw-r--r-- 1 rctest72 dba 13572 Dec 2 1995 lx0boot.d
-rw-r--r-- 1 rctest72 dba 13572 Dec 2 1995 lx1boot.d
이 두개의 화일이 ORA_NLS 디렉토리에 있어야 합니다.
(version 에 따라 size 는 다를 수 있습니다.)
해결 방법
========
만약,ORA_NLS(ORA_NLS32,ORA_NLS33) 이 setting 되지 않았거나,rdbms version
과 맞지 않을 경우 다시 수정한 후에 restartup 하면 이와 관련된 문제는
해결됩니다.
(특정 OS, Ticom 의 경우 OS 를 rebooting 해야 하는 경우도 있습니다.)
해결 방법은 ORA_NLS 를 정상적으로 setting 한 후에 restartup 하면,
v$nls_valid_values 에 KO16KSC5601 이 조회되었고, 한글 테이블명이나
컬럼명이 가능해지고, dictionary 도 KO16KSC5601 로 일치하게 됩니다.
다음의 CASE1, CASE2 를 통해 이 환경 변수가 DB 에 미치는 영향을
확인할 수 있습니다.
CASE1
=====
위의 lx0boot.d, lx1boot.d 화일을 ACCESS 할 수 있을 때, 기동된 instance 의
dictionary를 조회하면, 많이 사용하는 KO16KSC5601, US7ASCII 등의 character
set 을 조회할 수 있습니다.
SQLDBA> select * from v$nls_valid_values;
313 rows selected.
SQLDBA> select * from v$nls_valid_values where value='KO16KSC5601';
PARAMETER VALUE
CHARACTERSET KO16KSC5601
1 row selected.
; 즉, total 313 row 가 있고 그 중에 KO16KSC5601,US7ASCII 도 있음
CASE2
=====
그러나, lx0boot.d, lx1boot.d 화일을 ACCESS 할 수 없을 때, 기동된
instance 의 dictionary 를 조회하면, default value 들만 조회됩니다.
SQLDBA> select * from v$nls_valid_values;
PARAMETER VALUE
LANGUAGE AMERICAN
TERRITORY AMERICA
CHARACTERSET US7ASCII
SORT BINARY
4 rows selected.
;즉, lx0boot.d, lx1boot.d 를 access 할 수 없을 경우에는 위의 US7ASCII 만
지원합니다.

Hi Amos,
It should work but you will need to use a Unicode font. Try setting your field fonts in CR to MS Ariel Unicode and test again.
Thank you
Don

Error While running a J2EE application on J2EE Engine.

Hi Guys,
I have a Ear file which I deployed successfully .Now in some jsp pages its throwing some exception.
. I think its related to Sap parser Can any anyone Resolve this?
Application error occurs during request processing.
Internal error while parsing JSP page [D:/usr/sap/JDV/JC00/j2ee/cluster/server0/apps/JavaEE/SP/servlet_jsp/SP/root/Sample.jsp].
*Details:com.sap.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [http://java.sun.com/jsf/core]:*
+[com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a0(:main:, row:272, col:25)(:main:, row=272, col=25) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a0(:main:, row:272, col:25)].+
Exception id: [000C29A9E97100650000005B00000930000455FCF34E1452]
Edited by: Somil Agarwal on Sep 3, 2008 2:33 PM
Edited by: Somil Agarwal on Sep 3, 2008 2:34 PM

Hi Somil,
I've just had this same error message, and it was because I had a bogus character in my JSP sources. I'd cut-and-pasted the text from a Word document, and it included the "registered trademark" sign (an R in a circle) as a single character. This worked in my test environment, but not in my production environment (where presumably the default encoding is different). I replaced the character with the equivalent HTML entity &reg; (ie. the five characters & r e g ; ) and it all worked.
Have a look through the offending JSPs and see whether you have any characters that might be incompatible with your default encoding (anything that isn't plain old 7-bit ASCII is potentially a problem). Change them to HTML entities and you should be fine.
Hope this helps,
Richie

Urgent: cannot access the portal home page because of problems language

I have installed Oracle 9iAS, including infrastructure with language FRENCH_FRANCE.WE8ISO8859P15 and portal and wireless type I dont have problem for access to http://machine:1810 and http://machine:7779 in French.
But when I access this url: http://machine:7779/pls/portal, there is a error : java.io.IOException:
Unsupported character encoding: "ISO-8859-15"
at oracle.webdb.page.BaseContentRequest.getResponseJavaEncoding(Unknown Source)
at oracle.webdb.page.BaseContentRequest.getReader(Unknown Source)
at oracle.webdb.page.PageBuilder.getMetaData(Unknown Source)
at oracle.webdb.page.PageBuilder.process(Unknown Source)
at oracle.webdb.page.ParallelServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:269)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
When I install infrastructure, I select FRENCH_FRANCE.WE8ISO8859P15. I check in sql*plus in the v$NLS_PARAMETERS and NLS_LANGUAGE is FRENCH, NLS_TERRITORY is FRANCE, NLS_DATE_LANGUAGE is FRENCH and NLS_CHARACTERSET is WE8ISO8859P15. It seems all well.
But I check in the Windows registry, I find that NLS_LANG is FRENCH_FRANCE.WE8MSWIN1252 under under HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME1 and HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME2. Then I correct in FRENCH_FRANCE.WE8ISO8859P15 in the Windows registry.
Also I check in EM web_site in
To check the DAD settings, in my EM Console, I go to Http Server/PLSQL Properties/DAD status. I correct NLS Language with FRENCH_FRANCE.WE8ISO8859P15.
Also I correct langinst.cmd under OH/portal/admin/plsql to replace WE8MSWIN1252 with WE8ISO8859P15
case f:
setenv NLS_LANG FRENCH_FRANCE.WE8ISO8859P15
breaksw
case frc:
setenv NLS_LANG FRENCH_FRANCE. WE8ISO8859P15
breaksw
All that I do is not useful for access the portal home page, thers is always the error java.io.IOException: Unsupported character encoding: "ISO-8859-15"
I dont have problem in language English. My page portal is running well in a another machine where I install Oracle9iAS in English, but I have always problem in the machine where I install Oracle9iAS in French.
I find there are lots of this problem in this forum, but there isnt a answer. So thanks for anyone to resolve this problem.

Hello Michael,
Thanks for your help !
I think that the problem is in the PlsqlNLSLanguage. But I couldnt check it now with the version French WE8ISO8859P15, because today Ive installed oracle902 AS with WE8MSWIN1252 and it functions well. I find the PlsqlNLSLanguage in my $ORACLE_HOME_INFRA/Apache/mod_plsql/conf/dads.conf is FRENCH_FRANCE.WE8MSWIN1252
, and in my $ORACLE_HOME/Apache/mod_plsql/conf/dads.conf is AMERICAN_AMERICA.WE8MSWIN1252. But I dont understand why it doesnt create the languages problem.
I will try again in another machine with WE8ISO8859P15.

How to get a recordset defined by primarykeys using the LabVIEW Database Connectivity Toolset?

Hi folks.
I'm using LabVIEW with the LabVIEW Db Toolset and Microsoft Access. The table contains 18 columns with a growing nr of rows.Now I want to get the whole recordset containing all columns defined by my primary keys. My SQL-statement is sofar:
SELECT ALL FROM IMPULS_STATOR WHERE FAB = [string] AND LDATE = [datestring] AND ADATE = [datestring]
But every time I end up with an error message saying "Invalid string: specified field does not exist or contains an unsupported character". I mutated the statement several times, adding or removing spaces, colons, etc.
What am I doing wrong?
Thanks in advance

Thanks, Dennis.
Unfortunately, I`m still encountering some problems with the DateValue function. My date/time field has this format: yyyy-mm-dd hh:nn:ss . If I use DateValue, nothing will be returned. Changing the format to yyyy-mm-dd in the Access DB didn`t help and I do need the time. Combining DateValue and TimeValue let to several errors. Using only TimeValue did not help me out. LabVIEW does not indicate errors anymore, therefore the syntax should be fine. But I don`t get any information back from my database.

JAVA Mapping: Handle Special characters like u00E4,u00FC an so on

Hi everybody,
we have a JAVA Mapping that gerenates text nodes with special characters.
The generated XML is later used in an graphical message-mapping.
During runtime we ge the trace/error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error:
com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 31(:main:, row:1, col:2498) at
com.sap.aii.mappingtool.tf3.Transformer.checkParserException
Does anybody know, how to modify the JAVA-mapping to have a workaound for this problem?
Thanks
Regards Mario
Edited by: Mario Müller on Jul 22, 2008 4:33 AM

Hi Mario,
As java mapping does not validate the xml,the output gets created but if u have to use the xml structure,the u will have to include the following.
Assume u r using a write method to write the output xml,then
check for tspecial charactters like &,<,>.' etc and replce them as shown below
private void write(String s)
     //Traverse through the string
for (int i=0 ; i < string.length();i++)
     String s1 = data.substring(i, i + 1);
          if (s1.equals("&"))
               write ("&");
          else if (s1.equals("<"))
          write("<");
          else if (s1.equals(">"))
          write(">");
          else if (s1.equals("\""))
          write(""");
          else if (s1.equals("'"))
          write("'");
          else
          write(s1);
Should help u out
Edited by: Mohd Tauseef Ibrahim on Jul 22, 2008 11:08 AM
Edited by: Mohd Tauseef Ibrahim on Jul 22, 2008 11:09 AM

Error: Requested resource does not exist with SAP WebAS..deployed an ear

hi,
i deployed an application using SDM gui deployement manger.   the application is built using struts,spring etc. I have also created a datasource with Oracel 9i succesfully and hav associated it with the application.
When i try to access the application using the struts based path i get an "<b>ERROR 404:- Error: Requested resource does not exist</b>". I also tried accessing the index.jsp page directly without struts paths but dont know why i get an error "<b>File [appContext/admin/index.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].</b>"
The same ear is working perfectly fine with IBM WSAD but not in SAP Web AS ?? is there any configuration issues that i need to address ?? Kindly help me ASAP !!
Regards,
Vaibhav

Hi,
The Required server log contents are as follows:-
#1.5#000CF1AFC124017A000000020000067000041B1D550F525C#1155712701853#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/doculine#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server#Plain###Runtime error in compiling of the JSP file <C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp> !
The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [/WEB-INF/c.tld]: [
     com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)(:main:, row=739, col=23) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)
Exception id: [000CF1AFC124017A000000000000067000041B1D550F4D94]#
#1.5#000CF1AFC124017A000000030000067000041B1D550F5C88#1155712701868#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/doculine#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error##Plain###Processing HTTP request to servlet [action] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp].
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:117)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:429)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
     at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:1001)
     at org.apache.struts.action.RequestProcessor.processForward(RequestProcessor.java:560)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:209)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:386)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:229)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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(Native Method)
     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.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [/WEB-INF/c.tld]: [
     com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)(:main:, row=739, col=23) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.validate(JSPParser.java:243)
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:348)
     at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
     ... 37 more
#1.5#000CF1AFC124017A000000050000067000041B1D550F5F94#1155712701868#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/doculine#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [action] finished with error.
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp].
Exception id: [000CF1AFC124017A000000030000067000041B1D550F5C88]#

Aperture with referenced library on a terastation

I was experiencing a problem similar (or identical) to the one discussed in this post (http://discussions.apple.com/message.jspa?messageID=6695612&tstart=0) and made some head-way on debugging it. Since I have a few more data points, I'm creating a thread with a more specific description of the problem.
To quickly review: I was attempting to import photos from a camera or card reader and place the photos onto a volume hosted by a terastation. I would select 1 or more photos for import, push the button, and Aperture would quickly respond "0 Images have been imported" with no error/failure message.
- In the aforementioned configuration, I had the Library "package" on my local drive and was simply trying to save the pictures to the terastation.
- I started over (whacked the pictures folder, whacked the prefs.plist, whacked the library) and created a new library package on the local drive.
- When I selected a local drive as the destination for the pictures (though not IN the library itself) the import worked ok.
- Tried moving the library package over to the terastation and it said something to the effect of "could not copy all files because one or more files uses an unsupported character in the filename".
- I could move the folder containing the pictures to the terastation after import.
- If I create a library package on the terastation, it does not complain.
- So, with the library on the TS, I tried importing again with the destination for the pictures being a local drive.
- This time I got an error message saying "Import From Capture Card Completed with Errors" and it listed the files that failed (though it did not elaborate on the error).
So if either the library AND/OR the destination for the pictures is the terastation, the import will fail. Though I see no "good" reason for a failure in the case where the library is local and the pictures are on the TS.
Is there a way to enable logging so I can get a better idea for the failure mechanism?
Any known solutions/work-arounds to this problem?

Most of the description was a list of trouble-shooting steps I've gone through. The fundamental thing that I'm trying to do is keep the library on my local computer and the pictures on the terastation.
In the import dialog, I set "Store Files" to a path on the TS, copy and move are grayed (but copy is selected), subfolders is set to "Image year/month/day", I click "Import <n> Images" and it says "0 images have been imported"
None of the picture filenames are unusual. I'm not sure why its failing because none of the errors are verbose
FWIW, I believe the terastation uses XFS as the underlying format.
At this point I've disabled all access permissions and the folder should be fully writable by anyone.

Unsupported character

Similar Messages

Maybe you are looking for