MAP 7.0 errors completing inventory

I am using MAP v7.0 to run hardware and software inventory scans on Windows and Linux/Solaris servers and receive errors not found in any of the blogs or documentation. The specific error is "Failed- Inventory not completed". I cant think of a more generic
non descriptive error, the log does not seem to point to anything.
This error is generated when running the inventory scans on Linux/Solaris servers via SSH.
I have the firewall open SSH port 22 and the credentials provided for the scan are root or equal to root, any information or solution for the error?

Did you ever get an answer to this question? I am getting the same error on a few of my Linux servers with no documentation to help me.

Similar Messages

DBCA Fails with error accessing inventory - OEL5.3 DB11g SE install

Hello,
We're trying to install ODB11g for x86_64 on a OEL5.3 and after having prep'd the environment, kernel, etc... The oracle user runs the runInstaller script, everything passes with flying colors until... the DBCA when in the step of completeing "Database Creation" gives an error which is logged in the: emConfig.log and suggests we re-execute the emca script...
+"Enterprise manager configuration failed due to the following error - error starting Database Control+
+Refer to the log file /.../dbca/orcl/emConfig.log for more details.+
+You can retry configuring thsi database with Enterprise Manager later by manually running+
+/.../bin/emca"+
After searching the logs, we find that the oraInst.loc file does not exist or there are no permission, the /etc/oracInst.loc exists but the emConfig.log file says this is the error (or one of them maybe):
Aug 12, 2009 4:24:56 PM oracle.sysman.emcp.util.OUIInventoryUtil getInstallInventory
CONFIG: Error accessing inventory.
oracle.sysman.oii.oiii.OiiiInventoryDoesNotExistException: The inventory pointer location /etc/oraI
nst.loc is either not readable or does not exist
... this is a clean install. Any sugestions?? (we've tried re-running the config steps according to the documentation but maybe we've missed something???)
Thanks for any help!!
LMA.
Edited by: user8678312 on Aug 12, 2009 1:38 PM
Edited by: user8678312 on Aug 12, 2009 2:59 PM

No luck with either workaround... the DBCA runs smooth until it gets to the emca where the oraInst.loc keeps on annoying... checked its permissions 644, owner root... ran the emca manually heres the results:
Aug 12, 2009 8:29:48 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Error creating the repository
Refer to the log file at /u01/app/oracle/cfgtoollogs/emca/orcl/emca_2009_08_12_20_28_33.log for more details.
Could not complete the configuration. Refer to the log file at /u01/app/oracle/cfgtoollogs/emca/orcl/emca_2009_08_12_20_28_33.log for more details.
the log turns out the same error regarding the oraInst.loc.
any other suggestion perhaps?
thx!!

DG Observer triggering SIGSEGV Address not mapped to object errors in alert log

Hi,
I've got a Data Guard configuration using two 11.2.0.3 single instance databases. The configuration has been configured for automatic failover and I have an observer running on a separate box.
This fast-start failover configuration has been in place for about a month and in the last week, numerous SEGSEGV (address not mapped to object) errors are reported in the alert log. This is happening quite frequently (every 4/5 minutes or so).
The corresponding trace files show the process triggering the error coming from the observer.
Has anyone experienced this problem? I'm at my wits end trying to figure out how to fix the configuration to eliminate this error.
I must also note that even though this error is occurring a lot, it doesn't seem to be affecting any of the database functionality.
Help?
Thanks in advance.
Beth

