RFC 2 FLAT "Conversion configuration error: Unknown structure" MessageTrans

Hello all,
I want to use MessageTransformBean to map an RFC Call to a FlatFile in Receiver Adapter. As it is not FTP I can't use FCC.
Everytime I start the processing I get the error:
com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)'
I implemented everything according to [this|http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm] guide (complex conversion for receiver cc).
I also tried to map the RFC to another XML structure, but the error was the same?
Any ideas?
Best regards,
David

You can probably find answers in these threads:
Error in Receiver FCC: Unknown structure ... found in document
Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'
Error in reciever file content conversion
Regards,
Ravi

Similar Messages

'Conversion configuration error: Unknown structure

Hi, my scenario is very simple, Proxy->PI->File and there is no mapping.
There is a report that sends all the data to PI with the proxy and that works OK, but when the file adapter must generate the file I get the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'n:WU_MT_BP' found in document', probably configuration error in file adapter (XML parser error)'
The XML can't be wrong because the MT of the proxy service interface is the same that the MT of the file interface.
In the file content conversion I specified all the structures, with fieldFixedLenghts parameter and endSeparator = 'nl'... I checked those parameters too and they look OK too...

>>Unknown structure 'n:WU_MT_BP
This looks clearly like a content conversion issue.
In file content conversion for recordset structure,have you specified WU_MT_BP?
Is this tag required or it shouldn't be coming in payload in first place.
It is possible that the occurrence of this tag is optional and you may be specified/not-specified content conversion parameters for it.
Thanks
Aamir

Conversion configuration error Unknown structure Header found in document

Hi,
we are having the following target structure according to that we need to generate a file.
Output file sample format:
ACODESXXXX0001581012011-03-2209.12.42WARRANTY CAUSE CODES FILE
ACODESXXXX000158102CCCORROSION INSPECTION
ACODESXXXX00015810255CAVITY, PINHOLE
ACODESXXXX00015810256BAD MACHINING
BCODESXXXX0001581012011-03-2209.12.42WARRANTY COMPLAINTS CODES FILE
BCODESXXXX000158102NCNO CUSTOMER COMPLAINT
BCODESXXXX000158102XPCONSIDERATION
BCODESXXXX00015810299OTHER
BCODESXXXX000158199000000131
CCODESXXXX0001581012011-03-2209.12.42WARRANTY CIRCUMSTANCE CODES FILE
CCODESXXXX000158102 BLANK
CCODESXXXX000158102AAT ENGINE START
CCODESXXXX000158102BWHEN WARMING-UP
Target Record Structure:
DT_Codes
          Record
                    ACodes
                           Header
                           Details
                           Trailer
                     Bcodes
                           Header
                           Details
                           Trailer
                     Ccodes
                           Header
                           Details
                           Trailer
                     TWRNTY
                           Header
                           Details
                           Trailer
In receiver file adapter we have given following content conversion parameters
Content conversion Parameters :
Recordset Structure*: A_Code.Header,A_Code.Detail,A_Code.Trailer,B_Code.Header,B_Code.Detail,B_Code.Trailer,C_Code.Header,C_Code.Detail,C_Code.Trailer,
Name                                                                                value
A_Code.Header.filedFixedLengths               4,5,7,8,2,3,4
A_Code.Detail.filedFixedLengths               4,5,2,8,9,3,2,7,8,9,3
A_Code.Trailer.filedFixedLengths                  4,5,2,2,3,3,4
B_Code.Header.filedFixedLengths               4,5,7,8,2,3,4
B_Code.Detail.filedFixedLengths               4,5,2,8,9,3,2,7,8,9,10
B_Code.Trailer.filedFixedLengths                  4,5,2,2,3,3,4
C_Code.Header.filedFixedLengths               4,5,7,8,2,3,4
C_Code.Detail.filedFixedLengths               4,5,2,8,9,3,2,7,8,9,10
C_Code.Trailer.filedFixedLengths                  4,5,2,2,3,3,4
Now we are getting error "Conversion configuration error Unknown structure Header found in document"
Please suggest solution for the error.
thank you,
Praveen.

