SOAP Error when testing messages.

Hi Experts,
We are using webservices sync both sides. When we tested, I got this error:
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ModuleUnknownException</code>
 <text>com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/NW04S_06_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#3 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:380)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
 </s:SystemError>
Any input?
regards,
Narayanan

Hi experts,
our scenario, Webservice <-> XI <-> webservices (both in sync mode). We checked following message: another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro and hope we have all of it.
We face the same error. When checked test configuration, it worked fine but runtime, its giving the error.
Let me know if you need more details to suggest.
Regards.

Similar Messages

Error when testing from Message mapping test tab

Hi Experts,
I am wondering that when i test the message in the MM test tab its giving error and target message is not generating. I am not testing end to end then why it is triggering communication channel?
I can see that the 'RFC_Alert_Service_RFC_Receive' communication channel is in Red color RWB--> communication channel monitoring. I even even refreshed the cache and also activated the RFC channel but no use.
Below are the error details:
Error when testing message from test tab of mapping -->
java.lang.RuntimeException: Exception during processing the payload.Problem when calling an adapter by using communication channel RFC_Alert_Service_RFC_Receiver (Party: , Service: RFC_Alert_Service, XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing
Error in Communication channel monitoring -->
Receiver channel 'RFC_Alert_Service_RFC_Receiver' for party '', service 'RFC_Alert_Service'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts.
Please help me how can i resolve this issue to successfully test the message in mapping-test tab.
Regards,
Suresh.

> Error in Communication channel monitoring -->
> Receiver channel 'RFC_Alert_Service_RFC_Receiver' for party '', service 'RFC_Alert_Service'
> Error can not instantiate RfcPool caused by:
> com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts.
Unlock the user you are using in the RFC channel and provide the correct password in the channel configuration. Once the channel error is resolved you would be able to test the Mapping sucessfully...
>>why it is triggering communication channel?
You would be using RFC lookup in the mapping....
~SaNv...
Edited by: Santhosh Kumar V on Jul 8, 2009 5:48 PM

Test message from RWB: Error when sending message: 401 Unauthorized

Hi Experts,
While I am sending test message from RWB, I am getting following error:
Error when sending message: 401 Unauthorized
I am using correct userid/password as I am working with Repository/directory. Also in one of the test scenario files are picking up from folder but never got processed because of similar issue (HTTP_RESPONSE_CODE_NOT_OK) and SERVICE NOT AVAILABLE.
I am having SAP_ALL authorizations and few days back everything was fine.
I think something wrong with configuration in XI but I am unable to pin point.
Please help.
Regards,
Gourav

Yes,
but
Role of Business System : Integration system
Corresponding Integ. Server : http://<XI server>:<http port>/sap/xi/engine?type=entry
How can I change it to Application system
and RUNTIME->IS_URL = http://<XI server>:<http port>/sap/xi/engine?type=entry
Regards,
Gourav

Error when sending message: 500 Internal Server Error

Hi
IE is not accepting any messages,
when I try to send the messgae to the IE ( using RWB) i am getting the below error " Error when sending message: 500 Internal Server Error".
following things what i have noticed.
1. Pipleline URL is fine, both in the BS of XI and in the RFC destnation which i am maintaing on the IE admin) URL is "http://<host>:8000/sap/xi/engine?type=entry"
2. SICF all the XI serivess are up and running, i am able to test these service.
3. The http port is active ( SMICM )
Pls note the error is 500 Internal Server Error
regards
Nisar

I think in a simple term 500 can be said as "the request cannot be processed curretnly", these options mentieoned by you are not applicable in my case.
This generally occurs due to load problem or if you are on an SP less than 12 or even if there is an administration problem---I am on PI7.0 , what are the administration problem you are talking about?
1 Check Table Space is enough. ---i had installed server recently & very few interface running.
2 Server licence Date or Time. In this case change system date and restart server.---i have recently installed server.
3 Check the service pack levels on your XI. If it is obsolete upgrade it with latest versio----Can u explain more on this?
Try restart the java stack(XI Server) and follwing services.
com.sapii.af.app ---I am not passing trough Adater framework, so i dont think this service will matters....
com.sapii.cpa.af.app.---CPA cahe is done sucessfully, as i said i am not passsing through adapter framework.
basically for a simple HTTP post what might cause 500 error if all necessary services are up and running?
regards
Nisar

