~SAP BASIS RESOURCE ~

Download JAVA SC Patches via NW JAVA Support Tool – An Easy Way

2017-08-22T18:28:00.002+05:30

As we all know calculating the required dependencies of a JAVA SCA patch leads to lot of manual work sometimes and also prone that you may miss any required dependent patch which can lead to unwanted problems during patching process.

SAP NW JAVA Support Tool is a great troubleshooting tool and have amazing capabilities to record and collect logs however, there is another feature which lot of people are not aware of i.e SC patch tools.

Below are the steps to download the required patch along with the all required dependencies.

1. Download and install NW JAVA support tool 1.0 as per sap note 2352717.

2. Launch the tool NWJavaSupportTool.jar and connect to the JAVA instance.

1. Click on SC patch tools

1. Tool will check all the JAVA components installed in the system against the latest patch available.

1. Select the required components to be patches. In this case I have selected AJAX-RUNTIME. Tool is showing AJAX-RUNTIME SP 05 patch 20 as latest which is correct as checked at SMP

1. Tool will calculate the required dependencies. Add them in download basket by selecting all dependent patches.

Here you go and ready for patching. It’s quite easy as compared to manual calculation

Applying Support Patches in Netweaver 7.3 Java Stack

2012-09-20T12:29:00.000+05:30

First we need to determine the current SP level of the running Java Stack of the AS JAVA

1. Using JSPM . You can run the JSPM tool from the following location
Drive:\usr\sap\SID\J02\j2ee\JSPM

Well , got the following error while executing the JSPM tool.
"An error has occurred during the execution of the JSPM_MAIN phase.
Cannot initialize application data. Error occurred while trying to get the SAPLOCALHOST parameter value from the instance number: 2 on host: GDC-UAT via SAPCONTROL the web service API. See SAP Note 1401712 for further information. java.rmi.RemoteException: Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://GDC-UAT:50213" com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://GDC-UAT:50213"

To resolve this issue we need to change the entry of the parameter in DEFAULT.PFL file till we finish with JSPM tool also , we need to start all sapstartsrv services in the cluster.
Changed Entry " service/protectedwebmethods = DEFAULT "

Once the issue is resolved please check the version and level of SP's in JSPM.

As, we can not determine the SPS level by just looking at the individual SP level. We can check the current SPS level using MOPZ or at the stack calculation at the Service Market Place. Implementation and maintenance of SAP NetWeaver 7.3 via SP Stacks is only possible via SAP Solution Manager's Maintenance Optimizer (MOPZ)

https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001309472010

SAP Netweaver 7.3 Installation Step by Step - Windows/Oracle

2012-09-14T12:28:00.001+05:30

Here are the detailed steps to install a SAP Netweaver 7.3 Central Instance ( CI ) on the same host.
Here is the diagram to give more understanding regarding the standard ABAP + JAVA System.

So , let us start the installation . It is recommended if you check sap note 611361 and PAM matrix for OS and hardware requirement. Specially if you are installing on UNIX based system , please do check the above resources.

1. Download the Netweaver 7.3 media from SMP . Once , you have extracted the media you should be able to have the following folder. ( These may be different for you)

2. Prepare OS and Java Enviorment :

Set the Virtal memory as per the note 1518419.

Install JRE and set the environment variables on the host OS.

3. Install the 11g Oracle DB.
On the database server, place the Oracle RDBMS media in the media drive and change to the directory::\database\SAP\
The media I download is having the sapserver.cmd file at Drive:\Oracle_RDBMS\51042334\database\SAP

Install the relevant patch as per note 1503709

4. Start the Installation:

Once you browse the installation master media please choose the sapinst as per the desired OS and DB installation.
Here we have selected the media for Windows 2008 R2/Oracle installation.

As , you can see we do not have dual system selection expect for PI .

Here are the screenshots to gave you an idea regarding the installation.

Installation of Java Stack

For EP Installation you have to select following Usage Types.

Once the installation if completed for both stacks ( Abap and Java) , you can check the NWA .

The post installation steps for both Abap and Java instances as per the installation guide.

Oracle Upgrade and Troubleshooting

