My call to AppleCare re. my four faults

Amongst the several glitches/faults concerning Lion, I rang Applecare (complimentary for 3months after purchase of my iMac) about four of them and the result might be of interest to others:
MOUSE GOING AWOL I am typing in a Word doc., email, Apple Discussion thread, and the Magic Mouse disconnects with an image of the mouse on the screen and “Connection Lost”. I have to do Finder > Preferences > Mouse, and get “No mouse detected” (or similar). I press Continue and get “Searching for mouse”. After about 40 secs.The mouse returns. This happens about four times a day, and many people on this Discussion have the same problem. (No problem with the keyboard or trackpad.)
ANSWER Take my mouse to my dealer (who is a repairer) and get a new mouse. The Applecare guy will report this fault to his techies.
THE MOUSE INSERTION “I” BEAM POINTER CHANGES TO THE ARROW POINTER, but only in the Reply window of Apple Discussions. This prevents text insertion and lasts for about40 seconds until the “I” beam returns. (Again, no problem with the trackpad.)
ANSWER “I get this also”. Perhaps something wrong with Apple Discussions.
MAIL: INBOXES OFTEN SHOW A SMALL TRIANGLE INSIDE A CIRCLE. No new message destined for thatmailbox can be detected. Solution is to quit Mail and re-launch.
ANSWER: This icon reveals intermittent loss of Internet connection. COMMENT: I think he is correct: I have had intermittent disconnections, but it seems a coincidence that the problem always goes away immediately I relaunch Mail.
SPARKING WHEN INSERTING A USB PLUG. When the metal of the plug touches the metal case of the iMac there are small, silent, sparks, probably static. During discussion with Applecare we found that it was confined to a USB SATA drive in a USB case.
ANSWER He was foxed by this but I suggested that since the USB case is powered by the USB cable, the case is not earthed when the plug is inserted, and when it is inserted, a tiny current flows to bring the drive's case to earth level. As an electrical engineer I think this is convincing. However, the drive is connected by its Firewire 800 cable and if that earths the drive's case, this theory fails. I will mention it to my dealer.

I wonder if this is Adobe, the plugin makers, or a little bit of both. It seems like the blame would fall on both sides.
Either way, you're right. That's awesome. Hopefully that'll be a fixer soon.

Similar Messages

Call SQLGLM creates core dump segmentation fault in oracle 9i database

Hi,
I am doing call to SQLGLM to get description of error message. This always worked in oracle 9i 32 bit but it does not work with 64 bit installation. I get core dump and segmentation fault.
Please help.
Altaf

wow.. I just upgraded glibc to 2.3.2... and everything works!
:D

My iPhone 4 does not ring or vib.all setting are okay and the sound is on. What else can I do? I called the carrier. Not their fault.

HI, my iPhone 4 does not ring or vib. Check with carrier and setting .everything all right.

Did you try to reset your iPhone? Hold down Power and Home buttons together until Apple logo appears.

How to return a business fault from a DB Adapter call.

Using a SOA composite with a Mediator, from a BPEL service we call a PL/SQL package, via a DB Adapter, to get some information. Sometimes we will get a NO_DATA_FOUND from the select and we catch that (or as the documentation says - for example when a social security number is not found in the database).
The question is how do we raise that as a business fault that is returned to the caller. Currently we catch the fault in the PL/SQL and return the details in the return message - but the messageis not in itself a fault and so we would need to check the message using an IF to see if it was an error.
The question then also can we easily turn this message into a fault. We have tried using a Choose in a transformation without luck.
Hope I am describing the scenario but clearly it is something that must be regularly handled. Thus how should we handle when a social security number is not found in the database.

Sorry, the service was built without a BPEL. The service in question is used by othere services to access the database. There is a composite that exposes the service and includes a Mediator that has many Routing Rules that transform the various inputs using xsl, makes the appropriate jca call to a PL/SQL procedure and transforms the returned information from the database using xsl. The PL/SQL only has input and output variables and can raise an exception. We want to catch say N0 DATA FOUND and raise a business fault that subsequently gets caught. We tried adding code to the xsl to try and return a fault but it did not work. We can add a BPEL to the service to accomplish what we want but wanted to do without a BPEL.

How does the fault system work with AppleCare warranty extension?

I'm an owner of an iPhone 4S on Telus Mobility in Canada and I have two year AppleCare warranty extension that is linked to my phone. I've had my iPhone for over a year now with no issues, so this question is meant for reference if and when I do need to make a claim.
When I bought my AppleCare, the representative never explained to me how the fault system works, or if and what I pay in the event of a claim, or really anything else related to AppleCare. My friend told me if I pay a certain amount of money during a claim, I can get a new iPhone. Is this true? Are there limitations of the AppleCare?
Could somebody please explain to me in a fairly decent amount of detail how AppleCare works, how the fault system works, and anything else I would need to know about AppleCare? Thanks.

