Error in Webservice Call HTTP error (return code 404, message conn failed)

Hi
We wish to call  a standard EP7 webservice through ABAP.
When we try to create consumer proxy , we get the following error.
HTTP error (return code 404, message "conn failed")
Message no. SPRX090
==> Display Error Document
If you want to generate a proxy for an external WSDL document by specifying a URL, check that the proxy settings of the system are correct (transaction SICF - Client - Proxy Settings). If you want to generate a proxy for an XI Repository object, check the connection to the Enterprise Services Builder as follows:
Check List for Setting Up a Connection to the Service Repository
1. The address of the Enterprise Services Repository must be known in the SAP system
Check with report SPROX_CHECK_IFR_ADDRESS
The address is taken from the following parameters in the exchange profile ('Connections' section):
com.sap.aii.connect.repository.name: Server (for example,pwdf0436)
com.sap.aii.connect.repository.httpport: Port (for example, 1080)
com.sap.aii.connect.repository.contextroot: Root (for example,rep)
The logon data is also read from the exchange profile ('ApplicationSystem' section):
com.sap.aii.applicationsystem.serviceuser.name: User
com.sap.aii.applicationsystem.serviceuser.pwd: Password
As an alternative to using the exchange profile, you can maintain the RFC destination SAP_PROXY_ESR. If this RFC destination is maintained it will be used by the proxy generation in place of data from the exchange profile to access the Service Repository. In this case, the Exchange Profile will even not be read.
The RFC destination has to be set up using transaction SM59 and should look like this:
RFC Destination: SAP_PROXY_ESR
Connection Type: G (HTTP Connection to External Serv)
Description1: ESR for Proxy Generation
Target Host: esr_host
Service No: 1080
Path Prefix: rep
Logon and Security:
Basic Authentication: active
User: esr_user
Password: esr_password
2. The HTTP Framework of the Web Application Server must function
Check with report SPROX_CHECK_HTTP_COMMUNICATION
If necessary, contact your system administrator. Please be aware of the fact, that the HTTP framework is depending on the application server. Thus the result of the report may differ for different application servers.
3. Proxy generation must interpret the data of the Enterprise Services Repository correctly
Check with report SPROX_CHECK_IFR_RESPONSE
you can also login in dev and go to Xn se91
enter msg id SPRX and msg no 090
select the message and click on long text..
you get the same message in a formatted manner..
How to get rid of this ?
Regards
Rajendra

Hi
we have given the correct path as we have tested the webserive from
other technology (.net) by providing the same path.
regards
Rajendra