2012-02-08T11:09:00.001+05:30

Starting Today I would be publishing Oracle Upgrade steps in SAP environment. Keep Looking :)

EHP4 Installation using EHPi Tool

2010-06-11T21:34:00.001+05:30

Once you have downloaded the required EHP4 enhancement components using Solution Manager.Download the latest EHPi tool from the service market place . After that perform the following steps ( These are performed for ABAP installation).

1. Extract the EHPi download SAR file to the usr/sap/ , this will generate a EHPi folder with the required executable files.
2. Login into the target system with SIDADM account.
3. Open the cmd prompt with adm user and give the command STARTUP.BAT jce_policy_zip=" , Here you have to five full location path where the jce policy archive is stored , this will in turn start the process with a open command window
4. Open the explorer with http://:4239 . To start the program from IE . However , there are many other ways to do that you can find more information on service marketplace for this.
5. Start the webstart from the portal. ( in case of prompt to open or save sdtdsu.jnlp file on x64 enviorment , install the latest JAVA VM.

Adobe Document Services Configuration Document

2010-02-21T12:41:00.002+05:30

1. Introduction.

This document covers the phases which were performed during the course of the ADS implementation at the CRM Box. The system is a Dual Stack (AS ABAP+ AS JAVA) installed on the same machine with SP12 level. The goal is to setup the basic authentication model for the ADS services.

Please note that the document only covers the overview of the configuration phase and one should always follow to the updated document at the SDN network.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6

The basic steps performed to setup the ADS at the CRM box were-

Steps needed to be Performed at Web AS JAVA

At AS- ABAP side we need to install ADS services. We need to configure users/groups and Destination.

***For interactive forms scenario we need to configure web service client service at the Web AS JAVA side.

Steps needed to be performed at Web AS ABAP

We need to configure RFC Destination, User/role and ICF service at the AS ABAP

2. Phase-1.

This phase covers the reset of the system users which were required to configure and validate the ADS services on the CRM system.

Initially during the configuration and testing phase the password for the following users were required

1. Crmadm

2. SDM User

3. J2ee_admin

1. Have reset the password system account “crmadm” user to “***” to gain the access for go.bat directory to start the JSPM tool.

2. Have reset the password of SDM user to “***” to check/apply java support level/stacks.

Reset password of SDM user to access JSPM and verify the Support level for the ADS.

Steps to change the SDM password

SDM is default in Integrated Mode, first you have to take it to Standalone Mode and after changing password take it back to Integrated Mode

Stop the server from the SAP Management console

Navigate to the SDM\program directory in MS-DOS window

start the standalone SDM

sdm jstartup "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "mode=standalone"

change the password

sdm changepassword "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "newpassword=*****"

Take SDM to Integrated Mode: sdm jstartup "mode=integrated"

3. Activate the emergency user through the config tool.

Start the config tool ( Path: C:\usr\sap\CRM\DVEBMGS10\j2ee\configtool )

Set the following UME properties:

ume.superadmin.activated True

ume.superadmin.password Password

Restart the AS Java

** In the current CRM box being a dual stack box the j2ee_admin user resides in ABAP client and password should be reset from the client itself**

3. Phase-2.

This Phase covers the steps performed on the CRM system to setup the ADS services.

Steps performed sequentially to setup ADS (interactive forms scenario) at the CRM box.

1. Start Configuration tool at AS JAVA side (C:\usr\sap\CRM\DVEBMGS10\j2ee\configtool\configtool.bat)

Add following parameter if not found at the cluster data à instance_dvebmgs10à server

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptorJTSInitializer

2. Restart the AS Java.

3. Login into the http://server:port/useradmin and check for the ABAP Source client ( change it to 800 )

4. Check/create “ADSuser” user at the ABAP source client using su01.

5. Specify/check the role ADScallers assigned to the user as per guide.

6. Create ABAP connection using RFC destination using SM59. As per page number 18 of the guide.

7. Enter the URL http://:/AdobeDocumentServices/Config .

To find the port number of j2ee engine use this formula to calculate the port number. (Port number =50000+100*instance number)

Choose test à rpdata(test..), give adsuser users credentials and choose submit. If the configuration for the Users (Step 4, 5) is correct the system displays the version number of the ADS in the response area.

8. Test the Report FP_PDF_TEST_00 for displaying the version number of the ADS.

9. Activate the ICF service in ABAP Side

Log on to your SAP Web AS ABAP system
Choose transaction SICF.
Choose default host → sap → bc → fp in the tree.
Choose Service/Virt.Host → Activate

10. Create /Check the destination service

· Start the visual administrator tool àservicesà Destinations

· Under runtime select HTTP. Choose New and create in the navigation panel

· Configure the HTTP destinations for ADS by choosing Services ® Systems ® Destinations in the Visual Administrator for the J2EE Engine.

· Create an HTTP destination with the name FP_ICF_DATA.

· In the dialog box that follows, enter the name FP_ICF_DATA_, where is your ABAP system, for the new destination and choose OK.

· Under Connection Settings, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in the URL field:

· http://:

· To display the host name of your SAP NetWeaver AS ABAP log on to SAP NetWeaver AS ABAP and call transaction SICF. In the main menu, choose Goto → Port Information. The information is displayed on a screen; where the HTTP_port is specified under Services.

· Select the option BASIC for authentication and enter the service user (including password) that has authorization for Adobe in the standard client of the back-end ERP system.

· Choose Save.

11. Now run the report FP_CHECK_DESTINATION_SERVICE
once run this report without checking the destination and after that run with checking the destination box. Both should return the same number of bytes as per note 944221

12. Goto se38 : Program name, Now Execute report FP_PDF_TEST_00

If the program Execution shows a two page PDF document then ADS configure is done.

13. Obtain the Reader Rights Credential

You need to setup the RRC for the Adobe Interactive forms scenario. To obtain your Reader Rights Credential, see SAP Note 736902. Furthermore, you can get a trial 6-month Reader Rights Credential from SDN network.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/adobe_credential_sneakpreview_nw04.zip

14. Install and Configure the Reader Rights Credential

Copy the credential file (filename.pfx) to the /usr/sap//SYS/global/AdobeDocumentServices/TrustManagerService/trust/credentials directory

Configure the Credential Attributes:

Logon to the Visual Admin
On the Cluster tab, choose Server - > Services -> Document Services Configuration.
On the Runtime tab, select Credentials.
From the Type field, select the type of credential you are configuring (P12 record)
In the Alias field, enter the alias ‘ReaderRights’
Choose Browse to search for the name of the credential and then Select
In the sha1 field, enter the sha1 value. This value is available in the text file which is found along with the certificate in the zip file.
In the password field, enter the password you received along with the credential. In this case, you can enter your own password or the same value in the text file.
Confirm the password and click Add.

15. Restart the service PDF Manipulation Module for changes to take effect.

Logon to Visual Admin
On the Cluster tab, choose server -> Services -> PDF Manipulation Module
Right click and stop the service.
Once stopped, right click and start the service

4. Phase-3.

This Phase covers the Troubleshooting part done at the CRM system.

S.n.	ISSUES	RESOLUTION
1.	While accessing the Visual admin through normal user (having J2EE_ADMIN role) it is giving error, Apart from that the j2ee engine still crashed when accessed by "useradmin " through the UML portal.	Followed the Note 724452
2.	*After activating the emergency user sap I was not able to reset the password for j2ee_admin or create a new user in identity management**. An error occurred in the persistence. The original message (possibly not translated) was: "Attribute "lockreason" on namespace "com.sap.security.core.usermanagement" of principal "UACC.R3_DATASOURCE.J2EE_ADMIN" is not modifiable.” Contact your system administrator. Current user has user creation permissions in the UME, but cannot create users in the back-end system (data source). The original and possibly untranslated message was: "No active writeable datasource found for user creation, check your Persistence Configuration."	The ABAP Source client was set to 001 at the Portal. Changed that to 800 Client.
3.	When trying to execute the report FP_TEST_00 i am the following error An exception occurred which is explained in detail below. The exception, which is assigned to class 'CX_FP_API_INTERNAL', was not caught and therefore caused a runtime error. The reason for the exception is: Error in include information for function module /1BCDWB/SM00000002	Follow SAP NOTE 1076159: Download the program FP_GENERATE_FUNCTION_MODULE Run this program with FP_TEST_00 in the input parameter of this report. The report, FP_TEST_00 generates a few function modules based on the entries in few custom tables which should be refreshed. Thus by applying this note we refresh the entries.
4.	While accessing the Document services configuration with the visual admin tool , i am getting the error " can not load the required classes for the document services configuration "	Checked Note 1017526 and restarted the cluster
5.	While running the report FP_TEST_00 it was giving error” cannot find PDL type for output device LP01”	Installed a new printer device ( PDL Supported) and set it default for other users.
6.	While trying to execute the interactive form http://server:8010/sap/bc/webdynpro/sap/zneri_zadobe and after putting the credentials it is giving following error . The following error text was processed in the system CRM : WebDynpro Exception: ADS: Request start time The error occurred on the application server 187799-ap_CRM_10 and in the work process 0 . The termination type was: RABAX_STATE The ABAP call stack was: Method: RAISE of program CX_WD_GENERAL=================CP	Re-installed the Readers Rights credentials configuration and restart the PDM service.

Solution Manager 7.0 EHP 1 Installation

2010-02-20T14:10:00.002+05:30

Here are the steps complied after reading the installation guide which needs to be performed for the installation of Solman 7.0 ( EHP1 ) . Always do refer the updated guide at SAP service marketplace site.
Solman 7.0 ( EHP 1) Installation ---

Prerequisites: 64 bit platform with oracle 10.2.0.2 or higher in case you are using windows 2008 server

You start SAPinst

On the Welcome screen, choose Software--> Life-Cycle Options-->Additional

Preparations--> Prerequisites Check.

Central System Installation software checks

Paging file size -- should be 1 times RAM plus 14 GB .

To check paging file size:

Choose Start -->Control Panel -->System.
Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008).
Select Performance Settings--> Advanced.
If required, in section Virtual memory, choose Change.