Hi..   The following is the alert log message, the traced file generated, and the current values of the data guard configuration. In addition, as part of my research, I attempted to apply patch 12615660 which did not take care of the issue. I also set the inbound_connection_timeout parameter to 0 and that didn't help either. I'm still researching but any pointer in the right direction is very much appreciated.
Error in Alert Log
Thu Apr 09 10:28:59 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc (incident=69298):
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Thu Apr 09 10:29:02 2015
Sweep [inc][69298]: completed
Trace file:
Trace file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning and Oracle Label Security options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1
System name:    Linux
Node name:      <host name>
Release:        2.6.32-431.17.1.el6.x86_64
Version:        #1 SMP Wed May 7 14:14:17 CDT 2014
Machine:        x86_64
Instance name: <SID>
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 29902, image: oracle@<host name>
*** 2015-04-09 10:28:59.966
*** SESSION ID:(416.127) 2015-04-09 10:28:59.966
*** CLIENT ID:() 2015-04-09 10:28:59.966
*** SERVICE NAME:(<db_unq_name>) 2015-04-09 10:28:59.966
*** MODULE NAME:(dgmgrl@<observer host> (TNS V1-V3)) 2015-04-09 10:28:59.966
*** ACTION NAME:() 2015-04-09 10:28:59.966
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
DDE: Problem Key 'ORA 7445 [nstimexp()+71]' was flood controlled (0x6) (incident: 69298)
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/cdump'
Data Guard Configuration
DGMGRL> show configuration verbose;
Configuration - dg_config
Protection Mode: MaxPerformance
Databases:
    dbprim - Primary database
    dbstby - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
    FastStartFailoverThreshold      = '30'
    OperationTimeout                = '30'
    FastStartFailoverLagLimit       = '180'
    CommunicationTimeout            = '180'
    FastStartFailoverAutoReinstate = 'TRUE'
    FastStartFailoverPmyShutdown    = 'TRUE'
    BystandersFollowRoleChange      = 'ALL'
Fast-Start Failover: ENABLED
Threshold:        30 seconds
Target:           dbstby
Observer:         observer_host
Lag Limit:        180 seconds
Shutdown Primary: TRUE
Auto-reinstate:   TRUE
Configuration Status:
SUCCESS
DGMGRL> show database verbose dbprim
Database - dbprim
Role:            PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
    DG_CONFIG
Properties:
    DGConnectIdentifier             = 'dbprim'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'MANUAL'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = 'dbstby'
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = ‘<sid>’
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose dbstby
Database - dbstby
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   0 seconds
Apply Lag:       0 seconds
Real Time Query: ON
Instance(s):
    DG_CONFIG
Properties:
    DGConnectIdentifier             = 'dbstby'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = 'dbprim'
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = ‘<sid>’
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
SUCCESS

Dimension mapping mixes the data completely!

[Windows, OWB 10g R2]
I have a country and a post-code table (600000 rows).
I join in the mapping the two tables and link the join columns to a dimension DIM_COUNTRIES.
Just a simple dimension with a hierarchy Continent, Country, State, County, City etc.
But this mapping loads the data completely mixed up with rows like this.
America, Monaco, CT, Aguacalientes, Norfolk Then I have replaced the dimension with a simple table and this table gets loaded correctly.
As I don’t see any error in the mapping, wath can be the cause for such a data mass?
Thanks for any help.

Sorry. I think my message is not clear.
I want to know how do I map the SURROGATE KEY column when creating a DIMENSION.
So suppose first I create a STAGING TABLE (STAGING, as I have not added any TIMESTAMP fields as suggested) as below.
CREATE TABLE dw_branch
AS
SELECT dw_branch_seq.nextval AS dw_branch_surrogate_key
, branch.branch_id
, branch.branch_code
, branch.branch_name
, city.city_id
, city.city_name
from city
, branch
where branch.city_id (+) = city.city_id
Now I want to create DIMENSION dim_branch as
CREATE DIMENSION dim_branch
LEVEL branch IS dw_branch.branch_id
LEVEL city IS dw_branch.city_id
HIERARCHY branches
branch CHILD OF
city
ATTRIBUTE branch DETERMINES (branch_code, branch_name)
ATTRIBUTE city DETERMINES (city_name)
Now, my question is:
Question A: Should the last two ATTRIBUTE clauses actually be
ATTRIBUTE branch DETERMINES (dw_branch_surrogate_key, branch_code, branch_name)
ATTRIBUTE city DETERMINES (dw_branch_surroget_key, city_name)?
In case I am not creating the STAGING TABLE dw_branch, then I would be creating the DIMENSION as below (DIMENSION based on normalised tables).
CREATE DIMENSION dim_branch
LEVEL branch IS branch.branch_id
LEVEL city IS city.city_id
HIERARCHY branches
branch CHILD OF
city
JOIN KEY branch.city_id REFERENCES city
ATTRIBUTE branch DETERMINES (branch.branch_code, branch.branch_name)
ATTRIBUTE city DETERMINES (city.city_name)
Now, my next question is
Question B: Where does the concept of SURROGATE KEY fits in this situation?
Thanks and regards,
Manoj.