your content conversion parameters seem to be wrong.
Do refer;
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion

Error in Receiver FCC: Unknown structure ... found in document

Hi Experts,
I have a problem with the Receiver File Adapter. I want to use Content Conversion to generate a plain file.
Input to receiver file adapter:
<?xml version="1.0" encoding="utf-8" ?>
<PlainFile>
<filename>filename.txt</filename>
<line>Line 1</line>
<line>Line 2</line>
</PlainFile>
Wanted result: a file filename.txt with this content:
Line 1
Line 2
FCC settings:
RecordSet Structure: line, filename
line.fieldSeparator:'nl'
filename.fieldFixedLengths:0
filename.fixedLengthTooShortHandling:Cut
Problem is: the adapter throws error "Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'PlainFile' found in document'"
If I use:
RecordSet Structure: PlainFile, line, filename
and add:
PlainFile.fieldSeparator:'nl'
... the lines are printed, but also the unwanted filename. The XML input results from an 1:n mapping, therefore I want to set different filenames by variable substitution from the payload.
Many thanks for your help,
Ralf

Since you want to the filename to be sent in the payload, check out the below Variable Substitution Method. This information is available in help.sap.com.
Advanced Tab Page
Variable Substitution (Target Directory/File Name Scheme)
If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
●      Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
The variables can refer to attributes of the message header or elements of the message payload.
○       If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace,
message_id (message ID with hyphens, for example 9fbe1ff1-9a0d-11d9-8665-cbf10a126331)
message_id_hex (message ID in hexadecimal format, for example 9fbe1ff19a0d11d98665cbf10a126331)
For example, if you want to specify the interface name from the message header in the target directory or in the file name scheme, enter message:interface_name as the reference.
Note
If one of the message attributes contains characters that are not permitted in a file name, for example \, /, :, *, ?, ", <, >, |, then these characters are replaced by an underscore ("_").
○       If the variable refers to an element in XML schema, add the prefix payload: to the information under Reference. The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
Example
To reference the element that is in bold in the example, the following expression is used: payload:root,1,e1,1,e2,2
The parser searches for the first occurrence of the root element at the first level. It then searches for the first occurrence of e1 at the second level and for the second occurrence of e2 at the third level. The content of the last element (Example Value) is set as the value for a specified variable.
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<dummy>
     <e1>
        <e2>Data_1</e2>
        <f/>
        <g attr="abc">text</g>
        <e2>Data_2</e2>
     </e1>
</dummy>
<e1>
     <e2>illegal/value</e2>
     <f/>
     <g attr="abc">text</g>
     <e2 attr="fghij">Example Value</e2>
</e1>
</root>

Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'

I have other problem.
The receiver channel communication gives the next error:
Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_dbglgtr_FileName' found in document', probably configuration error in file adapter (XML parser error)'.
I haven't empty node and any condition.
Thank you.

Hi,
Same problem solved here: (infact many threads with the same problem and solution)
Error in Receiver FCC: Unknown structure ... found in document
Re: Receiver File content conversion - NO Output
Regards,
Abhishek.
Edited by: abhishek salvi on Apr 14, 2009 7:42 PM

The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: unknown user name or bad

The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
Logon failure: unknown user name or bad password
am using Windows integrated security,version of my sql server 2008R2
I have go throgh the different articuls, they have given different answers,
So any one give me the exact soluction for this problem,
Using service account then i will get the soluction or what?
pls help me out it is urgent based.
Regards
Thanks!

Hi Ychinnari,
I have tested on my local environment and can reproduce the issue, as
Vaishu00547 mentioned that the issue can be caused by the Execution Account you have configured in the Reporting Services Configuration Manager is not correct, Please update the Username and Password and restart the reporting services.
Please also find more details information about when to use the execution account, if possible,please also not specify this account:
This account is used under special circumstances when other sources of credentials are not available:
When the report server connects to a data source that does not require credentials. Examples of data sources that might not require credentials include XML documents and some client-side database applications.
When the report server connects to another server to retrieve external image files or other resources that are referenced in a report.
Execution Account (SSRS Native Mode)
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

