Wrong Kernel DVD Popup Message

Issue :

 

You are using SAP software provision manager for installing an SAP system. At define parameters phase you need to input kernel DVD. Even after giving correct media label tool gives wrong media error.

 

 

 

 

Resolution :

 

1.       Download Unicode, non Unicode and SL Controller 720/700

2.       Extract related kernel DVD

3.       Extract other kernel DVD and SL Controller

4.       Put all extracted folder to DATA_UNITS folder of original kernel DVD.

                                                                                                                                                                                                                                                        

Reference:

 

SAP Note : 1654937 - How to correctly build the SAP Netweaver Kernel Media

Read more...

HTTP Status 404 - while accessing BO4.0 CMC

Error:

While accessing CMC from url http://hostname:Port/BOE/CMC you get error

HTTP Status 404 -
---------------------------------------------------------------------------
type Status report
message

description The requested resource () is not available.

Resolution:

Even though there are more possibilities for this error. In my case there was an port conflict with earlier tomcat server. So i have changed port number for tomcat port number in file 

D:\Program Files (x86)\SAP BusinessObjects\Tomcat6\conf and edit server file to replace default 8080 port to other open port like 9090

Read more...

Installation of SAP Router on Windows

Environment :

Windows 2008 R2 , X64 Architecture, Public IP with ports opened 3298 and 3299

1.       Download Components ​​

A.      SAPRouter Files

Navigate to service.sap.com/swdc > SAP Software Download Center > Support Packages and Patches > Browse our Download Catalog > Additional Components > SAPROUTER > Download sap router depending on your operating system

 B.      SAP Cryptographic Software

Navigate to service.sap.com/swdc > SAP Software Download Center > Support Packages and Patches > Browse our Download Catalog > Additional Components > SAPCRYPTOLIB > SAPCRYPTOLIB.SAR

 2.       Register SAP router with SAP

Raise an OSS Message under component XX-SER-NET-NEW. After successful registration they will provide you distinguished name. This name is required for further activities and it look like Customer data

Hostname SAProuter : HOSTNAME

IP address SAProuter : XXX.XXX.XXX.XXX

Your Distinguished Name:

"CN=hostname, OU=Number, OU=SAProuter, O=SAP, C=DE"

 3.       Set environment variables

Variable name: SAPROUTTAB     Variable value: D:\usr\sap\saprouter

Variable name: SECUDIR               Variable value: D:\usr\sap\saprouter

Variable name: SNC_LIB               Variable value:  D:\usr\sap\saprouter\sapcrypto.dll

 4.       Create a shared folder on your router machine as folder structure and put all uncarred files in this folder. This will give you saprouter and other required files and uncaring cryptolib will give sapgenpse in architecture specific folder.

5.       Gereate certificate request
Execute following command where sapgenpse is located. In my case it is D:\usr\sap\saprouter\nt-x86_64. After executing command you will find new file certreq in same folder.

sapgenpse get_pse -v -r certreq -p local.pse "CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE" 

6.       Request certificate for sap router
Navigate to http://service.sap.com/saprouter-sncadd and click on Apply Now button. This will give you list of router systems registered with sap. Click on the newly created host name and continue.  This will give you a text box where you need to paste the content of certreq file including begin and end lines from path \usr\sap\saprouter\nt-x86_64 . Continue to Request Certificate. This will give certificate code. Paste all the contents to a notepad with file name srcert and rename srcert.txt to srcert with no extension.  
You will be asked twice for a PIN here. Please choose a PIN and document it, you have to enter it identically both times. Then you will have to enter the same PIN every time you want to use this PSE.

7.       Install the certificate in your SAProuter
Execute following command. After successful exection sap certificate will be installed in your sap router machine.
sapgenpse import_own_cert -c srcert -p local.pse 
8.       Create the credentials for the SAProuter ada
This will create a user used for sap router start and stop. Replace <User_For_SAProuter > with domain\user. if you omit -O <user_for_SAProuter>, the credentials are created for the logged in user account. This will create a file called cred_v2 in the same directory where local.pse is located.
sapgenpse seclogin -p local.pse -O <user_for _SAProuter> 
9.       Check if the certificate has been imported successfully
Execute following comman at the path sapgenpse is located.
sapgenpse get_my_name -v -n Issuer
The output of command should be
CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE

10.   Create Route Tab
Create a file saprouttab in notepad and rename to saprouttab with no extension. This file will consists route tab entries. And will be in following format.

# SNC connection to and from SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
# SNC connection to local system for R/3-Support
# R/3 Server: 192.168.1.1
# R/3 Instance: 00
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.1 3200
# SNC connection to local WINDOWS system for WTS, if applicable
# Windows server: 192.168.1.2
# Default WTS port: 3389
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.2 3389
# SNC connection to local UNIX system for SAPtelnet, if applicable
# UNIX server: 192.168.1.3
# Default Telnet port: 23
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.3 23
# SNC connection to local Portal system for URL access, if applicable
# Portal server: myserver.mydomain
# Port number: 50003
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" myserver.mydomain 50003
# Access from local network to SAP
P 192.168.*.* 194.39.131.34 3299
# deny all other connections
D * * *

 11.   Start SAP Router