Interface Mapping run time error...java.lang.nullpointerException thrown

Hi,
I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
Interface Mapping run time error...java.lang.nullpointerException thrown during application mapping.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>CAMEL_BS_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>Camel_BService_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
<SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
<SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
<SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070108</SAP:Date>
<SAP:Time>224350</SAP:Time>
<SAP:Host>gbdci550</SAP:Host>
<SAP:SystemId>PI7</SAP:SystemId>
<SAP:SystemNr>03</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
<SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>168</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>67</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
<SAP:Serialize_Children>X</SAP:Serialize_Children>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Please I request to give me some hint how to troubleshoot this issue.
Thanks a lot,
Srujan

Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
Here is the Java exception
Mappage d'interface
Can someone be helpful for that ?
Regards
Laurent
Message was edited by:
Laurent Gitton

Word couldn't send mail because of MAPI failure, Unspecified error.

This issue is crossposted in Microsoft Answers Word and OUTLOOK. I am posting here in hopes that someone at Mircrosoft may have a solution or at least elevate the issue to someone who does.
http://answers.microsoft.com/en-us/office/forum/officeversion_other-word/word-could-not-send-mail-because-of-mapi-failure/f62678fe-ef1d-42b5-8cfe-1e43d6a1d609
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/word-couldnt-send-mail-due-to-mapi-failure/1f03cf74-9258-411b-9e2b-e41cb5006d71
I dabble with VBA and write and maintain several amateur Word Add-Ins. Accordingly, I have Word 2003, 2007, 2010 and 2013 installed on my PC. They get along fine. However, I am unable to "Share" or "Send" an open Word
document as an E-mail attachment in any version! In each case Word returns an error mesage "Word couldn't send mail because of a MAPI failure, Unspecified error (the same issue occurs with Excel and Powerpoint except the error dialog is a bit different.)
Using Word 2003, I (CAN) "Send to (Mail recipient for review)" in which case OUTLOOK is opened with the document as an attachment. I can also "Send to Mail Recipient" from Windows Explorer, in which case the Word file is attached to
an OUTLOOK message, and I can create an instance of OUTLOOK and send mail from Word using VBA.
I have repaired all Office versions. I have removed the registry keys for all office versions and repaired all versions again. I have run "fixmapi" until I am blue in the face. I have renamed the MAPI32.DLL files and ran sfc \scannow
to ensure that the MAPI32.DLL file is not corrupt. In view of these actions and in view of what I can do, something tells me that the MAPI files are fine.
So what is this "Unspecified error?" This problem is rife on the internet and most of the "canned" solutions have been marked "Answered" by some MS support engineer. These "canned" solutions might have
fixed the issue at one point, but they don't work now. At least not for me.
Thanks.
Greg Maxey Please visit my website at: http://gregmaxey.mvps.org/word_tips.htm

Hello Greg,
I noted that there are 2 knowledge articles that describe scenarios where you may encounter this error.
KB 291152 You receive a "Word couldn't send mail because of MAPI failure" error message when you try to send a Word document as an e-mail attachment in Word 2002
http://support.microsoft.com/kb/291152/EN-US
KB 929362 You cannot send a file by clicking Send in a different program when Outlook 2007 is running as administrator
http://support.microsoft.com/kb/929362/EN-US
Please let me know the following:
1. What version of Outlook are you using?
2. Do you have Outlook open when you attempt the File > Share > Email as attachment from Word? If not, does the error occur if you open Outlook, open Word and then try to send the email?
3. If you close/reopen Word and then try the send again, do you get the same error?
4. Are you running either Outlook or Word in an elevated mode?
5. What happens if you start both Outlook and Word as "Run As Administrator". You may have to right-click each applications' .exe file to be able to choose the "Run As Administrator" option.
6. Do you get the same error when using File > Share > Email as attachment using Excel?
7. In Internet Explorer, open the Internet Options. On the General tab within the browsing history, delete your temporary Internet files and website files
8. Does the issue occur in selective startup mode?
Steps to setup selective startup mode:
Click on the Windows Start button, in the Search box type msconfig and then hit enter. This should open up the System Configuration Utility. Make the following adjustments within each tab.
Services Tab:
- Check the option 'Hide All Microsoft Services'
- Click on button 'Disable All'
Startup Tab:
- Click the button 'Disable All'
- Go back through the list and enable any Microsoft items
Click Ok. It will say “You must restart your computer for some of the changes
made by System Configuration to take effect”. Hit the ‘Restart’ button.
When the PC reboots try to run your test again.
To return back to a normal boot launch msconfig again and choose 'normal startup' on the general tab, click Ok and then reboot the PC.
Regards,
Dennis

