Login request messages

Hi,
Something really weird just happened to me... after restoring my iPhone 4 using iCloud I started getting login request messages with the above username (hapa**** @hotmail.com)... I have no idea what is this email and I can't get rid of this... any idea?
P.S - I googled it and I saw another person with the same exact email problem but he didn't answer me
<Email Edited by Host>

Oh my God!
The exact same thing has been happening to me for almost an year! Itunes keep  asking me the password to this account.
How do I solve this problem?
This is an old Iphone 4S that my sister used to use but this is not her´s account. How can I find out which songs are from this hapa**** @hotmail.com account?
Thanks!

Similar Messages

  • Wsdl validation fails for request message payload from custom schema

    Hello. I am having a problem which I cannot seem to work around. I have defined a schema to serve as a template for the request message payload of a bpel process. The schema is very simple:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:logininfo="http://sru/logininfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru/profile" targetNamespace="http://sru/logininfo" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:import namespace="http://sru/profile" schemaLocation="http://sru/profile.xsd"/>
         <xs:element name="logininfo" type="logininfo:logininfoType">
              <xs:annotation>
                   <xs:documentation>Needed information for SRU Login</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="logininfoType">
              <xs:all>
                   <xs:element name="email" type="sru:emailType"/>
                   <xs:element name="password">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="product" type="xs:string"/>
                   <xs:element name="ip" type="sru:ipType"/>
                   <xs:element name="timestamp" type="xs:dateTime"/>
                   <xs:element name="xpath" type="xs:string"/>
              </xs:all>
         </xs:complexType>
    </xs:schema>
    (The schema depends on another, which I have placed at the end of this message).
    I import it into the bpel process designer with no problems.
    Upon defining the payload of the request message type to be the {http://sru/logininfo}logininfoType, the WSDL file does not validate anymore:
    Validating WSDL...
    Validating E:\OraBPELPM_1\integration\jdev\jdev\mywork\SRU\BPELProcess5\BPELProcess5.wsdl
    Schema type not found: QName(http://sru/logininfo, logininfoType)
    Validate WSDL: has errors.
    Any ideas?
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns="http://sru/profile" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="http://sru/profile" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:schemaURL="http://sru/profile.xsd">
         <xs:annotation>
              <xs:documentation>Joel Salmerón Viver</xs:documentation>
              <xs:documentation xml:lang="en">General purpose internet profile schema</xs:documentation>
         </xs:annotation>
         <xs:simpleType name="emailType">
              <xs:restriction base="xs:string">
                   <xs:maxLength value="255"/>
                   <xs:pattern value="[a-z0-9]([a-z0-9\._][a-z0-9]+)*@[a-z0-9]([a-z0-9\.\-][a-z0-9]+)*\.[a-z]{2,6}"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ipType">
              <xs:restriction base="xs:string">
                   <xs:pattern value="((\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])\.){3}(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="labelType">
              <xs:restriction base="xs:string">
                   <xs:maxLength value="32"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="addressType" xdb:SQLType="ADDRESSTYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="lines" type="linesType" minOccurs="0" xdb:SQLName="lines" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="linesKey">
                             <xs:selector xpath="line"/>
                             <xs:field xpath="@num"/>
                        </xs:key>
                   </xs:element>
                   <xs:element name="city" xdb:SQLName="city" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="postalcode" xdb:SQLName="postalcode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="16"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="countrycode" xdb:SQLName="countrycode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="2"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
              </xs:all>
              <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
              <xs:attribute name="verified" type="xs:boolean" use="required" xdb:SQLName="verified" xdb:SQLType="RAW"/>
         </xs:complexType>
         <xs:complexType name="lineType" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="num" type="xs:positiveInteger" use="required" xdb:SQLName="num" xdb:SQLType="NUMBER"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="loginType" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="registered_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="registered_date" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_date" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_ip" type="ipType" minOccurs="0" xdb:SQLName="lastlogin_ip" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_time" type="xs:time" minOccurs="0" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_time" xdb:SQLInline="true"/>
              </xs:all>
              <xs:attribute name="product" use="required" xdb:SQLName="product" xdb:SQLType="VARCHAR2">
                   <xs:simpleType>
                        <xs:restriction base="xs:string">
                             <xs:maxLength value="32"/>
                        </xs:restriction>
                   </xs:simpleType>
              </xs:attribute>
              <xs:attribute name="status" type="xs:integer" use="required" xdb:SQLName="status" xdb:SQLType="NUMBER"/>
         </xs:complexType>
         <xs:complexType name="addressesType" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="address" maxOccurs="unbounded" xdb:defaultTable="PROFILE_ADDRESSES" xdb:SQLName="address" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:defaultTableSchema="SRU" xdb:SQLCollType="address360_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                        <xs:complexType xdb:SQLType="address358_T" xdb:SQLSchema="SRU">
                             <xs:complexContent>
                                  <xs:extension base="addressType"/>
                             </xs:complexContent>
                        </xs:complexType>
                   </xs:element>
              </xs:sequence>
              <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
         </xs:complexType>
         <xs:complexType name="phonesType" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="phone" type="phoneType" maxOccurs="unbounded" xdb:SQLName="phone" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="phone363_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
              </xs:sequence>
              <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
         </xs:complexType>
         <xs:complexType name="loginsType" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="login" type="loginType" maxOccurs="unbounded" xdb:SQLName="login" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="login366_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                        <xs:key name="loginKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@product"/>
                        </xs:key>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="phoneType" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="phonenumberType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="profileType" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="firstname" xdb:SQLName="firstname" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="surname1" xdb:SQLName="surname1" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="surname2" minOccurs="0" xdb:SQLName="surname2" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="gender">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="1"/>
                                  <xs:enumeration value="M"/>
                                  <xs:enumeration value="F"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="alt_email" type="emailType" minOccurs="0" xdb:SQLName="alt_email" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="addresses" type="addressesType" minOccurs="0" xdb:SQLName="addresses" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="addressesKey">
                             <xs:selector xpath="address"/>
                             <xs:field xpath="@label"/>
                        </xs:key>
                        <xs:keyref name="addressRef" refer="addressesKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@main"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="phones" type="phonesType" minOccurs="0" xdb:SQLName="phones" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="phoneKey">
                             <xs:selector xpath="phone"/>
                             <xs:field xpath="@label"/>
                        </xs:key>
                        <xs:keyref name="phoneRef" refer="phoneKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@main"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="language" type="xs:language" xdb:SQLName="language" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="logins" type="loginsType" minOccurs="0" xdb:SQLName="logins" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="loginsKey">
                             <xs:selector xpath="login"/>
                             <xs:field xpath="@product"/>
                        </xs:key>
                   </xs:element>
                   <xs:element name="origin" minOccurs="0" xdb:SQLName="origin" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:annotation>
                             <xs:documentation>iso3166 a2 country code</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="2"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="creation_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="creation_date" xdb:SQLInline="true"/>
                   <xs:element name="modified_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="modified_date" xdb:SQLInline="true"/>
                   <xs:element name="password" xdb:SQLName="password" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                                  <xs:pattern value="[a-zA-Z0-9]+"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="hint" minOccurs="0" xdb:SQLName="hint" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="additional" type="xs:anyType" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>future expansion</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:all>
              <xs:attribute name="email" type="emailType" use="required" xdb:SQLName="email" xdb:SQLType="VARCHAR2"/>
              <xs:attribute name="active" type="xs:boolean" use="required"/>
         </xs:complexType>
         <xs:complexType name="phonenumberType" xdb:SQLType="PHONENUMBERTYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:element name="profile" type="profileType" xdb:defaultTable="PROFILES" xdb:SQLName="profile" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU" xdb:defaultTableSchema="SRU"/>
         <xs:complexType name="linesType" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="line" type="lineType" maxOccurs="unbounded" xdb:SQLName="line" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="line354_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>

    IT would help if the people that are working this issue would post the resolve of their problems. Every post I see with this problem someone from oracle replies with needing the source project to replicate the issue and the thread dies....

  • Translation of "Invalid Login Credentials" message

    Hi
    I've application (just) in non-english language. Shared Component / Globalization / Text Messages works well for the translation of "Next/Prev", "Error" texts, but where to translate invalid login error message?
    Roman

    I do not assume you translate APEX into Czech language
    Not yet.
    Your function can redirect to a page that shows the message you like. For example, if you wanted to redisplay the login page with the message, just do something like this:
    owa_util.redirect_url('f?p=' || v('APP_ID') || ':101:' || v('APP_SESSION') || ':MSG' );
    apex_application.g_unrecoverable_error := true;
    return false;
    Then adjust your login page so that a message appears if the "request" value is 'MSG'. The redirect_url shown above sets the request value to 'MSG'. Normally the login page would not show the message because that request value would not be present.
    Scott

  • Proxy Login Request on Java applets

    • 10.4.5 Client
    • Windows 2.3k ISA 2005 Proxy Server
    • Users' fileserving to Win2.3k - ADmitMac for AD integration
    The client is a test machine on which I build campus master NetInstall images. In my testing procedures I've come across a bizarre problem with Java in the browsers (IE, Safari, & FireFox).
    We use ISA proxy server with web filtering, and users must authenticate to the proxy. On a new user's first use of any browser, the proxy username & password are requested, and the Add to Keychain checkbox is available. If the user checks the box, no further proxy login requests are made; the user's Keychain is updated with the proxy information.
    On pages with Java applets, however, each and every applet will ask for a proxy login, but the login window does not offer a Add to Keychain checkbox! If a page has 15 applets on it, the user will be asked 15 times to authenticate against the proxy.
    Naturally, this is a BIG problem, especially when several of the sites our teachers use in classes and labs contain many Java applets.
    On the web, there is almost nothing concerning setting up Java with proxy servers, as all Apple Java from v. 1.4.2 onwards picks up proxy information from the system's network settings.
    On the Apple Developer site, Tech Note QA1263 demonstrates a way of setting HTTPS proxy settings by entering text strings in the 1.3.1 and 1.4.1 Plugin Settings apps Java Runtime Parameters. The same capability exists in the J2SE 5.0 Java Preferences app, too. Unfortunately, the Java applets do not use HTTPS, so far as I can tell, so this remedy is useless.
    Any clues I can pursue? Any help or fixes?
    Thanks in advance!
    Derek I Smith
    Systems & Network Admin
    Riverdale Country School
    www.riverdale.edu
    eMacs,g4s,QSs,B/Ws,iMacs,G5,G5 XServe, etc   Mac OS X (10.4.5)  

    After some more research with the J2SE 5.0 Java Preferences app, I turned on the Java console, booted Safari and went to my favorite Java applet - babynamewizard. This is the output of the console log. From what I can glean, the plug-in sees the proxy server settings as it should, and reports them.
    In addition, the J2SE 5.0 Java Preferences app allows you to turn off all security settings. No change in behavior.
    The Log:
    Java Plug-in 1.5.0
    Using JRE version 1.5.0_05 Java HotSpot(TM) Client VM
    User home directory = /Users/admin
    network: Loading user-defined proxy configuration ...
    network: Done.
    network: Loading proxy configuration from Netscape Navigator ...
    network: Done.
    network: Loading manual proxy configuration ...
    network: Done.
    network: Proxy Configuration: Manual Configuration
    Proxy: http=pcproxy.riverdale.edu:8080,https=pcproxy.riverdale.edu:8080,ftp=pcproxy.ri verdale.edu:8080,gopher=pcproxy.riverdale.edu:8080,socks=pcproxy.riverdale.edu:8 080
    Proxy Overrides:
    basic: Cache is enabled
    basic: Location: /Users/admin/Library/Caches/Java/cache/javapi/v1.0
    basic: Maximum size: unlimited
    basic: Compression level: 0
    c: clear console window
    f: finalize objects on finalization queue
    g: garbage collect
    h: display this help message
    l: dump classloader list
    m: print memory usage
    o: trigger logging
    p: reload proxy configuration
    q: hide console
    r: reload policy configuration
    s: dump system and deployment properties
    t: dump thread list
    v: dump thread stack
    x: clear classloader cache
    0-5: set trace level to <n>
    basic: Referencing classloader: sun.plugin.ClassLoaderInfo@fb6354, refcount=1
    basic: Added progress listener: sun.plugin.util.GrayBoxPainter@dc0e7a
    basic: Loading applet ...
    basic: Initializing applet ...
    basic: Starting applet ...
    network: Connecting http://babynamewizard.com/namevoyager/nametide2.jar with proxy=HTTP @ pcproxy.riverdale.edu/172.16.1.52:8080
    network: Connecting http://babynamewizard.com/namevoyager/nametide2.jar with cookie "s_cc=true; s_sq=%5B%5BB%5D%5D"
    network: Firewall authentication: site=pcproxy.riverdale.edu/172.16.1.52:8080, protocol=http, prompt=ENKI.riverdale.edu, scheme=basic
    basic: User selected: 0
    ~ ~ ~
    The proxy login window appears at this point and I authenticate to the proxy
    The log continues...
    ~ ~ ~
    network: Connecting http://babynamewizard.com/namevoyager/nametide2.jar with proxy=HTTP @ pcproxy.riverdale.edu/172.16.1.52:8080
    basic: Loading http://babynamewizard.com/namevoyager/nametide2.jar from cache
    basic: No certificate info, this is unsigned JAR file.
    network: Connecting http://babynamewizard.com/namevoyager/namedb.zip with proxy=HTTP @ pcproxy.riverdale.edu/172.16.1.52:8080
    network: Connecting http://babynamewizard.com/namevoyager/namedb.zip with cookie "s_cc=true; s_sq=%5B%5BB%5D%5D"
    Columns found: 28
    Num years: 13
    YEAR NAME: 1880s
    YEAR NAME: 1890s
    YEAR NAME: 1900s
    YEAR NAME: 1910s
    YEAR NAME: 1920s
    YEAR NAME: 1930s
    YEAR NAME: 1940s
    YEAR NAME: 1950s
    YEAR NAME: 1960s
    YEAR NAME: 1970s
    YEAR NAME: 1980s
    YEAR NAME: 1990s
    YEAR NAME: 2004
    Num names: 5251
    0 --> 923475.0
    1 --> 915444.0
    2 --> 905002.0
    3 --> 910731.0
    4 --> 915165.0
    5 --> 924335.0
    6 --> 938721.0
    7 --> 940141.0
    8 --> 923814.0
    9 --> 869609.0
    10 --> 848116.0
    11 --> 800666.0
    12 --> 759055.0
    Rank misses: 21
    0.15
    0.4475
    0.395
    0.3425
    0.29000002
    0.23750001
    0.185
    0.48250002
    0.43
    0.3775
    0.325
    0.2725
    0.22
    0.1675
    0.465
    0.4125
    0.36
    0.3075
    0.255
    0.2025
    ~ ~ ~
    The applet runs

  • Request message mapping giving blank xml message

    I was trying a scenario JDBC-> XI -> RFC for tranporting the db table data from sqlserver to sap r/3.
    At the time of designing the mapping is working correctly.
    But in the pipeline step "Request message mapping" it is generating the inbound message but with any values from outbound source message.
    source message (xml ) structure
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:CUST_REQ_MT xmlns:ns0="urn:sqlserver:vendor">
      <row>
        <NAME></NAME>
        <ADDRESS></ADDRESS>
        <AGE></AGE>
        <LOGIN></LOGIN>
        <PASSWORD></PASSWORD>
      </row>
    </ns0:CUST_REQ_MT>
    and target message structure is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:ZBAPI_UPDATE_JDBC xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
      <UPDATE>
        <item>
          <NAME></NAME>
          <ADDRESS></ADDRESS>
          <AGE></AGE>
          <LOGIN></LOGIN>
          <PASSWORD></PASSWORD>
        </item>
      </UPDATE>
    </ns0:ZBAPI_UPDATE_JDBC>
    I have used the Graphical mapping tool for mapping these two MT's.
    the payload in the request message mapping step is as follows:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:ZBAPI_UPDATE_JDBC xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
    - <UPDATE>
      <item />
      </UPDATE>
      </ns0:ZBAPI_UPDATE_JDBC>
    here you can see a blank tag <item/>.
    How can i resolve this issue. I can not see any error anywhere.
    Regards,
    Gopesh

    Hi,
    It is not the issue of the datatype for outbound message for jdbc sender.
    I have done the Graphical mapping and mapped the sourse message type to target message type (which is a rfc xml format request message type).
    But when all the IR and ID objects activated and it comes to Runtime (integration server) then it is unable to execute the mapping in the xi pipeline step "Request Message Mapping" and generating a blank xml element as i have described earlier in my message.
    What should i do or where should i check for the possible reasons and what could be the solution for this issue.
    Regards
    Gopesh

  • SOAP Login Request Problem

    Hi,
    I have been trying to send a login request via Pear SOAP, without success.  Any ideas about what is wrong with the request?
    The Request:
    POST /dswsbobje/services/Session HTTP/1.0
    User-Agent: PEAR-SOAP 0.12.0-beta
    Host: 192.168.130.52
    Content-Type: text/xml; charset=UTF-8
    Content-Length: 615
    SOAPAction: "http://session.dsws.businessobjects.com/2007/06/01/login"
    Connection: close
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:ns4="http://session.dsws.businessobjects.com/2007/06/01">
    <SOAP-ENV:Body>
    <ns4:login>
    <credential xsi:type="EnterpriseCredential" AuthType="secEnterprise" Login="Administrator" Password="Password" Domain="ptgdw3" ReportedHostName="ptgdw3:6400"/>
    <version></version></ns4:login>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    ... and the response:
    HTTP/1.1 500 Internal Server Error
    Server: Apache-Coyote/1.1
    Content-Type: text/xml;charset=UTF-8
    Date: Wed, 04 Mar 2009 17:52:11 GMT
    Connection: close
    <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>java.lang.NullPointerException</faultstring><detail><DSWSException xmlns="http://dsws.businessobjects.com/2007/06/01"><ID xmlns="">S2</ID><Message xmlns="">login exception (Error: WSE 99998)</Message><Operation xmlns="">http://session.dsws.businessobjects.com/2007/06/01/login</Operation><CallStackTrace xmlns="">java.lang.NullPointerException&#xd;
        at com.businessobjects.dsws.session.SessionSkeleton.login(Unknown Source)&#xd;
        at com.businessobjects.dsws.session.SessionMessageReceiverInOut.invokeBusinessLogic(Unknown Source)&#xd;
        at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)&#xd;
        at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)&#xd;
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)&#xd;
        at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)&#xd;
        at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)&#xd;
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)&#xd;
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)&#xd;
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)&#xd;
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)&#xd;
        at com.businessobjects.dsws.wsc.common.axis.FlashFilter.doFilter(Unknown Source)&#xd;
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)&#xd;
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)&#xd;
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)&#xd;
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)&#xd;
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)&#xd;
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)&#xd;
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)&#xd;
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)&#xd;
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)&#xd;
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)&#xd;
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)&#xd;
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)&#xd;
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)&#xd;
        at java.lang.Thread.run(Thread.java:595)&#xd;

    Hi Matt,
    Unfortunately there isn't anything currently available on the proper structure of the soap request to communicate with the web services SDK.  What I would recommend doing is creating a regular web services SDK app (Or just download a sample), and then use a sniffer to look at the soap messages being sent back and forth.  You should be able to take those messages and modify them to suit your needs.
    Shawn

  • Login request failed, when logging in from the iPhone simulator.

    Hi all,
    I am currently working on a setup, based on the Co-innovation Architecture with a SUP 2.0 server and SAP Netweaver Mobile 7.1. We have created a SWCV in Netweaver Mobile and deployed it SUP 2.0 and generated Objective C code.
    The iOS 4.3 simulator is able to connect to the SUP server, and the device is registered in the control center, thus a "Login request failed" is thrown.
    Here are the logs from the SUP server:
    2011-11-24 11:45:34 INFO DataServices sup.mbs.10 [com.sybase.vader.mms.DataServiceImpl]9#78311995 supAdmin d1_mypackage_mdc.1_0 (sup.mbs.10) com.sybase.vader.mms.DataServiceImpl::execute:238 - Response From Operation: doec.execute {response={content={}, id=1322131361, pkg=mypackage_MDC:1.0, method=loginFailed, loginFailed=true, log=[{"timestamp":"2011-11-24 11:45:34","message":"No Subscription Found","level":"error","code":404}], cid=9#78311995}, pushTo=sup.mbs.moca.5}
    2011-11-24 11:45:34 DEBUG DOEC sup.mbs.10 [com.sybase.vader.sap.doe.SapDoeConnectorOperation]execute( login ) --> result:
    | cid : 9#78311995 : 10
    | log : [{"timestamp":"2011-11-24 11:45:34","message":"No Subscription Found","level":"error","code":404}]
    | loginFailed : true
    | method : loginFailed : 11
    | pkg : MYPACKAGE_MDC:1.0 : 19
    | id : 1322131361 : 10
    | content : {}
    DOE-C Response Message
    2011-11-24 11:45:34 WARN DOEC sup.mbs.10 [com.sybase.vader.sap.doe.SapDoeConnectorOperation]Login request failed:
    | cid : 9#78311995 : 10
    | pid : moca://SIMULATOR-MAC2SIM2__SUP101 : 33
    | method : login : 5
    | pushTo : sup.mbs.moca.5 : 14
    | pkg : MYPACKAGE_MDC:1.0 : 19
    | ppm : eyJsYW5ndWFnZSI6bnVsbCwidXNlcm5hbWUiOiJzdXBBZG1pbiIsInBhc3N3b3JkIjoiczNwQWRtaW4ifQ== : 84
    | replyTo : sup.mbs.moca.5 : 14
    | upa : *
    | content : {}
    | id : 1322131361 : 10
    2011-11-24 11:45:34 DEBUG DOEC sup.mbs.10 [com.sybase.vader.sap.doe.SapDoeConnectorOperation]execute --> login
    2011-11-24 11:45:34 TRACE DataServices sup.mbs.10 [com.sybase.vader.service.interaction.PipelineCompositeInteractionOperation] 9#78311995 supAdmin d1_mypackage_mdc.1_0 (sup.mbs.10) com.sybase.vader.service.interaction.PipelineCompositeInteractionOperation]Invoking d1_mypackage_mdc_1_0_subscriptions.findSubscriptionByClientInteractionOperationBean.getResult
    It looks like it is the doe-c throwing the error. I am able to ping Netweaver Mobile from the control center, with the tech user defined.
    I hope you have any suggestions.
    /Nima
    Edited by: NimaZandi on Nov 24, 2011 12:48 PM

    Hi Nima,
    Were you able to resolve this issue? I am also facing a similar problem.
    Thanks,
    Krishneel

  • How to store the value of request message and use it in Response mapping

    Hi All,
    We have an requirement where we need to store the data coming in Request Mapping and use the stored value in Response Mapping. Can anybody help us in how to proceed?
    Thanks
    Sujata

    Hi!
    In Mapping you may use the RFC Lookup function to store values in database table during request mapping and to read values from database table during response mapping.
    You can also use an ABAP or Java Mapping "in front of your" message mapping to store/read the values.
    You can also use an Adapter Module (if applicable for the adapter type you use) and/or a UDF to store the data e.g. in Dynmaic Configuration Header of Request Message and to read these data from Dynamic Configuration Header of Response Message. But this works only for synchronous scenarios (and it means overhead in your message traffic).
    Hope these thinkings help you o find the most suitable way for your concrete scenario!
    Regards,
    Volker
    Note:
    These techniques help you to avoid using BPM.
    Edited by: Volker Kolberg on Aug 27, 2009 11:18 AM

  • Request Message mapping in SXMB_MONI for File - RFC - File without BPM

    Hi ,
    In my File-RFC-File scenario, the messages are processed successfully.
    but when i look into the SXMB_MONI for File to RFC step, the records are present only till the  Message split According to Receiver List and not able to see the records from Request Message mapping step onwards.it contains
    <?xml version="1.0" encoding="UTF-8" ?>
      <ns1:Z_PI_LOTUSNOTES_UNIFORM xmlns:ns1="urn:sap-com:document:sap:rfc:functions" />
    in my mapping for the receiver RFC i have not done the mapping for all the fields. few fields i have disabled. whether this could create a problem in message mapping. pls let me know what needs to be done.

    Is it only for this scenario that the above display issue is occuring or is it for all scenarios?
    If onlt a particular Pipeline steps are displayed then you can check what is the TRACE level set in SXMB_ADM --> Integration Engine Configuration --> and check if the TRACE parameter is set to at least 2 (max is 3 which will ensure that your DB will get full quickly)
    For more information refer: /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    Regards,
    Abhishek.

  • RFC_to_File scenario: error in request message mapping

    Hi!
    I am configuring RFC_to_File scenario.
    The error at the begining is:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT
    : Fatal Error: com.sap.engine.lib.xml.parser.Parser
    Exception of class CX_XMS_SYSERR_MAPPING
    When I display the request message mapping are of the message I can see:
    <Trace level="1" type="T">Interface-Mapping http://www.sap-press.de/xi/training/PBU_00 IM_Z_RFB_MATERIALEINGABE_PBU_zu_MI_Material_Async_In</Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT_Material_</Trace>
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    Holger,
    Message Mapping Failed.
    >com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data >sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    You are Passing Char to a field, which is not as per the Message Mapping rule
    Cheers
    Agasthuri Doss

  • Message getting struck at Request Message mapping

    Hi All,
    In our interface we have Proxy to HTTP scenario.  When we trigger data from R/3 system the data is getting blocked at SAP XI system.
    In SXMB_MONI when we see the status of the message it doesnot show any error status flag comes with a grey dot .
    Generally as per the XI Message process flow it should be some thing like this
    Inbound message
    Receiver Identification
    Interface determination
    Message Branch According to receiver list
    Request message Mapping
    Technical Routing
    Call Adapter
    Response
    When we expand and see the message monitoring it shows the following steps -
    Inbound message
    Receiver Identification
    Interface determination
    Message Branch According to receiver list
    there is no error messages and you dont see any steps in monitoring after this.
    Trace level is set to 3 and also set trace enable for sync interfaces.
    Please let me know if some one faced this issue and how to resolve this.
    Regards,
    Reddy
    Edited by: Nanda kishore Reddy Narapu Reddy on Apr 8, 2008 5:31 PM

    Hi Srinivas,
    If receiver determination gets fail then it should give a error in SXMB_MONI messages.
    In the trace messages of the "Message Branch According to Receiver list" step in SXMB_MONI we are getting the details of the receiver and also the Communication channel need to be used also correctly.
    I would like to stress that after this step in sxmb_moni it should trigger "Request message mapping" step  but it is got getting triggered.
    Pls let me know if some one faced this issue or is it because of some cache related issue which is stopping the call to trigger message mapping.
    Reagrds,
    Reddy

  • How to fill Request Message ID in SXMB_MONI

    Hi,
    I have Abap proxy inbound -outbound asynchronous communication between XI and ERP backend .
    XI sends a kind of requests messages and the backend sends back messages with a kind of response.
    In the Tc:SXMB_MONI  I want to see the correlation between these two messages - for instance, to have an entry in column u201COriginal Message IDu201D or u201CRequest Message IDu201D, like it is made in synchronous communication.
    I think I need to fill the message header (e.g. field Main/RefToMessageID) in the outbound proxy on the backend, but I donu2019t know how to do it. .
    Thanks for your help,
    Janos

    Hi janos
    Then i can suggest a way to meet this. There is no standard way to do it.
    To get the message ID from the message you need to capture that in mapping.
    This code should help you.
    java.util.Map map = container.getTransformationParameters();
    String msgid = (String) map.get ( StreamTransformationConstants.MESSAGE_ID);
    return msgid;
    Now Create a table either in Non SAP or SAP and do a lookup to write the values. I recommend create a Z table in XI and use RFC lookup to write values to it.
    Now just write simple ABAP report to fetch these and give it to any one.
    Moreover extend the report to get the values from SXMSMAST in XI to get payload attached to that Message ID.
    Thanks
    Gaurav

  • RFC Function module-With Only Request message

    Hi
    i need a RFC with only Request message and Response message is not required.
    please help me, how to create a RFC function module with out Response message, and it should contain only Request message.
    i have created RFC in this way:
    RFC doesn't contain neither import nor export parameters. and i have defined one table in TABLE tab which refers to a ztable created already.
    when i imported RFC into XI i came to know that RFC has both Request and Response messages, but i don't need Response message.
    Thanks in advance..help would be appreciated
    Regards,
    Rajesh

    Thankx Michal,
    I have written ZRFC this way:
    insert ZMM_AUTO_GR from INPUT_TABLE .
      if sy-subrc = 0.
        commit work.
      else.
       rollback work.
    im not using neither import nor export parameters..but using only tables parameters. but when imported in XI im getting same table  structure in both request an response.
    please suggest what changes required in above code to invoke my ZRFC in async way.
    you will not get any response in XI- what chages required in my code to dnt get .reponse in XI.
    appreciate your help.
    Regards,
    Rajesh.

  • RFC to SOAP Interface - Problem in Request Message Mapping

    Dear All,
    We are working on RFC to SOAP Scenario i.e. pulling out data from an WebService from SAP via PI.
    In Request Message Mapping, when the wsdl file is uploaded as Target Message, the wsdl request shows the nested elements like below.
    <Request>
       <Request_New>
          <PAR1>xyz</PAR1>
          <PAR2>123</PAR2>
       </Request_New>
    </Request>
    But the desired Request should go like below.
    <Request>
       <PAR1>xyz</PAR1>
       <PAR2>123</PAR2>
    </Request>
    Hence it gives an error saying that the tag Request_New does not exist.

    Dear All,
    Our target webservice cotains multiple methods.
    The every method contains its corresponding request, response and SQL ecxeption as messages.
    In case of request structures, every method (except crmPaymentReceived) contains more than 1 root element.
    So while calling those methods having more than 1 root element, the additional header tag will always appear(not avoidable) in the request coming from SAP PI.
    For Example,
    Request Structure for method u2018isLoginIdExistu2019 (having more than 1 root element)
    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
    <ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing">      -
    >>>>>  u201CThis Header tag will always appear u201D
    <isLoginIdExistin0>asp</isLoginIdExistin0>
    <isLoginIdExistin1>1</isLoginIdExistin1>
    </ns1:isLoginIdExistRequest>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the error(saying that ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing" does not exists).
    Request Structure for method u2018crmPaymentReceivedu2019 (having only 1 root element)
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema-instance xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Body>
    <ns1:crmPaymentReceivedin0 xmlns:ns1="http://netpricing">false</ns1:crmPaymentReceivedin0>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the success response.
    I tested their wsdl URL in XMLspy and wizdal(a wsdl testing tool), it shows request in the format having only root elements and not the header tags.
    But header tags will always appear when header tag contains more than 1 root element.
    Can anybody suggest me how do I tackle this?
    Thanks in Advance.

  • Request message mapping failed in QAS server

    Hi ,
    I've transported the Developed  objects from DEV Server to QAS Server using CTS method , now when i m making any changes in the development system and re transporting it back to quality server , its showing one or the other error ,
    In one case it shows "Request message mapping failed"  just we added one filed and mapped it. The filed can be seen in the repository but in the moni it says this filed is missing  even though it is working fine in development, but in quality , i dont know why this problem is coming
    The scenario is jdbc -
    > xi ---> proxy,
    this problem is only is quality , in dev its working fine
    pl help  , i running short of time , 
    rgds
    mojib

    Ravi,
    In test tab , both in message mapping and configuration , its successful but still this error..
    rgds
    mojib

Maybe you are looking for