This completes your installation of sap router. And following commands are required to operate sap router.

start router : saprouter –r

You can  also use saprouter -r -V 2 -K "p:CN=example, OU=Number, OU=SAProuter,O=SAP, C=DE"  

stop router  : saprouter -s

soft shutdown: saprouter -p

new routtab  : saprouter –n 

12.   Test SAP Router

Follwing notes will guide you to test sap router installation.

Integrating SAProuter into a firewall see note 48243
Ping from SAProuter server to sapserv2 (194.39.131.34)
SAP Remote Services: Technical preparation (see SAP Note 812386)
niping.exe -c -H /H/<local_SR>/H/194.39.131.34/H/localhost 

13.   Open Connection to SAP
Maintain new sap router entry for the system , so that SAP can access your system for remote support. To do this navigate to
http://service.sap.com/system-data -> "SID" system -> "System" Tab -> SAProuter drop-down list and save the entry for sap router.

14.   Trouble shooting
If there are any issues with installation following commands will give you the logs

Output of the command 'sapgenpse'

Output of the command 'sapgenpse get_my_name -n all'

Output of the command 'sapgenpse seclogin -l'

Files dev_rout and saprouttab 

15.   References
https://websmp101.sap-ag.de/saprouter-sncdoc
http://scn.sap.com/community/netweaver-administrator/blog/2012/06/17/detailed-sap-router-installation-for-windows-x64
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c06c8846-c160-2d10-d18e-d9961e9c7219?overridelayout=true

Read more...

Installation of SAP Addons with SAINT

Introduction

SAP offers a wide range of add-ons that you can use to enhance your standard SAP system. These add-ons can be Industry Solutions, plug-ins, or customer-specific development projects.SAP Add-On Installation Tool (transaction SAINT) was developed to enable users to install and upgrade add-ons directly from their standard SAP system. You do not need to access the operating system or restart the system. Prior to installation, numerous import conditions are checked to ensure that only add-ons that fit the available SAP system can be installed.

The Add-On Installation Tool is delivered in its own Support Package, the SPAM/SAINT Update. We enhance and improve the tool constantly, and recommend that you always import the latest version from SAP Support Portal before performing an installation or upgrade

Prerequisites

·         The Change and Transport System (CTS) is configured correctly

·         There is enough space in the transport directory (UNIX: /usr/sap/trans)

·         You are using the latest version of Add-On Installation Tool

·         If you have already executed a modification adjustment (for example, in the development system) and have created an adjustment transport from it, then you can include it in the follow-on systems in the installation queue. You must have distributed maintenance certificates in your system if you want to import SAP add-on packages.

·         At OS level EPS/in contents are owned by sapsid and belongs to sapsys group(unix). Folder will have permission of 777 to its subfolders and contents.

·         All open data requests need to be processed before upgrade. All setup tables must be cleared if your system is connected to BI.

·         De schedule all background jobs.

Features

·         Add-On Installation Tool checks compliance with import conditions, such as the SAP NetWeaver Release and the Support Package level of the various software components, accepting or rejecting them accordingly.

·         Restart capability - The installation itself can be restarted, like the Support Package import process.

·         Special import procedure - You can use a special import procedure to reduce downtime while importing add-on packages

·         Background Processing - You can also schedule the modules with defined start times for background processing.

Loading Installation Packages

Loading Installation Packages from the Frontend – This option allows you to upload packages directly from your computer. After selecting this option navigate to the package path and decompress it. This will copy uncarred files to /usr/sap/trans/EPS/in. If the patch size is more than 10MB this option is not suggestable.

Loading Installation Packages from the Application Server -  Put all downloaded addon files in a directory and uncar .SAR, .CAR files using sapcar –xvf abcd.sar command. This will extract .PAT and .ATT files in /EPS/in folder in current working directory. Uncar all file and upload these file to your sap server at path \usr\sap\trans\EPS\in or directly you can uncar the files on your server at OS level.

Once uncarred packages are uploaded on to the server go to transaction SAINT > Installation Package > Load packages > From application server. In initial screen all installed components are displayed. Click on start to start installation process.

 

Installing and Upgrading Add-Ons

Logon to the client 000 with the user have authorizations like sap_all profile. Do not log in with user ddic and sap*.

The Add-On Installation Tool guides you through these. Use the Continue button to move to the next step. Choose Back to return to the previous step.

                                                                                                                          

Define the installation queue - Since it is often not only one add-on that is installed but several add-ons at the same time you first have to select the add-on packages that are to be installed. From the add-on packages that are selected, the system calculates the installation queue in the right order, that is, all packages that the installation consists of.Depending on whether your system is configured in the Solution Manager or not, you can define the installation queue using a stack configuration (Solution Manager) or manually.

 