Generate Flexfield and Mapping Information Process errors out

Hi,
The Generate Flexfield and Mapping Information process errors out with the following msg:
**Starts**19-OCT-2009 13:55:02
ORACLE error 6501 in FDPSTP
Cause: FDPSTP failed due to ORA-06501: PL/SQL: program error
ORA-06512: at "APPS.FND_FLEX_DSC_API", line 1626
ORA-06501: PL/SQL: program error
ORA-06512: at "APPS.FND_FLEX_DSC_API", line 925
ORA-01403: no data foun
I have created the element set with all the elements added one at a time into the element set.
Any idea on what could be the issue ?

Pl see if the steps in MOS Doc 453184.1 (ORA-01403 and ORA-06512 at HXC_CREATE_FLEX_MAPPINGS and FND_FLEX_DSC_API on Runnning hxcmprn.sql) can help
HTH
Srini

OWB Mapping and Sqlloader error.

Hi All,
OWB Config Details is as follows:
Oracle 9i Warehouse Builder Client: 9.2.0.2.8
Oracle 9i Warehouse Builder Repository: 9.2.0.2.0
I developed a mapping which involves a source text file delimited by comma with following structure.
Deptno,Dname,Loc
10,Account,New York
20,Sales,Boston
,Logistic,New Jersey
This data is uploaded into Table scott.dept.
Deptno is primary key.
The source file consist of one record with Deptno Null.
For this mapping Number of errors is set to : 0.
When the mapping is executed sqlloader rejects the record and append the same to bad file, although the sqlloader rejects the record mapping execution status is displayed as successful.
This seems to be problem since we included above mappings in process flow and depending on success of the mapping update some control table. This results in inconsistency and also loss of data since we set loading type to Truncate / Insert for the target table.
Can someone please let me know work around for this?
Thanks in Advance.
Regards,
Vidyanand

I have logged a bug (3940052) on this. As a workaround, have you tried to use an external table instead of a file, thus producing a PL/SQL map instead of SQLLoader?
Regards:
Igor

Error encountered while executing the transform project name.map name. Error:Unable to create the transform. Microsoft.XLANGs.Engine

Hi All,
I developed a Biztalk Application aims to upload a flat file data to our system MS SQL Server database. It works fine until one day, an exception is generated as below.
"Error encountered while executing the transform project name.map name. Error:Unable to create the transform. Microsoft.XLANGs.Engine"
It continues to generate an exception until I restart the Biztalk instance. And it happens occasionally, no pattern, cannot be traced and debugged.
Anybody has an idea about this error? Please help, thank you very much.
The Biztalk Server is running on Hyper-V Virtual machine, Biztalk Server 2009 on Windows Server 2008.
The Biztalk Application consists of Mapping Functoid, Orchestration, Flatfile Schema, Flatfile Disassembler Pipeline, SQL Send Port, File Receive Port and Send Port
Eric

HI Eric,
I think it might happen because of large message (Out of Memory exception). As you said you have flat file as inbound, you are doing mapping and then sending it to MSSQL
SO you can check below mentioned things
1) Any custom pipeline component is used in receive pipeline. (if so optimize the code)
2) This issue haapen only with large message (BizTalk convert flat file to XMl to if you have 1MB file corresponding XML will be of higher size)
again all thing mentioned above is assumption.
YOu can use debugdiag tool to see if memory leak is happening
http://www.microsoft.com/en-in/download/details.aspx?id=26798