Here's the link explaining it:
http://www.apple.com/support/products/iphone.html
This would work in the U.S. - I think (but am not sure) it will work in Canada as well.

SOAP Fault Exception [Actor null]

Hi All,
Im trying to call a webservice from portal This web service is in ECC. When I try to call it, it throws the following error:
#1.5 #00E0ED0BA5EF005C000000C500001E350004532D85C22E36#1217354889571#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#TESTUSER#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C700001E350004532D85C23109#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C800001E350004532D85C231DF#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'#
Has anyone come across this? Please help by giving directions on how to fix this.
Thanks
SB

Hi Alex,
Please ignore the above bapi call, it is too complex since it is a custom BAPI that Im trying to call. For now, I am trying to call a very simple BAPI --> BAPI_CUSTOMER_GETDETAIL just to make sure that communication is happening.
Here is the WSDL:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:rfc:functions">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char10">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char130">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="130" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char16">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="16" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char2">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char20">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char220">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="220" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char30">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char31">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="31" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char32">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char35">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char4">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char50">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="cuky5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="date">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:pattern value="\d\d\d\d-\d\d-\d\d" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="lang">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric6">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:complexType name="BAPIRET2">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="ID" type="tns:char20" />
<xsd:element name="NUMBER" type="tns:numeric3" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
<xsd:element name="PARAMETER" type="tns:char32" />
<xsd:element name="ROW" type="xsd:int" />
<xsd:element name="FIELD" type="tns:char30" />
<xsd:element name="SYSTEM" type="tns:char10" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIKNA101">
- <xsd:sequence>
<xsd:element name="FORM_OF_AD" type="tns:char30" />
<xsd:element name="FIRST_NAME" type="tns:char35" />
<xsd:element name="NAME" type="tns:char35" />
<xsd:element name="NAME_3" type="tns:char35" />
<xsd:element name="NAME_4" type="tns:char35" />
<xsd:element name="DATE_BIRTH" type="tns:date" />
<xsd:element name="STREET" type="tns:char35" />
<xsd:element name="POSTL_CODE" type="tns:char10" />
<xsd:element name="CITY" type="tns:char35" />
<xsd:element name="REGION" type="tns:char3" />
<xsd:element name="COUNTRY" type="tns:char3" />
<xsd:element name="COUNTRNISO" type="tns:char3" />
<xsd:element name="COUNTRAISO" type="tns:char3" />
<xsd:element name="INTERNET" type="tns:char130" />
<xsd:element name="FAX_NUMBER" type="tns:char31" />
<xsd:element name="TELEPHONE" type="tns:char16" />
<xsd:element name="TELEPHONE2" type="tns:char16" />
<xsd:element name="LANGU" type="tns:lang" />
<xsd:element name="LANGU_ISO" type="tns:char2" />
<xsd:element name="CURRENCY" type="tns:cuky5" />
<xsd:element name="CURRENCY_ISO" type="tns:char3" />
<xsd:element name="COUNTRYISO" type="tns:char2" />
<xsd:element name="ONLY_CHANGE_COMADDRESS" type="tns:char1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIRETURN">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="CODE" type="tns:char5" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
</xsd:sequence>
</xsd:complexType>
- <xsd:element name="BAPI_TRANSACTION_COMMIT">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="WAIT" type="tns:char1" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_TRANSACTION_COMMITResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="RETURN" type="tns:BAPIRET2" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAIL">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="CUSTOMERNO" type="tns:char10" />
<xsd:element name="PI_DISTR_CHAN" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_DIVISION" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_PASS_BUFFER" type="tns:char1" minOccurs="0" />
<xsd:element name="PI_SALESORG" type="tns:char4" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAILResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="PE_ADDRESS" type="tns:BAPIKNA101" />
<xsd:element name="RETURN" type="tns:BAPIRETURN" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="BAPI_TRANSACTION_COMMIT">
<wsdl:part name="parameters" element="tns:BAPI_TRANSACTION_COMMIT" />
</wsdl:message>
- <wsdl:message name="BAPI_TRANSACTION_COMMITResponse">
<wsdl:part name="parameter" element="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:part name="parameters" element="tns:BAPI_CUSTOMER_GETDETAIL" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAILResponse">
<wsdl:part name="parameter" element="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:message>
- <wsdl:portType name="YCUST">
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<wsdl:input message="tns:BAPI_TRANSACTION_COMMIT" />
<wsdl:output message="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:input message="tns:BAPI_CUSTOMER_GETDETAIL" />
<wsdl:output message="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="YCUST" type="tns:YCUST">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="YCUST" binding="tns:YCUST">
<soap:address location="http://myportal:8040/sap/bc/srt/rfc/sap/ycust/040/ycust/ycust" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
As you will see below in my portal component, Im populating the four fields that it requires:
public class WS_ECC_Service extends PageProcessorComponent {
public DynPage getPage(){
    return new WS_ECC_ServiceDynPage();
public static class WS_ECC_ServiceDynPage extends JSPDynPage{
     protected IPortalComponentRequest request;
           protected IPortalComponentResponse response;
           protected IPortalComponentSession session;
           protected IPortalComponentContext context;
           protected IPortalComponentProfile profile;
           protected String userId;
     //      protected IUser epUser;
           protected String sapSystem;
           protected String fileName;
           private DAO DAO = null;
     //      private FileUploadUtility FIU = null;
     //      private ReadExcelData RED = null;
           private final static int SUCCESS_STATE = 0;
           private final static int INITIAL_STATE = 1;
           private final static int ERROR_STATE = 2;
           private int state = INITIAL_STATE;
    public void doInitialization(){
      this.communicate();
      // fill your bean with data here...
     public void communicate()throws IllegalArgumentException{
                              try{
                                      IPortalRuntimeResources runtimeResources = PortalRuntime.getRuntimeResources();
                                   IYBAPI_Service myService = (IYBAPI_Service)runtimeResources.getService(IYBAPI_Service.KEY);
                                                     System.err.println("b4 passing object to service Anurag-"+IYBAPI_Service.KEY);
                                   com.ybapi.BAPI_CUSTOMER_GETDETAIL param = new com.ybapi.BAPI_CUSTOMER_GETDETAIL();
                                   com.ybapi.BAPI_CUSTOMER_GETDETAILResponse result1 = new com.ybapi.BAPI_CUSTOMER_GETDETAILResponse();
                                   com.ybapi.Char10 custno = new com.ybapi.Char10();
                                   custno.setValue("0000009702");
                                   param.setCUSTOMERNO(custno);
                                   com.ybapi.Char2 distr = new com.ybapi.Char2();
                                   distr.setValue("12");
                                   param.setPI_DISTR_CHAN(distr);
                                   param.setPI_DIVISION(distr);
                                   com.ybapi.Char1 buff = new com.ybapi.Char1();
                                   buff.setValue("w");
                                   param.setPI_PASS_BUFFER(buff);
                                   com.ybapi.Char4 sorg = new com.ybapi.Char4();
                                   sorg.setValue("0001");
                                   param.setPI_SALESORG(sorg);
                                   result1 = myService.BAPI_CUSTOMER_GETDETAIL(param);
                                System.err.println("message message dear message : - " + result1.getPE_ADDRESS().getNAME());
                              }catch (IllegalArgumentException ex){
                              System.err.println("Getting details2 " + ex.getMessage());
                              }catch (Exception e) {
                              e.printStackTrace();
                              System.err.println("We are in Exception and got the message778: " + e.getMessage());
                              }//end try catch
    public void doProcessAfterInput() throws PageException {
    public void doProcessBeforeOutput() throws PageException {
      this.setJspName("uploadutility.jsp");
and this is what it is throwing the error, exactly the same that I got in my above post which I asked you to ignore.
#1.5 #00E0ED0BA5EF006E0000015A00001E350004533EB66A08B6#1217428720322#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015C00001E350004533EB66A09BD#1217428720322#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###$$$$$$$$$$$$$exex-SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#
#1.5 #00E0ED0BA5EF006E0000015D00001E350004533EB66A0B44#1217428720323#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015E00001E350004533EB66A0B93#1217428720323#System.err#sap.com/irj#System.err#TESTUSER#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#

IOS8 downgrade caused Siri to now keep asking "just to confirm, you want to call" on every call request. Anyone else having this annoying issue?

Ever since I made the mistake of moving to iOS 8 on my iPhone 5s, whenever I use Siri to place a phone call, I get "Just to confirm, you want to call <enter name>?" It's driving me crazy! I've resorted to disabling Siri and just using the native Voice Control, which works flawlessly for making phone calls, but not so well for other functions. I tried wiping my phone and restoring from a backup, but no luck with that. Apple doesn't seem to want to help since it's not a widely reported issue. I've also noticed that incoming calls don't connect on my car's bluetooth, when that was never a problem. Also, outgoing calls no longer make any sounds. i never know if the call dropped, the phone bricked, or the call was answered unless the other person says something. If only I could go back to iOS 7!!!

I, too, had been suffering through Siri's relentless need to confirm calls that recently she (heh!) just called.
Applecare support told me to backup and restore from that backup. I balked at the need to spend so much time reloading my music and docs, and also asked what good would it do to replace the phone's data with a copy of what was there after the problems began.
"Good question." was the reply. No answer, though.
I told her I had to go, hung up, turned Siri off and back on, and the problem disappeared. It's been nearly 72 hours and all's well.
Of course, YMMV, but it's painless and worth a shot.
I hope it works for you, too. And I hope Apple will better train their advisors to give more informed advice.
Regards,
Maurice

SOAP Call to SAP RFC

Hi,
I have a scenario in which I am calling a RFC from SOAP client. RFC has been exposed as a web service. The RFC takes a table parameter. The Table param is Not Optional.
Everything works fine except when I try to send an invalid value in the Export Param to the RFC. The SOAP Call Fails and I get a fault Message.
If there is an invalid value in the Export Param the Table Parameter is Null. So is that the reason why the SOAP call fails??
Any help regarding this would be appreciate. Tried searching OSS but could not find anything on this.
Here is the Fault Message:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>failed to call the adapter engine</faultstring>
      <detail>
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>DeliveryException</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java(Compiled Code))
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java(Compiled Code))
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:513)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     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))
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:
     at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)
     at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)
     at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)
     ... 21 more
Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java(Compiled Code))
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java(Compiled Code))
     at com.sap.engine.frame.core.thread.Task.run(Task.java(Compiled Code))
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java(Compiled Code))
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thanks
Ashish

