on 06-13-2015 6:32 PM
HI All,
While testing the report using FP_TEST_00 in SE38, I get the below error.
FP_CHECK_DESTINATION_SERVICE Failing
In ABAP 740 and NW 7.4 versions SAP introduce ICM security and not sure ICM block the ADS service. when i test the ADS RFC the status HTTP response showing 404 error and the status text "Not found".
I have gone through all the link and configuration side is correct and no issue found so for.What would be the issue?
Kindly help on this.
Thanks
Senthil
Hi again Senthil,
Ok, so the first thing I'd like to know is a bit about your landscape. Presumably these are two different systems, one running ABAP 7.4 and the other running Java 7.4 with ADS enabled, yes? Is your ADS server a dedicated system for ADS, or is ADS running side-by-side with something else, like an Enterprise Portal, etc?
I will say straight up that my recommendation is to give ADS a dedicated server. It usually doesn't have to be very big, unless you are planning to use for high-volume printing scenarios, so a typical VM will usually work. Assuming this is the case, the first place to start is ensuring your AS Java is correctly configured. I've covered the basics for this in a blog I wrote a while back at .
There are any number of blogs out there about configuring ADS (so I didn't write my own to just add one more). A good one is at .
The basic Note for the sequence of troubleshooting steps in ADS is 944221. Have you gone through this Note?
Cheers,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matt,
Thank you for sharing the link
Portal side i tested wsnavigator and it is successful.
I have gone through the troubleshooting steps for ADS 944221.However i test all the procedure as mentioned in the note. I am able to view the result.
ABAP side i tested the report but error is same and there is no further improvement on this issue.
Also, I have raised the incident to SAP for production and SAP suggested few note but issue remains the same .
Would be grateful if you could give me some more inputs for solving this issue.
Thanks
Senthil
Ok, here are the things to check for the ABAP connection. Note that this all assumes you are not using SSL (https). If you are, there are some extra configuration steps:
See how you get on with that. The issue is probably going to be a wrong password, wrong port, or inactive service.
Cheers,
Matt
Hi Matt,
All the necessary steps are cross verified and till step 5 it is configured properly.
when i ran the report as mentioned the step 6 is not successful and getting the same error.
Please find the default trace information
defaulttrace17.trc
------------------
Caused by: com.adobe.ProcessingException: XMLFM Exception during render: com.adobe.ProcessingException; [Error Log file "2015.06.14.061644DDIC.pdf" written to /usr/sap/DPQ/SYS/global/AdobeDocumentServices/renderErrorLog/errorFiles]
at com.adobe.ads.operation.Render.execute(Unknown Source)
at com.adobe.ads.operation.ADSOperation.doWork(Unknown Source)
... 86 more
Caused by: com.adobe.ProcessingException: XMLFM Exception during render: com.adobe.ProcessingException
at com.adobe.ads.operation.support.RemoteRenderer.renderAllRemote(Unknown Source)
at com.adobe.ads.operation.support.RemoteRenderer.renderAll(Unknown Source)
at com.adobe.ads.operation.support.RemoteRenderer.renderAll(Unknown Source)
at com.adobe.ads.operation.Render.renderWithoutCache(Unknown Source)
... 88 more
Caused by: com.adobe.ProcessingException: CORBA Connection to XML Form Module failed, please verify the binaries are deployed to the os_libs directory
You may be running on a non-supported platform.
at com.adobe.ads.remote.ConnectionFactoryHandler.getConnection(Unknown Source)
at com.adobe.ads.remote.EJB_XMLFormAgent.getConnection(Unknown Source)
at com.adobe.ads.remote.EJB_XMLFormAgent.renderAll(Unknown Source)
... 92 more
Caused by: java.lang.IllegalStateException: Connection to failed service.
at com.adobe.service.ResourcePooler.allocateResource(ResourcePooler.java:98)
at com.adobe.service.ConnectionFactoryManagerPeer.getConnectionResourceFromPool(ConnectionFactoryManagerPeer.java:95)
at com.adobe.service.J2EEConnectionFactoryManagerPeerImpl.getConnection(J2EEConnectionFactoryManagerPeerImpl.java:115)
... 95 more
Please suggest on this
Thanks
Senthil
It looks to me like you probably have a basic issue with your installation (not configuration) of your ADS. You didn't deploy any extra software components to it after installing AS Java, did you? Everything needed for ADS is included in the AS Java installation. Is this a dedicated server for ADS? You might have a look at the file /usr/sap/DPQ/SYS/global/AdobeDocumentServices/renderErrorLog/errorFiles/2015.06.14.061644DDIC.pdf to see if there is more useful information there, but it's things like "Unknown Source" and "You may be running on a non-supported platform" and "please verify the binaries are deployed to the os_libs directory" that give me pause.
What are the operating system and database platform versions? You said this is on NetWeaver 7.4 -- what SP Stack? And what is your kernel release and patch level?
Hi Matt,
We didn't done any installation and extra deployment after the upgrade.
Please find the details information
OS level : Linux 2.6.32-504.12.2.el6.x86_64 SLES-11
Oracle : 11.2.0.3.0 - 64bit
NW 7.4 SP 9.0
Kernel Level : 742_REL Patch 28 UNICODE
/usr/sap/SID/SYS/global/AdobeDocumentServices/renderErrorLog/errorFiles/
Thanks
Senthil
Ok. I don't work with Oracle/Linux, but as far as I can tell, that's a supported combination.
I think you're going to have to wait for SAP to respond to your Customer Incident for this one. Alternatively, start over, reinstall the ADS system from scratch, making sure all of the components (kernel, etc) are properly matched. I do still think you have something mismatched somewhere, indicating an installation problem, and not a configuration problem. Reinstalling might potentially go faster than troubleshooting through the Incident ticket.
Oh, I just clued in on something else you mentioned. Was this an upgrade from a pre-7.4 release? Or did you mean the update to sp9 after initial installation? I've been assuming this was a fresh install. I think potentially, since ADS doesn't store any data other than the configuration you put into it, and it's pretty easy to configure, that a fresh install may be cleaner than an upgrade.
User | Count |
---|---|
73 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.