Error when sending message: 404 not found

Hi,
New to XI, practicing file to jdbc scenario. File is pickedup from the source folder but nothing appearing on the receiver end ms access database.
In the Component Monitoring, tried sending message manually with all the right info in Integration engine, getting an error message saying:
"Error when sending message : 404 not found"
Also tried in Adapter Engine and the result same.
Before doing this scenario, I tried file - file scenario then also the sender file pickedup from source folder but nothing happend at the receiver end.
Any idea's?? what might be the issue????
Thanks,
Venu.

Hi Venu,
"404 is a not found error", plz make a check of your URL you're using is correct? do you use the right port? Normally the port is 80<SystemNo>, so rather 8001 than 7001.
Also check in transaction SICF, if the node /sap/xi/adapter_plain has been activated, if not, activate it and try again.
If you are testing sending the message to the Adapter Engine, then the Send Message URL should be like this:
http://<server>:<J2EEport>/MessagingSystem/receive/AFW/XI
For your error, refer to the following threads:
Unable to find an associated SLD element
Unable to refresh cache contents in XI.
Unable to find an associated SLD element
Also check that the Adapter Engine is successfully registered in the SLD. To do this, call the Content Maintenance function in the SLD as follows:
http://<sld-host>:<sld-j2ee-port>/sld u2192 Administration u2192 Content Maintenance.
Select XI Adapter Framework.
Thirteen associations have to be registered.
(Source: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752a857)
If you can't find all the associations, then you will have to create the associations manually.
This is a very good blog which answers ur question:
check this weblog
https://weblogs.sdn.sap.com/pub/wlg/4061?page=last&x-showcontent=off [original link is broken] [original link is broken] [original link is broken]
Regards,
Vinod.

RWB:Error when sending message: 404 Not Found

Dear all,
"i am getting error: Error when sending message: 404 Not Found"
while testing from rwb > Component Monitoring > Non-Central Adapter Engines > Adapter Engine AIPID > test message >
with send message to = http://pid:50000/sap/xi/engine?type=entry - pi server url
sld buss system > pipeline url http://pid:50000/sap/xi/engine?type=entry (same)
and my id comm channel > target host > bid.xxx.com with service no
(adapter type: xi
adapter engine: Integration server
address type: url address
target host: bid
service no: 8000
path: /sap/xi/engine?type=entry
i am working in nw2004s system)
while testing cache connectivity test from rwb > Component Monitoring
i got error:http://docs.google.com/Doc?id=dcdrq9jt_0g6j35p
green: Integration Repository
green: Integration Directory
green: Integration Server - JAVA
red:Adapter Engine af.axd.aipid
yello:Integration Server - ABAP
Adapter Engine af.axd.aipid > Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.00.aipid, string], target element type: SAP_BusinessSystem)
[Data Evaluation]: GlobalError
though if i try to send message from rwb...> with send message to field with : directly to bi rather than pipeline url through bi than message send successfully but not getting into component monitoring.
what should i do?
best regards,
dushyant.
refer this forum: is rwb's send message to field = sld>buss system>Pipeline URL?
and
SXI_CACHE
@8O@ Error during last attempt to refresh cache
LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM
Smq2 = 0
Sm58 = 0

Hi,
If you are testing sending the message to the Adapter Engine, then the Send Message URL should be like this:
http://<server>:<J2EEport>/MessagingSystem/receive/AFW/XI
For your error, refer to the following threads:
Unable to find an associated SLD element
Unable to refresh cache contents in XI.
Unable to find an associated SLD element
Cheers
Manish

Error when sending message: Method not implemented

Hi, All:
We have newly setup system and when we test sending test message from RWB, (RWB-Component Monitoring-Integration Engine-Test Tab), we got following error:
"Error when sending message: Method not implemented", I know this is related to post configuration issue, I just know someone has come cross the situation and how it was resolved.
Thanks
Liang