Hi Ashish,
Were you able to resolve this problem? I am facing a similar situation.
After doing all the steps necessary when I try to send a request to the soap_sender channel I get a message unable to post:error 500
ANy help would be appreciated.
Thanks

No Fault When Dynamic Partner Link Is Down?

Hello,
I have an async process that establishes a dynamic partner link based on runtime data. I understand how to fire off to a dynamic partner link, however, I ran into a problem while testing a scenario where the partner link's endpoint is down.
In situations where the dynamic endpoint is up, my process calls it without any problems. However, when testing what happens if the dynamic endpoint is not available, I expected the process to throw a fault that I can catch. What I find is that an exception is raised in the logs (see below), but the calling process does not throw a fault. The process also continues on as if the call were successful?
Is there something that I can do to ensure that faults are raised in cases where dynamic partner links are down?
<2008-06-07 21:42:13,413> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: when invoking locally the endpoint 'http://alcalba2-lap:8889/orabpel/default/CDS_DNS_process/1.0', ; nested exception is:
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-02178
Process not found.
The BPEL process "CDS_DNS_process", revision "1.0" has not been loaded. Either the process was not initialized properly or the process has been disabled.
Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.
v10.1.3.3.0
Thanks!

There is a catch all block. I have no fault policies or fault binding set outside of what is defaulted.
Shouldn't my catch all block be enough to pick this up? It's as if nothing is bubbling up to the process and I clearly see an exception in the logs.