Perform a local installation ( No Domain Installation )

Configure a local SLD

SLD HTTP Port --The HTTP port of the Java system where the SLD is installed. The following naming

convention applies: 500.

Disable windows firewall.

Reducing the Size of the File Cache---If you are not using windows 2008.

1.Choose StartControl Panel-->Network Connections--->Local Area Connections.

2.In the Local Area Connection Status dialog box, choose Properties.

3.In the Local Area Connection Properties dialog box, double-click File and Printer Sharing for Microsoft

Networks.

4.Select Maximize data throughput for network applications

Download JDK from ( JSE 1.4.2 x64)

http://www.sun.com/software/javaforbusiness/sap_download.jsp

Download

JCE policy 1.4.2 from

http://www.sun.com/software/javaforbusiness/sap_download.jsp

Go for Central Instance Installation .

Check for Windows Server 2008: You require the Oracle Instant Client Version 10.2.0.4.8.

Oracle Installation :

On the database server, start the Oracle Universal Installer as follows:

Place the Oracle in the DVD drive and change to the directory: :\NT\
Double-click the file sapserver.cmd.
In the installation phase "Configuration Assistants"
If you see an error message, choose OK. Ignore the following Warning screen and choose OK.
Choose Next.

SAP Installation :

You can use sapinst.exe -p To see a list of all available SAPinst properties, open a command prompt and