Define the start options or check those selected - You can define start options for the individual modules according to your system requirements. If you confirm the dialog field without changing any settings, the import tool assumes the default start options, according to the selected import mode. If you change any settings, you can save them as a template for future import activities.

 

Adjusting Modifications

If you have modified SAP objects from the add-on that you want to install, you need to adjust these objects when importing them. This ensures that your modifications are not overwritten by SAP objects. Transaction SPDD adjusts Dictionary objects, while transaction SPAU adjusts repository objects.

If you have already performed the modification adjustment in a system (in a development system for example), you do not need to perform it manually in the follow-on systems (quality assurance and production systems). You can include the transport requests that you created for the modification adjustment (modification adjustment transports) in the installation queue. The modification adjustment then takes place automatically when the queue is imported.

Modification Adjustment for Dictionary Objects - Transaction SPDD

Modification Adjustment for Repository Objects - Transaction SPAU

These modifications will be taken care by developer.

 

Checking Logs

The queue calculation log displays detailed information for queue calculation. The log is structured hierarchically. The highest package occupies the highest position. This log provides you with various details, including the prerequisites for importing the package. You can thus to determine which prerequisites have not been met, preventing successful queue calculation.

If analyzing the log does not solve your problem, you can save it, using the print function. You can then send a problem message to SAP and include the log as an attachmen

​​

t.

​ ​

 

 

​

Read more...

SAP Support Patches Check List

1. Confirm and sign-off the support pks and combination of SPs that will be applied and project/test team available for testing
2. Verify all functional and cross-system dependencies are met. Must review and OSS note 822379 (netweaver 7 version)
3. Enough Disk space and atleast 85% free space on sapdata filesystem
4. Check if file system /usr/sap/trans/data and ../EPS/in  has free space, if not clean-up old support package data files or Pat files in EPS/in
5. Post a system message & a login screen message indicating the outage (refer to procedure Applying Support Packages).
6. Check if no tablespace is over 85 % full
7. Verify if you have a recent backup., if not schedule a full on-line backup. If production, have a backup just before Support pkgs to be safe.
8. Unpack all required SP's and then load them into SPAM and verify that all queues are OK  e.g SAPCAR -xvf /sapcd/sp/XXXXXXX.CAR –V
9. Update Spam with latest version from Service marketplace. Also ensure binaries R3trans and tp are updated if necessary. If you are not sure, usually it will not hurt to update these anyway.
10. Define Queue and perform TEST import and report any SPDD/SPAU conflicts to project/developers
11. Prepare one excel sheet with component list and uncarred file name.
12. Check permission on components present in EPS/in. Pat file should have owner as sidadm belongs to sapsys group.
13. Carry out any modifications done at development for same activity. Import the transports before you start import of support packages. Once started you are not allowed to do any transports and even if you try you will end with error OCS is locked by username by transaction SPAM. In this case its very difficult to apply notes or to do any changes.

Read more...

SPAM Import Steps and Explanation

1.      PROLOGUE

This phase checks whether you are authorized to import Support Packages.

2.      CHECK_REQUIREMENTS

This phase checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.

3.      DISASSEMBLE

This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.

4.      ADD_TO_BUFFER

This phase places the queue in the transport buffer of your system.

5.      MODIFY_BUFFER

This phase prepares the transport buffer for correct processing of the following import phases.

6.      TEST_IMPORT

This phase performs a test import for the queue with the transport control program tp. The system checks whether there are objects that are in open repairs and that are overwritten during the import, or whether other conditions prevent the import of an object.

7.      IMPORT_OBJECT_LIST

This phase imports the object lists for the Support Packages in the queue into the system.

8.      OBJECTS_LOCKED_?

This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests.

9.      ADDON_CONFLICTS_?

This phase checks whether there are conflicts between objects in the queue and any installed add-ons.

10.      SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP).

Import 1 Module

11.      CREATE_VERS_BEFORE

This phase generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).

12.      SPDD_SPAU_CHECK

In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).

13.      DDIC_IMPORT

This phase imports all ABAP Dictionary objects in the queue.

14.      AUTO_MOD_SPDD

This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

15.      RUN_SPDD_?

In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

16.      LOCK_EU (only for import mode downtime-minimized)

This phase locks the development environment.

17.      INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state.

18.      DDIC_ACTIVATION

This phase activates the imported ABAP Dictionary objects.

Import 2 Module

19.      IMPORT_PROPER

This phase imports all the Repository objects and table entries if they were not already imported in the INACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of the name tabs.

20.      PREPARE_XPRA

This phase prepares the execution of the XPRAs and after-import methods.

21.      UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment.

22.      AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.

23.      XPRA_EXECUTION

This phase executes the XPRAs and after-import methods.

24.      ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source texts and screens).

Clean Up Module

25.      RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

26.      CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts in the database.

27.      EPILOGUE

This phase completes the import. Among other things, it checks whether the queue has been processed completely.

Read more...