BT trying to charge me for call I have not made.

Hi
Can anyone help me - I have just spent ages on the phone to your billing people none of who seem to have any common sense (also I have been cut off in "transfers" from one helpdesk to another). Apparently I have made a phone call for 18.28 hrs none stop and I am been charged £88 for it. Although no one in the house has made this call so it is obviously a fault!! I am actually on anytime free calls!
Thanks

I didn't mean for that reason, just making sure it's not a dodgy company that's charged you And if its a family number how are you sure the calls not been made?
Sadly phone records are accurate, extremely accurate. It's likely the phone hasn't been put down properly. Maybe it went through to answer phone and wasn't disconnected

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server.generalException</faultcode>
         <faultstring>Login failed</faultstring>
         <detail>
            <LoginFault xmlns="NAMESPACE">
               <exceptionCode>710</exceptionCode>
               <exceptionMessage>Login failed</exceptionMessage>
            </LoginFault>
            <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message Error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

Yesterday I moved a folder from my portable drive to the desktop of a computer called B3. The folder

Yesterday I moved a folder from my portable drive to the desktop of a computer called B3. The folder contained four tiff files and 16 PSD image files that I had been Photoshoping for two weeks. I dragged the folder into bridge for a quick look. Most of the fliles had been processed in Lightroom 4. When I opened the first image in PS all of the layers were gone and the image looked like it had never had anything done to it. All of the PSD images opened with the same result, no layers, weeks of work gone. I took the portable drive and plugged it into my labtop. All of the layers were there. What happened? there was no older version of the file on the drive.