Error message in Logic "audio configuration contains unknown items"

I am using Logic Studio with an apogee Duet and Mac Book Pro.
So far I love the apogee duet for it's simplicity and sound. I have
however started to receive this error message working with Logic Studio,
almost anytime I start a new track, add a plug-in or instrument, etc.
"Audio Configuration contains unknown items"
It did not do this from the very beginning but started after a few
sessions. I have tried re-installing the driver disc for the Duet but it still happens.
when it does pop-up i can click the ok box and after clicking several times
it will go away and let me proceed.
Could anyone please advise me.
thank you very much.

Maybe this happen bacause you put many additional info in your "Aple discussion" profile about the software that you use, but we can also say you the same as Logic message:
your detailed "Audio configuration" profile info contain a "unknow item"
Whitch is your audio interface?
G
PS: anyway, try to trash Logic preferences.

The recording device reported the media error: Unknown device error. (0x0C,

Hello
I have a problem making a DUAL LAYER DVD, i have done anothers before. But now I can't burn it.
It's a message error.
(The recording device reported the media error: Unknown device error. (0x0C, 0x00.))
Next this my Mac configuration.
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3.2 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 6 GB
I have DVD STUDIO PRO 4.2.1, and in the log appears this:
Starting DVD Build UNTITLED_DISC...
Compiler Initializing...
Precompiling Project UNTITLED_DISC
Compiling VMG Information...
Created 6 PGCs in VTSM1
Created 8 PGCs in VMG.
0 Menu(s) will be created...
Compiling Menu PGCs...
Writing VTS010.VOB
Writing VIDEO_TS.VOB
1 VTSs and 1 Titles will be created...
Compiling VTS#1 (Track 1)...
Writing VTS010.VOB
Muxing VTS011.VOB
Done.
Linking VMG...
Linking VTS#1...
Writing VTS#1...
Writing VMG...
Writing Layout Info...
Compile Completed Successfully
Note: The file ‘UNTITLED_DISC.layout’ found in the ‘VIDEO_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Note: The file ‘VOB_DATA.LAY’ found in the ‘VIDEO_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Start formatting
Formatting as Standard DVD
Simulation mode is off
Lossless linking is on
Number of layers is 2
Doing opposite track path
Setting layer switch at sector 2053488.
Doing side 1 of 1
Playable in region 1,2,3,4,5,6,8
Disc size is 12 cm
Disc has no copyright material
Writing ISO 9660 directories
Writing UDF 1.02 structures
Writing files
The recording device reported the media error: Unknown device error. (0x0C, 0x00.)
What should be the problem?

There could be a few reasons, a common one is bad DVDs or a burner going bad.
[Some threads discussing the error|http://discussions.apple.com/search.jspa?threadID=&q=Therecording+device+reported+the+media+error%3A+Unknown+device+error.+(0x0C%2C0x00.)&objID=f952&dateRange=all&userID=&numResults=15]
You can try the [arrpoach in this thread|http://discussions.apple.com/thread.jspa?messageID=2453295&#2453295] as s start.
Take a look at this
Not sure which brand of DVDs you are using, but [this guide rates brands|http://www.digitalfaq.com/reviews/dvd-media.htm]
Verbatim are usually good for me for DL.

Plan Driven Procurement - Error message "Structure 01 CP 10170237 CP-S-O

Hi SRM Experts,
Iam seeking your help to avoid error messages in the Plan driven procurement scenario.
I have configured Plan driven procurement scenario as described in the ref. material. The objective of this scenario is transferred PR in EB/SRM should create a entry in sourcing cockpit.
Back end (R/3)configuration steps completed:
1. Entries maintained in V_T160EX, V_T160PR
2. RFC communication established using RFC user
3. As soon as PR (Purchase Requisition) is created from Projects, Network the PR is available in EPRTANS table with Procurement profile.
4. Manually executed PR Transfer program BBP_EXTREQ_TRANSFER
5. Outbound Queue got generated but with below error message.
Error Message: Structure 01 CP 10170237 CP-S-O: No agent found
SRM/EBP Settings maintained:
Direct procurement attribute maintained.
Entry channel created under Company code org. structure
RFC user is assigned to the entry channel.
Assigned Product categories and entries channel to the respective purchase group.
Defined sourcing for product categories.
After maintaining all above configuration, iam still getting error message.
Please provide your expert guidence to complete this scenario setup.
Regards,
Karnati

Hi Nagi,
This is related to Parner determination process with both systems in CRM & ECC.
Error Details: "Partner Function" in CRM is not there in ECC.
We mapped in ECC by creating a ZB copied from "SB" Partner function in ECC & reprocessed the order in CRM, Henceforth rectififed the error.
Many Thanks !!!
Sany.

Handling XMLs with unknown structures.

Hello Experts,
I have to build a generic interface RFC -> PI -> JMS, which will receive XML structure as a string in import parameter of RFC.
Then I need to convert this string to XML, add digital signatures and then output the signed payload to JMS Queues.
I have been looking at SDN posts and found that XSLT can be used to convert string to XML. But the catch is I am not aware of the XML structures that will be sent in as a string. So how can I handle these unknown structures? Or what should be the structure of the target Interface for XSLT mapping??
Any inputs on this will be of great help.
Kind Regards,
PIQueries_2010

If you dont want the target structure to be validated XSLT/java mapping is the way to go as pointed out by MIchal.
If you use the new feature, I believe it will validate the target structure.
@Michal,
Just a quick clarification, when we use java/xslt mapping to skip target message validation in PI 7.1 is it mandatory to have the operation name exactly same as Service Interface name? I recently ran into an issue where the Service interface name was different from the operation name and the Java mapping was giving an error saying "Unable to validate root element" or something similar (Ofcourse, the content was binary file and hence java mapping to skip the target structure validation).
Thanks
Jai

J2SE adapter PI 7.1 issue with XML to flat conversion and namespace length

Dear reader,
We are facing an issue with J2SE Adapter PI7.1 for a number of flows.
The flow requirements:
[1] Namespace length for interfaces is up to 100 characters
[2] The XML message must be converted to Flat on the adapter channel
Our PI system is at patch level 7 and we implement J2SE adapter on patch level 7 as well.
We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1 j2SE adapter) but no issues where found with the XML to flat conversion [2].
Experimenting with J2SE adapter on patch level 6 we found the long namespaces [1] are supported however an issue is found with the XML to flat conversion [2] as stated in SAP note 1335527.
An SAP Customer Message is raised on this issue however your input is highly appricated!
With Kind Regards,
Harald Kastelijn
Edited by: Harald Kastelijn on Mar 6, 2010 9:17 AM
Edited by: Harald Kastelijn on Mar 6, 2010 9:19 AM

We found that the J2SE adapter on patch level 7 does not support long namespaces [1] (as it should since this is an PI 7.1
j2SE adapter) but no issues where found with the XML to flat conversion [2]
I think the restriction of namespace length still remains in design time (IR).....the same however has been extended in configuration and runtime...this SAP note has some information: https://service.sap.com/sap/support/notes/870809

[SOLVED] configure: error: cannot run C compiled programs

I'm trying to build lib32-libxkbcommon 0.5.0-1 from AUR with makepkg. I already tried installing pacman (setting the default makepkg.conf) and multilib-devel with no luck.
makepkg messages:
==> Making package: lib32-libxkbcommon 0.5.0-1 (Mon May 11 00:17:05 EEST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found libxkbcommon-0.5.0.tar.xz
==> Validating source files with sha256sums...
libxkbcommon-0.5.0.tar.xz ... Passed
==> Extracting sources...
-> Extracting libxkbcommon-0.5.0.tar.xz with bsdtar
bsdtar: Failed to set default locale
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for style of include used by make... GNU
checking for gcc... gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
==> ERROR: A failure occurred in build().
Aborting...
makepkg.conf:
# /etc/makepkg.conf
# SOURCE ACQUISITION
#-- The download utilities that makepkg should use to acquire sources
# Format: 'protocol::agent'
DLAGENTS=('ftp::/usr/bin/curl -fC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
'http::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
'https::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
'rsync::/usr/bin/rsync --no-motd -z %u %o'
'scp::/usr/bin/scp -C %u %o')
# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/wget
#-- The package required by makepkg to download VCS sources
# Format: 'protocol::package'
VCSCLIENTS=('bzr::bzr'
'git::git'
'hg::mercurial'
'svn::subversion')
# ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
# BUILD ENVIRONMENT
# Defaults: BUILDENV=(!distcc color !ccache check !sign)
# A negated environment option will do the opposite of the comments below.
#-- distcc: Use the Distributed C/C++/ObjC compiler
#-- color: Colorize output messages
#-- ccache: Use ccache to cache compilation
#-- check: Run the check() function if present in the PKGBUILD
#-- sign: Generate PGP signature file
BUILDENV=(!distcc color !ccache check !sign)
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg
# GLOBAL PACKAGE OPTIONS
# These are default values for the options=() settings
# Default: OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)
# A negated option will do the opposite of the comments below.
#-- strip: Strip symbols from binaries/libraries
#-- docs: Save doc directories specified by DOC_DIRS
#-- libtool: Leave libtool (.la) files in packages
#-- staticlibs: Leave static library (.a) files in packages
#-- emptydirs: Leave empty directories in packages
#-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge: Remove files specified by PURGE_TARGETS
#-- upx: Compress binary executable files using UPX
#-- debug: Add debugging flags as specified in DEBUG_* variables
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)
#-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
INTEGRITY_CHECK=(md5)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
# PACKAGE OUTPUT
# Default: put built package and cached source in build directory
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Log files: specify a fixed directory where all log files will be placed
#LOGDEST=/home/makepkglogs
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <[email protected]>"
#-- Specify a key to use for package signing
#GPGKEY=""
# COMPRESSION DEFAULTS
COMPRESSGZ=(gzip -c -f -n)
COMPRESSBZ2=(bzip2 -c -f)
COMPRESSXZ=(xz -c -z -)
COMPRESSLRZ=(lrzip -q)
COMPRESSLZO=(lzop -q)
COMPRESSZ=(compress -c -f)
# EXTENSION DEFAULTS
# WARNING: Do NOT modify these variables unless you know what you are
# doing.
PKGEXT='.pkg.tar.xz'
SRCEXT='.src.tar.gz'
# vim: set ft=sh ts=2 sw=2 et:
config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by libxkbcommon configure 0.5.0, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure --prefix=/usr --libdir=/usr/lib32 --disable-docs --disable-static
## Platform. ##
hostname = Arch
uname -m = x86_64
uname -r = 4.0.1-1-ARCH
uname -s = Linux
uname -v = #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /usr/lib/jvm/default/bin
PATH: /usr/bin/site_perl
PATH: /usr/bin/vendor_perl
PATH: /usr/bin/core_perl
## Core tests. ##
configure:2424: checking for a BSD-compatible install
configure:2492: result: /usr/bin/install -c
configure:2503: checking whether build environment is sane
configure:2558: result: yes
configure:2709: checking for a thread-safe mkdir -p
configure:2748: result: /usr/bin/mkdir -p
configure:2755: checking for gawk
configure:2771: found /usr/bin/gawk
configure:2782: result: gawk
configure:2793: checking whether make sets $(MAKE)
configure:2815: result: yes
configure:2844: checking whether make supports nested variables
configure:2861: result: yes
configure:2987: checking whether to enable maintainer-specific portions of Makefiles
configure:2996: result: yes
configure:3023: checking for style of include used by make
configure:3051: result: GNU
configure:3122: checking for gcc
configure:3149: result: gcc -m32
configure:3378: checking for C compiler version
configure:3387: gcc -m32 --version >&5
gcc (GCC) 5.1.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3398: $? = 0
configure:3387: gcc -m32 -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/gcc-multilib/src/gcc-5-20150505/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --with-default-libstdcxx-abi=c++98
Thread model: posix
gcc version 5.1.0 (GCC)
configure:3398: $? = 0
configure:3387: gcc -m32 -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3398: $? = 1
configure:3387: gcc -m32 -qversion >&5
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:3398: $? = 1
configure:3418: checking whether the C compiler works
configure:3440: gcc -m32 -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
configure:3444: $? = 0
configure:3492: result: yes
configure:3495: checking for C compiler default output file name
configure:3497: result: a.out
configure:3503: checking for suffix of executables
configure:3510: gcc -m32 -o conftest -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
configure:3514: $? = 0
configure:3536: result:
configure:3558: checking whether we are cross compiling
configure:3566: gcc -m32 -o conftest -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
In file included from /usr/include/stdio.h:27:0,
from conftest.c:11:
/usr/include/features.h:365:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
configure:3570: $? = 1
configure:3577: ./conftest
./configure: line 3579: ./conftest: No such file or directory
configure:3581: $? = 127
configure:3588: error: in `/mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0':
configure:3590: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
## Cache variables. ##
ac_cv_env_CC_set=set
ac_cv_env_CC_value='gcc -m32'
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4'
ac_cv_env_CPPFLAGS_set=set
ac_cv_env_CPPFLAGS_value=-D_FORTIFY_SOURCE=2
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_DOT_set=
ac_cv_env_DOT_value=
ac_cv_env_DOXYGEN_set=
ac_cv_env_DOXYGEN_value=
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value=-Wl,-O1,--sort-common,--as-needed,-z,relro
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_PKG_CONFIG_LIBDIR_set=
ac_cv_env_PKG_CONFIG_LIBDIR_value=
ac_cv_env_PKG_CONFIG_PATH_set=set
ac_cv_env_PKG_CONFIG_PATH_value=/usr/lib32/pkgconfig
ac_cv_env_PKG_CONFIG_set=
ac_cv_env_PKG_CONFIG_value=
ac_cv_env_XCB_XKB_CFLAGS_set=
ac_cv_env_XCB_XKB_CFLAGS_value=
ac_cv_env_XCB_XKB_LIBS_set=
ac_cv_env_XCB_XKB_LIBS_value=
ac_cv_env_XORG_MALLOC_DEBUG_ENV_set=
ac_cv_env_XORG_MALLOC_DEBUG_ENV_value=
ac_cv_env_YACC_set=
ac_cv_env_YACC_value=
ac_cv_env_YFLAGS_set=
ac_cv_env_YFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/usr/bin/mkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_ac_ct_CC='gcc -m32'
ac_cv_prog_make_make_set=yes
am_cv_make_support_nested_variables=yes
## Output variables. ##
ACLOCAL='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing aclocal-1.14'
ADMIN_MAN_DIR=''
ADMIN_MAN_SUFFIX=''
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='$${TAR-tar}'
AM_BACKSLASH='\'
AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
AM_DEFAULT_VERBOSITY='1'
AM_V='$(V)'
APP_MAN_DIR=''
APP_MAN_SUFFIX=''
AR=''
AUTOCONF='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing autoconf'
AUTOHEADER='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing autoheader'
AUTOMAKE='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing automake-1.14'
AWK='gawk'
BASE_CFLAGS=''
BUILD_LINUX_TESTS_FALSE=''
BUILD_LINUX_TESTS_TRUE=''
CC='gcc -m32'
CCDEPMODE=''
CFLAGS='-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4'
CHANGELOG_CMD=''
CPP=''
CPPFLAGS='-D_FORTIFY_SOURCE=2'
CWARNFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR='.deps'
DLLTOOL=''
DOT=''
DOXYGEN=''
DRIVER_MAN_DIR=''
DRIVER_MAN_SUFFIX=''
DSYMUTIL=''
DUMPBIN=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ENABLE_DOCS_FALSE=''
ENABLE_DOCS_TRUE=''
ENABLE_X11_FALSE=''
ENABLE_X11_TRUE=''
EXEEXT=''
FGREP=''
FILE_MAN_DIR=''
FILE_MAN_SUFFIX=''
GREP=''
HAVE_DOT=''
HAVE_DOT_FALSE=''
HAVE_DOT_TRUE=''
HAVE_DOXYGEN_FALSE=''
HAVE_DOXYGEN_TRUE=''
HAVE_NO_UNDEFINED_FALSE=''
HAVE_NO_UNDEFINED_TRUE=''
INSTALL_CMD=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LD=''
LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro'
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIB_MAN_DIR=''
LIB_MAN_SUFFIX=''
LIPO=''
LN_S=''
LTLIBOBJS=''
MAINT=''
MAINTAINER_MODE_FALSE='#'
MAINTAINER_MODE_TRUE=''
MAKEINFO='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing makeinfo'
MANIFEST_TOOL=''
MAN_SUBSTS=''
MISC_MAN_DIR=''
MISC_MAN_SUFFIX=''
MKDIR_P='/usr/bin/mkdir -p'
NM=''
NMEDIT=''
OBJDUMP=''
OBJEXT=''
OTOOL64=''
OTOOL=''
PACKAGE='libxkbcommon'
PACKAGE_BUGREPORT='https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon'
PACKAGE_NAME='libxkbcommon'
PACKAGE_STRING='libxkbcommon 0.5.0'
PACKAGE_TARNAME='libxkbcommon'
PACKAGE_URL='http://xkbcommon.org'
PACKAGE_VERSION='0.5.0'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PKG_CONFIG_LIBDIR=''
PKG_CONFIG_PATH='/usr/lib32/pkgconfig'
RANLIB=''
RT_LIBS=''
SED=''
SET_MAKE=''
SHELL='/bin/sh'
STRICT_CFLAGS=''
STRIP=''
VERSION='0.5.0'
XCB_XKB_CFLAGS=''
XCB_XKB_LIBS=''
XKBCONFIGROOT=''
XLOCALEDIR=''
XORG_MALLOC_DEBUG_ENV=''
XORG_MAN_PAGE=''
YACC=''
YACC_INST=''
YFLAGS=''
ac_ct_AR=''
ac_ct_CC='gcc -m32'
ac_ct_DUMPBIN=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include='include'
am__isrc=''
am__leading_dot='.'
am__nodep='_no'
am__quote=''
am__tar='$${TAR-tar} chof - "$$tardir"'
am__untar='$${TAR-tar} xf -'
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/install-sh'
libdir='/usr/lib32'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''
## confdefs.h. ##
/* confdefs.h */
#define PACKAGE_NAME "libxkbcommon"
#define PACKAGE_TARNAME "libxkbcommon"
#define PACKAGE_VERSION "0.5.0"
#define PACKAGE_STRING "libxkbcommon 0.5.0"
#define PACKAGE_BUGREPORT "[url]https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon[/url]"
#define PACKAGE_URL "[url]http://xkbcommon.org[/url]"
#define PACKAGE "libxkbcommon"
#define VERSION "0.5.0"
configure: exit 1
other info:
core/pacman 4.2.1-1
multilib/gcc-multilib 4.9.2-4 (multilib-devel) [installed]
The GNU Compiler Collection - C and C++ frontends for multilib
multilib/lib32-fakeroot 1.20.2-1 (multilib-devel) [installed]
Tool for simulating superuser privileges (32-bit)
multilib/lib32-libltdl 2.4.5-1 (multilib-devel) [installed]
A generic library support script (32-bit)
Last edited by tsester (2015-05-10 22:10:28)

tsester wrote:P.S.: I recently transfered the linux system between failing disks
In that case you should probably check that no other packages are missing files with
pacman -Qkk 2>&1 | grep "No such file or directory"
Any packages that report that they're missing files, you should reinstall.

Error: unknown entity type 'Archive' when building external library

Hi,
This is what I get when trying to build a external library in SP14. If I look at the Libraries.pp files there are entries like this:
<entity>
     <name>CLASSES12.JAR</name>
     <package></package>
     <caption>CLASSES12.JAR</caption>
     <description></description>
     <entity-type>Archive</entity-type>
     <entity-sub-type>Java Library</entity-sub-type>
</entity>
CLASSES12.JAR is a jar file I've added to the libraries folder and then added to the Public part (used <a href="/people/valery.silaev/blog/2005/09/14/a-bit-of-impractical-scripting-for-web-dynpro blog</a> as an example)
Build log:
Development Component Build (2006-02-23 10:27:16)
Component name: lib
Component vendor: XXXXXXXXX.com
SC compartment: MyComponents
Configuration: LocalDevelopment
Location: local
Source code location: jarpak@XXXXXXXXX
DC root folder: C:\Documents and Settings\jarpak\.dtc\LocalDevelopment\DCs\XXXXXXXXX\lib\_comp\
DC type: External Library
Host: XXXXXXXXX
DC Model check:
[dcmake] All used DCs are available locally
[dcmake] validating dependency to build plugin "sap.com/tc/bi/bp/externalarchive"
[dcmake] DC model check OK
Start build plugin:
[dcmake] using build plugin: sap.com/tc/bi/bp/externalarchive
[dcmake] starting build plugin from : C:\Program Files\SAP\JDT\eclipse\plugins\com.sap.tc.ap\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\externalarchive\_comp\gen\default\public\lib\
Build Plugins Version 6.40.0.111 (ExternalArchivePlugin, 630_VAL_REL ) from 2005-09-09 23:37:14 CEST
Building development component 'lib', vendor 'XXXXXXXXX', type 'External Library'
software component 'MyComponents', vendor 'sap.com'.
location 'local'.
source code location 'jarpak@XXXXXXXXX'.
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Reading BuildInfrastructure extension from DC tc/bi/util (vendor sap.com)
Added technology 'sap.com/tc/bi/core'
Error: unknown entity type 'Archive'.
Cleaning up.
Regards,
Jari

Hi,
Solved it on my own with
Re: Activation Error: "unknown entity type 'Archive'" thread.
Jari

Unknown structure ID 0 for flexfield code GL# with application ID 101

Hi Experts,
I am working on Report builder 6i, EBS 11i, and data base 9i. I have standard report, when i am running it, it's giving below error.
ERROR: APP-FND-01016: Routine FDFRKS: Unknown structure ID 0 for flexfield code GL# with application ID 101.
It's calling below thing in Before Report Trigger.
begin
SRW.USER_EXIT('FND FLEXSQL CODE="GL#" NUM=":P_ACCT_STRUCT_NUM"
APPL_SHORT_NAME="SQLGL" OUTPUT="P_acct_flex"
MODE="SELECT" DISPLAY="ALL" TABLEALIAS="GCC"');
exception when srw.user_exit_failure then
srw.message(3,'Failed in GL#/Select');
raise;
end;
Could somebody help me what could be the reason for this error.
Thanks.

Hi,
Is the error still ocurring ? Is yes, please refer the below note in Metalink. This should resolve the issue.
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=227438.1
-Sailaja.

Column value ' ' too long - must stop', probably configuration error

Hi Experts,
I have a Proxy to File Scenario when I execute it I get this error in RWB. Can you please help me on this:
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value ' ' too long - must stop', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value ' ' too long - must stop', probably configuration error in file adapter (XML parser error)'
Thanks
Srikanth E

Hi,
if there is any empty tag coming from source then target structure tag will not be created and because of which ur payload structure and FCC configuration is not matching.
To use map with default between source and target strcture so in case source tag dont have value target structure will be created because of mapwithdegfault fuction and ur FCC will not fail.
Open SXMB_MONI output payload and compare the structre with Data type u will se for no source value target tag is not created at all and FCC is failed.
please refer below thread,
0 byte txt file using receiver File Adapter
regards,
ganesh.

RFC 2 FLAT "Conversion configuration error: Unknown structure" MessageTrans

Similar Messages

Maybe you are looking for