start SAPinst with the option -p:sapinst.exe -p . ( required in case of manually defining the port number

)

1. Use the local administrator account for the installation.

2.If you want to install a new SAP Solution Manager system from scratch, choose SAP Solution Manager

SAP SystemsBased on AS ABAP and AS Java. ( go for central

Instance)

After the installation is completed check for ABAP and JAVA users :

Start a Web browser and enter the following

URL:http://:500 with user java_admin .

Install the license:

http://help.sap.com/nw70SAP NetWeaver 7.0 Library (including Enhancement Package 1) English--->SAP

NetWeaver Library-->Technology Consultant's Guide-->Cross-NetWeaver Configurations->SAP License Keys

Follow the sap note 94998 for updated method to request license key.

****http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a7/512d23407a11d1893b0000e8323c4f/frameset.htm**** (licensing for java engine, J2ee)

Apply the latest kernel and support packages for abap and java-----check sap notes 19466 and 1276022

For ABAP use SPAM

For java use JSPM

Install the SAP online Documentation---

Install the SAP online documentation in your SAP system as described in the README.TXT file contained in

the root directory of the online documentation DVD, delivered as part of the installation package.

Performing Initial ABAP Configuration

When you have installed your SAP ABAP system, you have to perform the following initial configuration

steps:

Perform a consistency check
Configure the transport management system
Perform basic operations
Configure system parameters
Configure the number of work processesH‚
Configure kernel parameters
Install languages and performing language transport
Configure the integrated Internet Transaction Server(ITS)
Maintain your company address for initial users
Configure AS ABAP to support Secure Socket Layer (SSL)
Configure Fully Qualified Domain Names (FQDN)
Configure business applications