HI Liang
Yes it looks like post installation problem. I have not come across this but i think you should check with the RFC created for IE while installation. To connect IE & AE and even the exchange profile if something is missing
Thanks
Gaurav

Error when sending message: 403 Forbidden....sender si file

hi...
here iam working with File to IDoc scenario
file is picking from a particular source but its is not showing any messages in SXMB_MONI and in IDX5 (outbound) or in RWB.
when i check test my message in RWB its is showing Error when sending message: 403 Forbidden.
can anyone explain me this problem plz...
all my DESIGN and CONFIGURATION is fine....
its urgent...
THX..
john wesly

Hi John
403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
for more details on error code follow the link
http://www.web-cache.com/Writings/http-status-codes.html
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm
first try to solve problem by making CACHE refresh
either by directory
Check whether you have given the right credentials. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
steps to restart J2EE engine
1) run transaction SMICM
2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
Thanks
sandeep sharma
PS ; if helpful kindly reward points

"Not an executable or is a link" errors when starting Messaging Server

"Not an executable or is a link" errors when starting Messaging Server

If Calendar Server 3.x has been installed to the same server root
as Messaging server, it is possible that the command 'NscpMail start'
to restart the server will return a string of errors:
# /etc/NscpMail start
19971207145610:Dispatch:Notification:Local Module
(Account-Handler) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Account-Manager) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(AutoReply-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Configuration-Manager) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Error-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Mailbox-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Program-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Router) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(UNIX-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(Finger-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(IMAP4-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(POP3-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(SMTP-Accept) is not an executable or is a link.
Module not loaded.
Startup Problem:
Module Error-Handler is required for proper operation.
Netscape Messaging Server Exiting!
The Calendar server 3.x installation may have changed the permissions
on [server-root]/bin directory from 755 to 750. Simply issue the
command (as root) 'chmod 755 [server-root]/bin' and then start
the server with the 'NscpMail start' command, and it should start
without a problem.

"Not an executable or is a link" errors when starting Messaging Server

If Calendar Server 3.x has been installed to the same server root
as Messaging server, it is possible that the command 'NscpMail start'
to restart the server will return a string of errors:
# /etc/NscpMail start
19971207145610:Dispatch:Notification:Local Module
(Account-Handler) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Account-Manager) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(AutoReply-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Configuration-Manager) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Error-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Mailbox-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Program-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Router) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(UNIX-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(Finger-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(IMAP4-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(POP3-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(SMTP-Accept) is not an executable or is a link.
Module not loaded.
Startup Problem:
Module Error-Handler is required for proper operation.
Netscape Messaging Server Exiting!
The Calendar server 3.x installation may have changed the permissions
on [server-root]/bin directory from 755 to 750. Simply issue the
command (as root) 'chmod 755 [server-root]/bin' and then start
the server with the 'NscpMail start' command, and it should start
without a problem.

Error when sending message: 500 Timeout

while sendin a message in the http to rfc scenario, im gettin this error message "Error when sending message: 500 Timeout".
can any1 throw some light on this.

Hi venu,
you need to go to RZ10 and there select the profile instance and go with the extended maintance option in the change mode.
there are two ways you can change it:
1. check out note: 824554
TCODE - rz10
icm/server_port_0 = PROT=HTTP,PORT=8010,TIMEOUT=800,PROCTIMEOUT=800
(for 800 seconds)
8010 is my HTTP port so you have to change it:)
2. SXMB_ADM -> configure integration server -> change specific identifiers
runtime parameter:
Parameter HTTP_TIMEOUT
Meaning
Specifies the timeout for http connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
Personally I only changed the one from the instance profile but the second one should work too
My suggestion is change only PROCTIMEOUT to 600 or 900 but dont change TIMEOUT. Imp thing is u need to restart the XI, then onlychanges will take place.
If these dosent work out go for changing TIMEOUT also. Just set the value for the instance and dont maintain the HTTP_Timeout in the sxmb_adm
Let me know what u have done , if it works
Thanks,
srini

Spectrum digital DSK5416 driver setup gives an error when test wizard is run.

Please help us with the following problem we are facing:
1.   Spectrum digital DSK5416 driver setup gives an
error when test wizard is run. A snap shot of the same has been
attached.
2.   The A/D module doesn’t pickup microphone signal or
an audio sample for loopback but the implementation of the same works
fine in CCS environment. (We are using Mic In and Speaker Out lines)
3.   When a real-time application has run successfully
and if you close the VAB environment the application starts running
automatically until you reset the board.
4.   We don’t find the flash program button enabled, so
that any real-time program can be burned into flash and demonstrate the
embedded feature.
Note:
We are using Windows Xp professional edition.
Program is developed using DSK5416

Hello, I have included some information that will help address your questions: (1) I couldn't see the attached image file (contained errors). The RIDE/VAB DSK5416 Driver makes use of a JTAG communication when reading/writing memory on the DSK5416 hardware. You will need to make sure that the JTAG transfer option has been selected in the Driver Setup dialog box. The memory test process may seem to take a long time due to the amount of memory being accessed. (2) The VAB RTDSKAD block component provides a one-channel A/D input that makes use of the line-in channel on the DSK5416 hardware. (3) VAB does not remove the downloaded DSP executable program from DSK5416 memory, and it does remain resident. That being said, I wouldn't expect that the program would begin execution when VAB is closed. I would recommend that you verify that the DSP program stopped properly upon selecting the VAB Stop command. Then, close VAB as normal. (4) The RIDE/VAB driver for the DSK5416 does not support programming of flash memory on the DSK5416 hardware. Regards, Steve

Error when sending message(e-mail) from Process Chain ?

Hello SDN s,
How ya all ?
I scheduled a Process Chain with Message option to send it to (U - INternet Address) email ID but it says some error in sending message. What could be the reason ?
The following is the Job Log Entries....
30.06.2006 18:05:53 Job started 00 516 S
30.06.2006 18:05:53 Step 001 started (program RSPROCESS, variant &0000000000261, user ID ALEREMOTE) 00 550 S
30.06.2006 18:05:54 Hierarchy/attribute change successfully carried out RSM 794 I
30.06.2006 18:06:00 Document <PV FOR GETTING MESSAGE THROUGH E-MAIL - SUCCE> could not be sent SO 654 S
30.06.2006 18:06:00 Error when sending message RSRA2 11 S
30.06.2006 18:06:01 Job finished 00 517 S
Thanks !!!
Best Regards....
Sankar Kumar
+91 98403 47141

Hey yes, in that T.Code all the values are 0. What to do to activate that ????????????
 Duration Duration
 Completed Error In transit Waiting In transit Waiting
 hh:mm hh:mm
B08(100) 0 0 0 0
FAX Telefax 0 0 0 0 0:00 0:00
 5 INT Internet 0 0 0 0 0:00 0:00
SMTP 0 0 0 0:00 0:00
X40 X.400 0 0 0 0 0:00 0:00
 RML R/Mail or 0 0 0 0 0:00 0:00
 PAG 0 0 0 0 0:00 0:00
 PRT 0 0 0 0 0:00 0:00
So, how to solve this issue ? how to send e-mails ? what configuration or settings to be done ?
could u give the steps to do that ? as i am the only one BW guy here !?
Thanks !!!
Best Regards....
Sankar

SPROXY: XSLT Type Error when testing

We are using SAP PI 7.1 to consume ABAP Proxies. We have performed all the necessary configurations and are able to see the ESR from within SAP R/3. When testing an ABAP Proxy via SPROXYI receive the error shown below. In fact I receive this error for all proxies that I try to test, including standard SAP functions. I am assuming this is a configuration issue rather than a specific issue with a proxy. I have checked SDN and SAP Service and I can't find any mention of this specific error. Is there anyone out there who can help?
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_CALL_ST_ERROR</SAP:P2>
<SAP:P3 />
<SAP:P4>Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_CALL_ST_ERROR; ( Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION)) A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

Hi Robert,
i know that this is quite late. The problem is with the XSLT which gets generated when you generate PROXY. And some times the kernel doesn't doesn't set the conversion of XSLT correctly. you can check the syntax of the XSLT /1SAI/TXS1EF71A636AE519CFE80A in the transaction STRANS.
There should be some basis notes from the component BC-DWB-PRX to solve the problem.

Error when test a Web service

Hi all,
I am trying to create a web service for RFC Function module. I ceated the web service, now I want to test this Web service. I have the URL of WSDL file, but when I execute the URL, it doesn't display.
Can you please suggest me what will be the reason for this error?
Thanks
Sanket sethi

Please find below the steps to create and test web services.
Please follow up these steps and you would not get any error in testing web services.
Hope this would help you.
1. Go to SICF and activate this webservice: u201C/sap/bc/srt/rfc/sap/QUERY_VIEW_DATAu201D
2. Go to transaction WSCONFIG andenter service destination u201CQUERY_VIEW_DATAu201D and enter variant u201Cquery_view_datau201D and hit
enter. Currently, there are no released services so create a new service.
3. Choose Save to release this web service.
4. Choose ICF Details -> External Aliases
5. Choose u201CNewu201D to create a new external alias.
6. Enter external alias u201C/sap/bw/xml/soap/queryviewu201D and enter description u201CSAP BI Web Service u2013 XML Result Setu201D
7. Specify your security and user ID on the u201CLogon datau201D tab.
8. Specify u201C/sap/bc/srt/rfc/sap/QUERY_VIEW_DATAu201D under the u201CTrg Elementu201D tab.
9. Save your external alias.
10. Go to transaction WSADMIN -> Goto -> Administration Settings. Ensure that the path to your J2EE is specified here and save this.
11. Find your web service and choose the u201CWeb service homepageu201D
12. Login to your ABAP system from the Web Service Navigator
13. Choose Test -> GetQueryViewData to test this service.
14. Enter and Infoprovider and Query and send the request to test this web service. Note: If the query has mandatory variables, those must be passed in the parameter. For the sake of this test, use a query without variables.
15. Ensure the request and response are successful.
16. If you have issues, make sure you activate your Web Service and Interface in SE80.
17. Here is an example of how to pass parameters for filter values using WEB API commands. We are passingtheFILTER_IOBJNM=0D_CHANNEL and FILTER_VALUE=3.
18. Here is an example of how to pass parameters for variable values using WEB API commands. In this case, we are using a selection option variable. We are passing the following parameters:
VAR_NAME_1=DISTGOP
VAR_OPERATOR_1=EQ
VAR_VALUE_LOW_EXT_1=3
VAR_VALUE_HIGH_EXT_1=5

Error when testing ADS service method rpdata from Portal

Dear All,
We have configured ADS in our portal system and at the same time in the respective ERP system also.
previously, like just before 2 days it worked fine. But now it is throwing an excpetion when testing the ADS service using the test option of ADS service.
We are usign ADSUSER to test the rpdata method.
Our landscape is NW2004s (EPDIAS Java), BAckend is ECC5.0.
Error we are getting on portal side is:
User ADSUSER does not have access to method rpData.
Error we are getting on ERP side when try to see printpreview of test form:
Adobe document services error: SOAP Runtime Exception: CSoapExceptionFault : SOAP (100102)
We have tested the FC destination on ERP system, and the destinations maintained on Viosual Administrator also.
Please do the needful,
Your help will be appreciated.
Thanks in advance,
Regards,
Sireesha.

Hi Preetha,
Thanks for reply.
as per note 944221we have checked our configuration its look like every thing ok
but error was same
so we I have activated trace, here is the corresponding details
1.5#00300580ABE600520000B4BC00001038000430184A8E73A6#1178780795046#com.sap.engine.services.ejb#com.adobe/AdobeDocumentServices#com.sap.engine.services.ejb#ADSUSER#7474####fd104a70fec411dbcdd100300580abe6#SAPEngine_Application_Thread[impl:3]_49##0#0#Error##Java###
[EXCEPTION]
#1#com.sap.engine.services.ejb.exceptions.BaseEJBException: User ADSUSER does not have access to method rpData.
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:74)
 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:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
 at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:608)
 at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:505)
 at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:72)
 ... 25 more
com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
 at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:608)
 at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:505)
 at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:72)
 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:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please do the needful.
Regards,
Sireesha

SOAP Error when testing messages.

Similar Messages

Maybe you are looking for