Actually that would not have had any impact. When I processed the files in Lightroom there was a software glitch and they would not open as PSD 's inPs they appeared as raw files in PS. Yes I know how to set preferences. Ok to get around that one I exported my files as PSD into a folder. After I always opened them from the folder so I don't see how the XMP files could be an issue. Also remember for two weeks I had been working using the same procedure with out any trouble@bdentonphoto: RT @Patrick_Baz: @patrickwitty: Brutal, important frontpage of the @guardiannews, heartbreaking photo from the massacre in Houla, #Syria http://t.co/7411qhUf
Sent from my iPhone
Andrea Star Reese
Photojournalist based in New York
currently in New York

Handling service-callouts in bpm which doesnt use faults to signal errors

I need to call a bunch of services from my bpm process. Normally i have boundary events on my service call activities, but now i have a whole bunch of services that i need to call that doesnt doesnt respond with faults for error situations. Instead, i should expect to get a predefined element in the normal response.
I was hoping that it was possible to define this in the event boundary thing, but it looks like i am only able to trap faults.
I was thinking that i might encapsulate each service call with a mediator, but i havent been able to define a mediator to go through the normal response and throw a fault to initial caller.
I am not able to do this translation in the OSB since sending faults for minor errors is having an impact on infrastructure components in the overall architecture (non-200 responses are treated as severe errors).
BR
Peter

Thanks - my scenario I guess is #2 of that blog. But is your take that even if I don't care what is in the fault message, i.e. I don't care about the contents of it but rather I just want to continue on from it, that I still need to perform this java coding? It's not clear to me from what he says - it seems to me he does the java coding to actually capture the contents of the message. I am in fact using the soap axis adapter too, as he is. The screen shot showing the exception branch is basically what I have.
Regards,
Keith

After updating to iOS 7 the contact photos no longer appear when I receive a call. How can I get them to show again?

After updating to iOS 7 the contact photos no longer appear when I receive a call. How can I get them to show again?

I'm having the identical problem on my iPhone 4 after upgrading to IOS 7--no ability to update apps or download new apps. Here is what Apple tech support emailed to me:
I understand that you are unable to download or update applications after updating iOS7 on your iTunes. I know you must be eager to get this resolved and I will be happy to help you today.
... to help you better with this issue I would request you to please try this steps given below to resolve your issue.
Please follow this steps:
1) Double tap the home button
2) Hold down on an icon
3) Tap the red "X" on iTunes, and the App Store.
4) Tap Settings > Store > Tap your Apple ID, and choose sign out
5) Tap Settings
6) Tap General
7) Tap Reset
8) Tap Network Settings
Once it has been closed with multi-tasking, and you have rebooted the device in the network settings reset, please sign in, and try again.
Howevr, if you are facing the same issue than for this issue, you may need to call our AppleCare technical support team. A technical Advisor will be able to tell you about Apple's complimentary and fee-based support. The technical Advisor can also assist you in determining what option might be most helpful to you in this case.
Mildly amusing that the instructions for force-closing a program are the IOS 6 instructions, which do not work on IOS 7.
Otherwise I'm having a little success with this. Some apps (not all) are updating. It seems that a few more apps update each time I go through the process (close everything, sign out, and either reset or reboot, then go to the app store, sign in and try to update all). So far it has been a very lengthy, iterative process.

Abstract asynchronous message interface for fault (exception) messages

Hi,
Has anyone yet discovered how to create an abstract asynchronous message interface for a fault message so that said message can be referenced in an Integration Process? I am currently at a loss as to how to reference the exception message returned by a synchronous RFC call, and how to return the fault message of a synchronous MI from a BPM.
Thanks for any help you can provide on this issue - please do not refer me to existing blogs or forum messages if they do not specifically answer this question in a positive manner. I have just been through the SAP Notes and the SDN forum and Google and while I have seen many questions about this topic I have not seen any answers.
Stephen

hi stephen,
never worked on this but out ofcuriosity after seeing ur question i tried to create one:
but i found these:
fault message types will only be used in case of synchronous messages.....if it is asynchronous the fault message type radio button it self will not seen while creating message interface..just check.
you need to create a Fault message type to use it in an interface...u can add your own fields also if u want.
in your present case you mentioned you are using synchronous RFC...try creating a synchronous abstract interface there you can give fault message type also...just check by creating one...
correct me if i am wrong...
regards.

My call to AppleCare re. my four faults

Similar Messages

Maybe you are looking for