LMS4.0.1 Nexus 5020 - internal error in inventory collection

Hello,
2 Nexus 5020 (SysObjId ...3.719) brings internal error in inventory collection as following:
"RICS0001: Internal Error, unable to process the collected data from the device"
whereby 2 other devices from same type, same sysobjid are working well. SDT from v401 shows this device as supported.
What can we do?
Steffen

Hi Steffen,
Try updating the MDF and device packages for RME first and check the issue..
If you have not applied the below patch before ,kindly apply this :
Download the Patch for this BUg from cisco.com and apply it ..I hope that should take care of the issue.
CSCto46927 Psu support changes from CCO to SPRIT
lms40x-win-CSCto46927-0.zip (For windows)
lms40x-sol-CSCto46927-0.tar (For solaris)
Thanks
Afroj

We are getting the following error "Complete allocation structure GA"

Hi,
Please help on the below issue:-
We are carrying settlement of order (Period end activities ) for CO88 . We are getting the following error complete allocation structure GA.
Please guide us.
Regards
Srinivas

Hi,
Go to Allocation structure and maintain the Source and Settlement cost element for various cost groups in the structure.
And maintain this Allocation Structure in the settlement profile for your Production/Process orders.
Regards
Balaji

Mapping Problem-Mapping not sufficient Error Message

Hello SDNers,
I m facing one problem, details are as below
Source Structure
MT_Source
   Invoice                               1..unbound
           Type                                          1..1
           Invoice Header                      1..1
              PartyID
                        ID                           1..1
              DocuID
                        ID                           1..1
           InvoiceLine                            1..unbound
          Item                            1.1
                 InvoiceSubline                        1.unbound
                        costCentre                          1..1
                        GL Code                          1..1
Target Structure
MT_Target
         Target                                                                     1.unbound
              Bgr00
                    Stype                                                            1..1
                    Xkeep                                                           1..1
              Bkpf                                    1..1
             Stype                                1..1
                    Tcode                                 1..1
                    Bldat                                                                1..1
                    bukrs                                  1..1
              Bseg                                    1..1
             Stype                                1..1
                    Tbnam                                 1..1
                    newbs                                                               1..1
                    wrbtr                                  1..1
                     zunor                                                                1..1
              Bseg1                                    1..unbound
             Stype                                1..1
                    Tbnam                                 1..1
                    newbs                                                               1..1
                    wrbtr                                  1..1
                     zunor                                                                1..1