1. Perform a consistency check --Call T-code SICK

2. Configure the transport management system --

perform post installation steps for TMS . T-code se06-->Standard Installation-->perform post

installation steps.Call STMS in abap System ( Which client ? )

( put all the steps to coinfigure STMPS in SOLMAN)

3. COnfigure Operation mode ( can be skipped for now) RZ03.

4. Setup Logon groups ( SMLG)

5. Setup Administrators for background jobs, take print from this url and (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/74/08703713bf277ee10000009b38f8cf/frameset.htm)

6. Schedule background Jobs ---( define the steps)

7. Install a printer--Go to command line > SPAD and enter > choose Output devices > Click on Change >

Click on create new > define the output device > spool server, short name, host id (printer name), define

to the output type (choose F:frontend printing or L: for LPR printing) > and save the config.

( If the printer is a laser printer it usually prints with Device type HPLJ4 or HPLJ5.) , otherwise

import the drive from tcode SPAD, goto "Utilities --> For device types --> Import".)

8. Configure the system log ---To display system logs, choose Tools ® Administration from the R/3 initial

screen.The system displays the System Administration initial screen. ChooseMonitoring ® System log. The

System Log initial screen appears.

Checking the Configured Number of Work Processes ( * can be done later )

Check sap notes 39412 and 9942.

Configuring Kernel Parameters --

Check sap notes 146289 and 835474

Installing language and performing language transports ---

i18n ( t-code)

Perform initial JAVA configuration---

1. Create a second administrator user -- Start Identity management

http/https://hostname:as_http_port/nwa

http/https://hostname:as_http_port/irj

create new user (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4a/e06f429c789041e10000000a1550b0/content.htm)

Check for JAVA VM memory settings ( note 723909)

Performing Oracle-Specific Post-Installation Steps---

Security Setup for the Oracle Listener ( note 186119)

Enabling DB monitoring ( Note 706927)

Perform Initial Backup using brtools.

Configure SLD--- (* can be done later on )

Configuring SAP solution Manager --- check configuration guide at service market place ****

solman_setup ( T code)

SAP Implementation Journey

2010-02-14T11:58:00.000+05:30

Hello , I would be defining the technical road map and activities which were followed by me for SAP implementation in this post. This topic would be further categorized in few sub topics.

Common Problems with SAP Interactive Forms by Adobe - PART II

2009-07-03T15:29:00.000+05:30