Similar Messages

  • How to consume web service in WDP ABAP ---HTTP error (return code 404, mess

    Hi,
    Am trying to consume a web serivce in WDP where I got error HTTP error (return code 404, message "conn failed")in sdn i came to know that it could be resloved by giving the IP address of the host but in case it is not the web services am using are the external links.
    kindly help me to sort it.
    Regards
    Raj

    hi,
    in addition to above thread
    refer this too
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0d4aa08-beed-2a10-fab2-ad975cead04a
    bvr

  • HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")

    Hello All,
    I am trying to create a proxy class from a webservice through a URL.
    I get the error:
    HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")
    What could be the reason for this. Please help.
    Thanks,
    Smita

    Hi Smita
    Pls refer the links for this error ICM_HTTP_CONNECTION_FAILED
    The specified item was not found.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/changing%252bhttp%252bport%252bof%252bdecentralized%252badapter%252bengine
    Http* Errors in XI
    Configuring & Publishing Enterprise Services from SAP Business Suite system into NWCE (Netweaver Composition Environment) Services Registry
    Publishing ABAP WebServices to an External UDDI Server
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    Regards
    Abhishek

  • Error during webservice call

    Hi all,
    Has anyone worked on Inspire. I am working on a typical scenario integration on primavera with PS.
    But when I do start sync I get " could not start Synch. Error during webservice call"
    When I check Sender SOAP CC in SAP PI in RWB , I get no information. It's status is green and no logs. Also SXMB_moni has no logs.
    Is there a problem with my Sender SOAP CC confihuration .or application has failed
    Can anyone help me on this.
    Regards,

    Hi,
    I tried to reach the URL using SOAPUI but got the following error :
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:STREAM_TRANSFORMATION_EX:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1193)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:592)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at $Proxy1413.process(Unknown Source)
         at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:592)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at $Proxy788.process(Unknown Source)
         at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:187)
         at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:513)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
         at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    What could  be the issue. Plz help

  • Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

    Hi experts,
    I have a big issue in production server,
    the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
    if i am reprocess or press F6 it is going manually.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">&copy; 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Regards,
    Kiran polani

    Dear Sriram Ramani,
    in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
    but my problem is in Soap to RFC case..
    for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
    when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
    not for all signals for few signals for some time..
    Why it is happening i can't understand.
    in repository it is saying Repsitory object hmi failed and address already in use.
    is there any problem with loading IR objects.
    Please suggest me good suggestion for this type of issue what can do for this to resolve.
    Regards,
    Kiran Polani

  • Getting the error: Error while receiving by HTTP error code: 110

    Hi,
    I have developed an interface which actually gets data from SCM system and in BPM to gets additional data from R/3. There are five synchronous call to this R/3 to get different sets of data. I am using only one communciation channle from BPM to R/3. The interface works perfectly OK in the development system. When the interface is migrated to the test system I found that the four calls work perfectly fine while the last call error out as below and the J2ee server goes down:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Any input/help will be appreciated. I have tried increasing timeout/connection alive time but still not get resolved.
    Thanks in advance,
    Sushma

    Hi Prateek,
    Thanks. But this note I have checked before and this seems not related. I actually found out the system logs in SM21 and saw the "Operating system call recv failed (error no. 10054)". What I did then is I seach notes related to this error and found a numebr of SAP notes. And I have informed the Basis guys to look into the notes and the system logs. They are working on this and they are deleting the old messages which have errored out. They are suspecting the system memory or too many old messages would have caused this issue.
    If you have any knowledge of why this error would have occurred please let me know.
    Thanks,
    Sushma

  • Document control failed due to error in [DOCMGR-CANCEL] with a return code

    i am getting this error while calceling the purchase order "Document control failed due to error in [DOCMGR-CANCEL] with a return code of [OTHER]. "
    I am doing the calcel like this
    Nav: buyer work centre --> order
    searche the po and then
    select order --> cancel then click GO button
    i gave the Reason as Cancel
    communication method: email
    Cancel Requisition: Yes
    Please help on this, its urgent.
    Thanks,
    Vijay.

    Hi Vijay,
    Check this MOS note.
    Cancelling A Standard Purchase Order In Buyer Work Center Results In Error [Docmgr-Cancel] With A Return Code [ID 1338826.1]
    Thanks
    -Arif.

  • Error while receiving by HTTP (error code: 110)  ?

    Hi Experts,
    I am working on IDOC to file Scenario.
    I am getting this error in SXMB_MONI. What may be the reason.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Best Regards,
    Anil

    Check these threaads:
    Re: XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
    Regards,
    ravi

  • Error for COM Routine application program (return code 40028)

    Hi,
    When we loading data in Planning Book ,we are getting below error
    Error for COM Routine application program (return code 40028)

    Hi,
             Did you try checking your COM build? The COM communicates between your database and Livecache and fetches the data requested. The last time we had this, SAP recommended COM upgrade.

  • Activation problem: Adobe DRM Error System: 8 State: 4 Class: 65 Code: 59 Message: VE error 59

    Hi,
    I bought a book yesterday and I was able to open it in my vista machine. I have a second computer and I can't open my book there. I get this error:
    Adobe DRM Error
    System: 8
    State: 4
    Class: 65
    Code: 59
    Message:
    VE error 59
    --- end ---
    I already downloaded Adobe Digital Editions 1.5 beta 2, and went back to acrobat reader 6, activate from aractivate.adobe.com, but nothing seems to work. What can I do?

    System 7, code 31 is always a networking problem. Meaning something on your network is preventing the book information from getting to the rights-management server (or from the rights-management information getting sent back)
    You can check firewalls, security software, etc to see where the blockage might be, or work with your network admins if you have them. See 'Error "Adobe DRM Error" when you activate Digital Editions or access an eBook" at http://www.adobe.com/go/kb402747
    Regards,
    Bentley Wolfe
    Senior Support Engineer, Flash/Flash Player/Digital Editions
    Adobe

  • TMS Error messgae: Source file could not be opened. Message: FTP Failed

    Can you please help me with this error ?
    I am trying to adjust the import queue on prod system, but I get this error:
    TMS Error messgae: Source file could not be opened. Message: FTP Failed
    SLOG:
    STOP  TRANSMIT BUFFER ENTR SID g 0000 20110720075455              ADMIN        ulvcp743p
    STOP  TRANSMIT BUFFER ENTR SID g 0000 20110720075809              ADMIN        ulvcp743p
    START TRANSMIT BUFFER ENTR SID g      20110720075812              ADMIN        ulvcp743p
    STOP  TRANSMIT BUFFER ENTR SID g 0000 20110720080133              ADMIN        ulvcp743p
    START TRANSMIT BUFFER ENTR SID g      20110720081655              ADMIN        ulvcp743p
    WARNING: /usr/sap/trans/tmp/SID.LOB is already in use (10), I'm waiting 2 sec (20110720081843). My name: pid 28901462 on ulvcp743p (SIDadm)
    WARNING: /usr/sap/trans/tmp/SID.LOB is already in use (20), I'm waiting 1 sec (20110720081918). My name: pid 28901462 on ulvcp743p (SIDadm)
    WARNING: /usr/sap/trans/tmp/SID.LOB is already in use (30), I'm waiting 5 sec (20110720081951). My name: pid 28901462 on ulvcp743p (SIDadm)
    ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
    STOP  TRANSMIT BUFFER ENTR SID g 0000 20110720082014              ADMIN        ulvcp743p
    ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
    ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
    ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18

    Hi ckary,
    Thanks for your post. It looks as if your computer is not seeing the driver
    calls and thus it gives the error saying it cannot complete that task. Does
    this happen with any other example programs you run using DAQmx? What version
    of DAQmx do you have? I would first recommend getting the latest DAQmx driver
    version, 8.7.1. You can find this at the following link below.
    Drivers and Updates
    Please post back if installing the latest driver does not
    fix the problem.
    Corby_B

  • Making a REST webservice call. Error code: 401 Access to the requested resource is not allowed

    Hi All,
    I’m having a hard time figuring out how to make Rest WebService calls.
    I tried executing this directly through browser and I get an error.
    http:localhost:8080/rest/bean/atg/userprofiling/ProfileServices/loginUser?arg1=[email protected]&arg2=Password
    13:18:20,613 ERROR [RestSecurityServlet] Error code: 401
    Access to the requested resource is not allowed: /atg/userprofiling/ProfileServices
    atg.rest.RestException: Access to the requested resource is not allowed: /atg/userprofiling/ProfileServices
    at atg.rest.processor.RestSecurityProcessor.checkAccess(RestSecurityProcessor.java:546)
    at atg.rest.processor.RestSecurityProcessor.handleGetRequest(RestSecurityProcessor.java:313)
    at atg.rest.processor.RestSecurityProcessor.doRESTGet(RestSecurityProcessor.java:199)
    at atg.rest.servlet.RestPipelineServlet.serviceRESTRequest(RestPipelineServlet.java:417)
    at atg.rest.servlet.RestPipelineServlet.service(RestPipelineServlet.java:260)
    at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:320)
    at atg.rest.servlet.RestPipelineServlet.service(RestPipelineServlet.java:264)
    at atg.rest.servlet.HeadRestServlet.service(HeadRestServlet.java:130)
    at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:267)
    From the documentation I understand that I need to create a session, is the session only necessary to access secured components since this
    particular method “ProfileServices.loginUser “ has been declared as not secure in restSecurityConfiguration.xml
    Also, are there two different ways in which I can log in
    1.       Using RestSession.createSession providing the username and password.
    2.       Or using ProfileServices.loginUser or ProfileFormHandler
      Can someone please clarify

    If you are invoking the REST web-service from a Java client then you can create a RestSession object using the createSession method. But in your case you seem to be invoking it with a HTTP request which by default would be treated as a GET request by ATG's REST implementation. Therefore being a GET, it would try to fetch a property "loginUser" from /atg/userprofiling/ProfileServices component (based on your URL) which would always fail.
    To invoke loginUser() method of ProfileServices with your passed argument you need to tell ATG's REST system to treat your incoming request not as GET but as a POST request which you can do using  atg-rest-http-method control parameter in your request like this
    http:localhost:8080/rest/bean/atg/userprofiling/ProfileServices/loginUser?arg1=[email protected]&arg2=Password&atg-rest-http-method=POST
    It should work this way provided your restSecurityConfiguration.xml is proper.

  • Error in Webservice call

    Hi All,
    We are trying to call a webservice synchronously which is in IIS webserver.
    But we are getting the following error
    <SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code>MESSAGE.GENERAL</SAP:Code>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
    XIISUSER has no permission for accessing party service :BS_IIS
    </SAP:AdditionalText></SAP:Error>
    The webservice can be is of anonymous access.
    Can anyone help.
    Thanks in Advance
    Chemmanz

    Hi, well there is no QOS in the URL, is this the right parameter?!
              <wsdl:port name="MI_BOM_OUTB_ASYNCPort" binding="p1:MI_BOM_OUTB_ASYNCBinding">
                   <soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://ctsr110:50100/XISOAPAdapter/MessageServlet?channel=:VM_HRT_SAP:CC_HRT_SOAP_BOM&version=3.0&Sender.Service=&amp;Interface=%5E*"/>
              </wsdl:port>

  • [Error during Export] R3load exited with return code 11

    Hi guys,
    While performing and Unicode Migration, during Export Phase, Migration Monitor returned the following error while exporting a package
    ERROR: 2014-06-01 10:57:44 com.sap.inst.migmon.LoadTask run
    Unloading of 'REGUC' export package is interrupted with R3load error.
    Process '/usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error' exited with return code 11.
    For mode details see 'REGUC.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    REGUC.log details:
    (As you see, it does not provide reasons of this error, all messages are informative and alike all other Packages logs)
    /usr/sap/ECP/DVEBMGS00/exe/R3load: START OF LOG: 20140601105052
    /usr/sap/ECP/DVEBMGS00/exe/R3load: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /usr/sap/ECP/DVEBMGS00/exe/R3load: version R7.40/V1.8
    Compiled Jul 23 2013 21:30:53
    /usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC001.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE "
    (GSI) INFO: hostname = "ecp "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    Tried to find what does R3load Return Code 11 means, but I couldnt find further information on this.
    Any hint of what is causing this error?
    (Please disregard any Filesystem issues since all of them have available space)
    Best!

    After using latest R3load patch, it provides furher information on the log file.
    -------------------- Start of patch information ------------------------
    patchinfo (patches.h): (0.070) R3ldctl: fix CDS views creation in upgrade export mode (note 2
    017805)
    DBSL patchinfo (patches.h): (0.022) Smaller corrections in release 7.40 (th, dp, vmc, dpmon)
    (note 1821404)
    --------------------- End of patch information -------------------------
    process id 27326
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC003.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "ecp                                                             "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    (GSI) INFO: instno   = "6120023288"
    (RTF) ########## WARNING ###########
            Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: cannot find version token "ver:" at line 1
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: unknown file format, assuming version 2
    (EXP) INFO: table REGUC will be exported with sorting (task modifier)
    ------------------ C-STACK ----------------------
    [0] t_splay ( 0x1020df850, 0xb3, 0x4386, 0x100a02078, 0x0, 0x1020df870 ), at 0xffffffff7b9629
    94
    [1] t_delete ( 0x1020df850, 0x4348, 0x1d9870, 0x1000d0408, 0xffffffff7bb3c000, 0x0 ), at 0xff
    ffffff7b9627e4
    [2] realfree ( 0x101ee7590, 0x1f82b1, 0x1d9cd0, 0x1f82b0, 0xffffffff7bb3c000, 0x101ee7590 ),
    at 0xffffffff7b9623b0
    [3] _malloc_unlocked ( 0x7d40, 0x200000, 0x101edf840, 0x0, 0x101ee7580, 0x0 ), at 0xffffffff7
    b961eb4
    [4] malloc ( 0x7d39, 0x2388, 0x1da428, 0x10038fe84, 0xffffffff7bb3c000, 0x2000 ), at 0xffffff
    ff7b961c28
    [5] rstg_get ( 0x2, 0x0, 0x2, 0x7d10, 0x0, 0x10077d8c0 ), at 0x10038ff4c
    [6] c3_uc_new_cache ( 0x100a02078, 0x284db0, 0x284c00, 0x10077d8c0, 0x100a02108, 0xb3 ), at 0
    x1000d1ce8
    [7] c3_uc_seek_cache ( 0xb3, 0xff79, 0xffffffff7ffcae3e, 0x100a02078, 0x10189fa48, 0x10077d8c
    0 ), at 0x1000d188c
    [8] c3_uc_new_tabcache ( 0x0, 0xb3, 0x4386, 0x100a02078, 0xb3, 0x10077d8c0 ), at 0x1000d13fc
    [9] c3_uc_insert_record_in_cache ( 0xffffffff7ffcb04e, 0x10189fa48, 0x100a02078, 0x100a024c8,
    0xb3, 0x1058c8f84 ), at 0x1000d0408
    [10] c3_uc_insert ( 0x0, 0x100a02078, 0x0, 0x0, 0x10077d8c0, 0xffffffff7ffcb04e ), at 0x1000c
    f944
    [11] c3_uc_convert_table_entry ( 0x1015c61f8, 0x0, 0x100a02078, 0x0, 0x10189f408, 0x31a000 ),
    at 0x1000ce314
    [12] c3_uc_convert_logic_table ( 0x1015c61f8, 0x100a02078, 0x0, 0x4a, 0x100638dc0, 0x10077d8c
    0 ), at 0x1000cdb18
    [13] c3_uc_convert_cluster_data ( 0x100a02078, 0xffffffff7ffcbc50, 0x1015c6428, 0x1015c61f8,
    0x10077d8c0, 0x0 ), at 0x1000cd10c
    [14] c3_uc_convert_cluster_item ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x1038
    6f6e0, 0xffffffff7ffcbb8c, 0x100a02812 ), at 0x1000be1d4
    [15] process_task ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x100a02810, 0x10063
    32e0, 0x10077d8c0 ), at 0x1000b2f58
    [16] CnvCluster ( 0x1014642d0, 0x100954670, 0x100aa9610, 0x2849b8, 0x284800, 0x6cb978 ), at 0
    x1000b1f8c
    [17] cnv_clust2 ( 0x100aa9580, 0xffffffff7ffcc258, 0x100954770, 0xfc0, 0x107d00, 0x100954670
    ), at 0x100062714
    [18] cnv_cp ( 0x100aa9580, 0xffffffff7ffcc258, 0x100aa95e0, 0x0, 0x10077d8c0, 0x1d6c00 ), at
    0x100064644
    [19] process_buffer ( 0x100aa9580, 0xffffffff7ffcc258, 0xfff00, 0x100a97bd0, 0x10, 0x100aa95b
    0 ), at 0x10007162c
    [20] execute_table_unload ( 0xffffffff7ffed610, 0xffffffff7ffdc4b0, 0x0, 0x100aa9580, 0xfffff
    fff7ffcc258, 0x10077d8c0 ), at 0x10006c488
    [21] export_table_task ( 0xffffffff7ffed610, 0x0, 0xffffffff7ffdc368, 0xffffffff7ffcc330, 0xf
    fffffff7ffeedb8, 0xffffffff7ffeec60 ), at 0x10006c934
    [22] db_unload ( 0x100a97b0d, 0xffffffff7ffed610, 0x0, 0x10077d8c0, 0xffffffff7ffeec60, 0xfff
    fffff7bb47540 ), at 0x10006d148
    [23] main_r3ldmain ( 0x72ec00, 0xffffffff7ffff448, 0xffffffff7ffff228, 0xffffffff7bb47540, 0x
    1005fc290, 0x0 ), at 0x1000514e0

  • Asyncronous webservice call gives error

    At this point, since I have not gotten any replies to the post below I wonder if I need to go in a new direction. I created my async web service off of the example given by Weblogic. Does anyone know of any different examples to use?
    I have an asynchronous web service that calls a synchronous web service. Currently the synchronous one does nothing and the asynchronous simply calls the synchronous one. I receive an error when attempting to make this call. Does anyone know why I would receive this error? I have done everything I can think of.
    Failed to invoke end componentFailed to invoke methodjava.rmi.RemoteException: No onAsyncResponse method 'onAsyncTransferToResponse' found for asynchronous invoke of transferTo
    //this is my onAsyncTransferToResponse method
    @AsyncResponse(target = "port", operation = "transferTo")
    public void onAsyncTransferToResponse(AsyncPostCallContext apc, String a) {
    log.info("-------------------");
    log.info("Got quote " + a);
    log.info("-------------------");
    I have also removed this method all together and it still fails. Any help at all would be appreciated. Or let me know if you need more info to help me.
    Edited by: ntsd2 on Feb 27, 2008 8:18 AM
    Edited by: ntsd2 on Feb 28, 2008 2:00 PM

    Hi
    we have given the correct path as we have tested the webserive from
    other technology (.net) by providing the same path.
    regards
    Rajendra

Maybe you are looking for