Mapping need to be done in such a way like
Invoice Header must go in the corresponding fields of BKPF ,BSEG
Invoice Line fields must go in the corresponding fields of BSEG1
I tried split by Value with a user defined function copyPerValue
public void copyPerValue(String[] a,String[] b,ResultList result,Container container){
for(int i=0;i<=a.length;i++)
          result.addValue(b[0]);
InvoiceLine----
                                        CopyPerValue ->SplitBYValue[EachValue]->bldat
DocumentDateTime----
but I m getting Mapping not sufficient Error Message.
Pls help me in getting resolve this problem.
Thx in advance

Hi;
Just check that all the mandatory fields (1.1 occurances) are mapped.
No node in the target message should be left red.
Mudit

Need help in Component Mapping - "Mapping has not been completed" !

Hi Experts,
i read the SAP Galileo Press Book "Web Dynpro for ABAP" and i try in Chapter 2 some exercise for Multi-Component-Architecture.
In this Chapcter i have 2 Components "Main" and "Nations". In one of this Components i created Node´s and Attributes in the Context of Component-Controller. After this i changed to the View and tryed to mapping the Component-Controller and View.
Before i explain what i have done, i want show us the following Error:
Note
-> The following error text was processed in system FID : Adapter error in TEXT_VIEW "TV_LANDX50" of view "ZZWDC_CHAP02_NATIONS.V_NATIONS": Context binding of property TEXT cannot be resolved: The Mapping to Node COMPONENTCONTROLLER.1.T005T Has Not Been Completed.
-> The error occurred on application server fidvfid0_FID_00 and in work process 0 .
-> The termination type was: RABAX_STATE
-> The ABAP call hierarchy was:
-> Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
-> Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
-> Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP

ETN_58 wrote:
Hi Experts,
>
> i read the SAP Galileo Press Book "Web Dynpro for ABAP" and i try in Chapter 2 some exercise for Multi-Component-Architecture.
>
> In this Chapcter i have 2 Components "Main" and "Nations". In one of this Components i created Node´s and Attributes in the Context of Component-Controller. After this i changed to the View and tryed to mapping the Component-Controller and View.
>
> Before i explain what i have done, i want show us the following Error:
>
> Note
>
> -> The following error text was processed in system FID : Adapter error in TEXT_VIEW "TV_LANDX50" of view "ZZWDC_CHAP02_NATIONS.V_NATIONS": Context binding of property TEXT cannot be resolved: The Mapping to Node COMPONENTCONTROLLER.1.T005T Has Not Been Completed.
> -> The error occurred on application server fidvfid0_FID_00 and in work process 0 .
> -> The termination type was: RABAX_STATE
> -> The ABAP call hierarchy was:
> -> Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
> -> Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
> -> Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
hello,
i think you missed mapping the layout with the context attributes....check out the property of all the elements in the view, if not mapped map it by selecting the attribute from the node.
Regards,
Sahai.S

Access an interface node : the mapping has not been completed

Hello all,
by getting an element of interface-node within a component I get follow error message
"the mapping to node COMPONENTCONTROLLER.1.INIT_DATA" has not been completed"
Can anybody say me, what does it mean?
Some more information (in case for somebody need it):
1. I have a component A, where I have defined usage component of component B.
2. Component B has an interface node INIT_DATA, which is mapped with the node INIT_DATA of component A.
3. I set attributes of node INIT_DATA of component A and expect, that those values will be assigned to the node INIT_DATA of component B (becouse they are mapped)
4. by doing it within a component A:
lo_node = wd_context->get_child_node( name = if_componentcontroller->wdctx=>init_data).
lo_elem->get_element( ).
lo_elem->set_attribute(....).
I get this error message:
"the mapping to node COMPONENTCONTROLLER.1.INIT_DATA" has not been completed"
Please let me know, what I do wrong?
thanks in advance
Anna

Hi Anna,
You should not be having the node INIT_DATA defined separately in both components. It should be defined only in component B and marked as Interface node. Now when you define a usage of component B in component A, you will be able to see this node. You need to map this in component A by drag and drop.
Also, in the properties tab of the component controller of component A, declare the usage of component B using the F4 help. I think that should solve your problem.
Regards
Nithya

Data Load errors in Inventory

Hello,
I am trying to load 2LIS_03_BF data to the cube via PSA. The data is loading fine in to the PSA but while updating from PSA to the cube I am getting the following error message.
An error occurred when reading PSA data
I am getting the following short dump (ST22)
CONVERSION_CODEPAGE_UNKNOWN
Hope will find a solution
full points will be awarded
thank you in anticipation

Hi,
For this type of requirements, itis better to upload the data to Z-cube from BF datasource. In that cube, you can take Movement Type characterstic , so that you can give reports on movement type wise.
You can not include Movement type characterstic into Inventory(stock) cube.What I mean is you need a Cube purely gets the data from BF and this cube will not have any Stock Keyfigures.
Or take a Z-KF into 0IC_C03(or you custom inventory cube) , But in update rule give a logic so that system fills the value if and only if movement type of the record is 321
you can go with Z-KF on your cube.
But in the mapping you have to give communication structure field either with filteration on other fileds or with out any if conditions .But you can not use infocube Kf as source for this new KF as you mentioned.
use the movement type in IS and D/C indicator to filter the quantity like
if comm_structure-movetype eq '321' and comm_structure-d/cindicator eq 's' then
result = comm_structure-cpquab (this field is populating the stock quantity)
so i think this code will bring all the issue of movement type 321 to my key figure
Regards,
Hareesh

MAP 7.0 errors completing inventory

Similar Messages

Maybe you are looking for