Always Refer to the original Article at Common problems with SAP Interactive Forms by Adobe - PART I - If you have not read it yet please read it! Part I contained the JAVA side common configuration errors, now in part II we will check the issues wich are connected to ABAP side or occure in a later stage of the configuration.
P5. The destination Service
Sympthoms- The ABAP Test Program: FP_PDF_TEST_00 returns the Version information of the ADS but the Report: FP_TEST_00 fails with the Exception: FPRUNX001- In the default trace you see enty like: com.adobe.ads.destination.DestinationException:
Destination exception during destination lookup: FP_ICF_DATA_
- In the default trace you see enty like: File Not Found while reading Dest URL:
http://:/sap/bc/fp/form/layout/.XDP?fp-language=
Possible cause:- Please check SAP note: #915399 what describes how the destination Servce has to be created / maintained. - When you maitain the URL to the FP_ICF_DATA_ destination, quite often the JAVA port is used instead of the ABAP. Make sure you use the hostname and port what you see in transaction: SMICM on the ABAP side! - If you do not enter specific client, the logon will take place in the default client on the ABAP side. Please make sure the ADS_Agent user exists in the client where the JAVA stack is trying to log on. - Make sure the Service: default_host/sap/bc/fp is activated in Tr. SICF on the ABAP Stack. - Make sure in Transaction SU01, that the ADS_Agent user (-or the user you have defined in the Visual Administrator for the destination -) is: - not locked - type: System - assigned to the role: SAP_BC_FP_ICF
P6. Printer Devices
Sympthoms- message FPRUNX 113 ("Cannot find PDL type for output device XXXXX")
Possible cause:- The SAPWin printer can not be used together with SAP Interactive Forms by Adobe. Please reas SAP note: #685571Unfortunatelly there is no workaround for this.- Check the printer device associated with the caller user, make sure this printer does not uses the SAPWIN device type.
P7. Problem in complex landscapes only in NW04
Sympthoms- You use a Webdynpro for JAVA Application containing an Interactive Form, the form is not displayed. - In the default trace file you can see the following error: java.net.SocketTimeoutException:Read time-out
Possible cause:- Please check the stting:Visual Administrator: Server -> Services -> Configuration Adapter -> webdynpro -> sap.com -> tc~wd~dispwda Check entry "sap.ADSCallingMode" make sure here the value: 'SOAP' is entered. If not please change this to 'SOAP' and restart the cluster.
P8. Problem with the JMX Service.
Sympthoms- In the default trace you can see the following exception: Stack Trace:
com.sap.engine.services.jmx.exception.JmxSecurityException:
Caller Guest not authorized, only role administrators is allowed to access JMX
Possible cause:- Start Visual Administrator and navigate to: Server node -> Services -> Security Provider. Please also make sure that the MBeanAdmin is mapped to the Administrators Security role on both: com.adobe/AdobeDocumentServices*ADS-EJB and com.adobe/DocumentServicesLicenseManager*ADS-License
P9. xACF controls.
Sympthoms- You use Interactive Forms in Webdynpro Applications. The Form you are using uses ACF (Active Component Famework) technology and not ZCI (Zero client Installation). The PDF is not displayed, instead you see something like a broken image at the place the PDF should be displayed. - You do not see adobe specific exceptions in the default trace file of your J2EE engine.
Possible cause:- The Active Component Framework is not installed on your client. Please follow SAP note: #766191 and install the latest version of the Famework to your client.- You are not using Internet Explorer for accessing the Webdynpro Application. Unfortunatelly ACF is only running in Internet Explorer. In Firefox / Mozilla you can only used ZCI based forms. - You Famework is too old. Please try completely removing it as described in SAP note: #846952 and reinstall the latest version again as described above.
P10. Error while reading trusted anchor configuration information
Sympthoms- The Exception: adobe.service.sap.configuration##com.adobe.service.sap.configuration#######
SAPEngine_System_Thread[impl:5_59
##0#0#Error#1#/System/Security#Plain###
Error while reading trusted anchor configuration information: can be raised when the system tries to seach one entry in SeureStore service. But within the default installation, this entry does not exist.
Possible cause:- This can happen if you never opened the DocumentServiceConfiguration Service in the Visual Administrator. Open VA and navigate to: Server node -> Services -> DocumentServiceConfiguration.-> The mentioned exception should not occure again.

Common Problems with SAP Interactive Forms by Adobe - PART I -

2009-07-03T15:04:00.000+05:30

Always Refer to the original Article at https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5484

This weblog is based on problems we often see at our standard support chanel. Here I list the common sympthomes, and common causes. The list (of course) is not complete. If you have one of these sympthomes, it is not sure you have the same problem, what you find here. I hope you will find it useful ;-)
P1 - Plattform / Basis Level -
Sympthoms- The standrad test report: 'FP_TEST_00' or 'FP_CHECK_DESTINATION_SERVICE' "hangs". It runs enendless.- There are NO files (n)or directories located in the "/usr/sap///j2ee/os_libs/adssap/XMLFormService" folder. Maybe the complete: "/usr/sap///j2ee/os_libs/" folder is empty. - You see the following exception in the default trace of the J2EE engine: Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001 - You see the following exception in the default trace of the J2EE engine: javax.xml.rpc.soap.SOAPFaultException:
Transaction system failure in method rpData.
Possible cause:- The ADS is installed on a plattform, that is currently not supported by SAP for ADS. Please check the avaliablity at: Product Availability Matrix - Mixing of different Netweaver releases (NW04 and NW04s) -> This is unfortunatelly not possibble the J2EE engine release has to match with the ABAP stack release in order connect them properly.- The ADS SP level does not match the J2EE engine SP level. -> Please update the software components to have the same support package level.
P2 - Problems with the Credential -
Sympthoms- The printforms work fine, but you can not create interactive forms. - You have error during registration of the credential file.("An error occurred while updating the credential expiry date for alias XXXX") In the default trace you see: java.io.IOException: Error in loading the keystore:
Private key decryption error:
(java.lang.SecurityException: Unsupported keysize or algorithm parameters)
- You see the error: "An error occured while indexing the credential files" while trying to open the credential file.
Possible cause:- First make sure the credential file is ok. You can test this as follows: Download the credential to your local machine (Windows). Start it with double click. The certificate import wizard will be started. Try importing this file, and provide the password at step 3, what you have recived with the credential. If the import is successful that means the crendential is ok. If not, please contact SAP support. - Make sure you have the unrestricted version of JCE installed on your system. You can download this from your JDK vendor. For details see SAP note: #899808 - You have to restart the J2EE engine after you have registered the credential. - The IIOP Service has to be running to register the credential. Please check P3. - Make sure the credential can be found in the correct direcotry. For details see SAP note: #848539
P3 - Problems with the IIOP Service -
Sympthoms- You see the error: "An error occured while indexing the credential files" while trying to open the credential file. (as in P2)- You see the following exception in the default trace file: Caused by: org.omg.CORBA.INITIALIZE:
can't instantiate default ORB implementation com.sap.engine.services.iiop.internal.ORB vmcid: 0x0 minor code: 0 completed: No
- You see the following exception in the default trace file: org.omg.CORBA.BAD_PARAM: Not found ServiceContext with id=0 vmcid: OMG minor code: 26 completed: Maybe
- You recive the following exception, while testing the ADOBE Document Services functionality (e.g FP_TEST_00) ERROR CODE :
100.102
ERROR
MESSAGE :
SOAP Runtime Exception: CSoapExceptionFault : SOAP fault found in SOAP document /Transaction system failure in method rpData./...
Possible cause:- Make sure the start up mode for the IIOP Service is set to 'Always' on both Server and Dispatcher nodes! - After enabling IIOP Service please restart the J2EE engine. - Please check P1 as we have quite often see, that there were IIOP related exceptions in the default trace, when the used plattform was not released for ADS. - Make sure you have at least one data element bound to the form. As we have seen CORBA exceptions when there was no databinding at all.
P4 - a common problem with the ADSUser -
Sympthoms- When you try to test the ADS functionality via the URL: http://:/AdobeDocumentServices/ConfigYou recive the error: Incorrect content-type found 'text/html'
- The response headers of the ADS look: HTTP/1.1 302 Found
Connection: close
Location: http://:/AdobeDocumentServices/Config/ChangePassword
Server: SAP J2EE Engine/7.00
Date: Tue, 05 Sep 2006 11:58:10 GMT
Possible cause:- The password of the ADSUser user is initial. This happens often in the following cases:>> a. The Installation is double stack, and the ADSUser is defined as 'DIALOG' on the ABAP side. Please change this to 'SYSTEM'. >> b. You use some other UME mechanism, what request's the password change for ADSUser. -> You should make the necessary steps to aviod this request. >> c. Please check the following: Go to Visual Admin:
-> server -> service -> security provider service -> user management tab, then select user ADSUser.
If option 'No password change is required' is not selected, please check it.

~~~~~SAP BASIS RESOURCE ~~~~~