I often come across SAP customers who are not sure of how to check the equivalence level of support packages at the service marketplace. I hope that this document will help in such cases. Here we will take an example of SAP_BASIS package SAPKB70026 and would check the equivalence level of this package in releases as 701, 702 and others.

The link where we can check this is "http://service.sap.com/patches" and in the left menu, we should click on "Search for Support Packages and Patches". After that we can follow as given in the screenshots and we will get the desired packages.

Click on search after entering the package name.

Click on "View content info" button.

Now we click on the field value of "Expanded Attributes" and get the result for other releases.

1. each 300 seconds started by the so-called Auto ABAP. The exact point of time depends on the time when the instance was started.
2. at each fifth logon at the instance.

Difference between Remote Client Copy and Client Export/Import

Brief explanation of difference between Remote client copy and client export/import

Remote Client Copy Method:

• Make sure there is no activity in source and target client
• Make sure enough space available on target system
• Suspend the background jobs, Tcode SE38, BTCTRANS1
• Create a system message SM02

Prerequisite for Remote client copy

• Create ABAP RFC connection from target to source client. Tcode SM59, Connection type 3

Steps:

1. Login into target client
2. 2.     Run transaction  SCC9 on target client, and enter the following:
   1. a. Selected profile:                        Choose the correct copy profile
   2. b. Source Destination:       Choose the RFC destination created in above steps
   3. c. System name and source client automatically filled after choosing the RFC connection
3. 3.     Run in background
4. 4.     Monitor the remote client copy logs in SCC3 and background job in SM37

Thanks

TREX CONFIGURATION

1. Create a user Trexadmin in CRM client and assign the role SAP_BC_TREX_ADMIN to this user  as per the sap note 766516
2. Check the following services are running    

3.   Select Trex Administrationoption in the above screen

4.  You can confirm the running services in the below screen through TREX administration tool

Landscape -> Services 

5.  Go to Landscape -> RFC

6.  Select Connection (highlighted in green color) button

                      Click ok

7.  Select RFC Destination (Sm59) button

            Save the RFC destination

8.   Now select the connection tool button in below screen

  9.  The connection is ok.  Ok is green

10. If you find any warning signal then select Repair All button. Warning is in Yellow.

11. When it is in warning click the Repair All button

12. Select   the connection to check if it all green as shown in the below screen.

13. RFC destination in the ABAP CRM system

14. The program ID will be generated in random by the TREX application

15. Login into the CRM system

16. Transaction Trexadmin

17. Enter TREX_DCM as the connection to RFC server

18. Execute

19. TREX Administration Screen

1.Executing only "niping" will show online help as below:

2.Performing niping self test:

3. Starting niping server on the host by cmd "niping -s"

4.Starting niping client from the front end by cmd " niping -c"

5.Connection test:

Connect / Ping OS Level

Check if the server is reachable, no data are written to the partner (Linux): niping -c -X9 -H <host> -s 3298

Connect / Ping Application Level

To check whether a NI base application can be reached, use the extra option –X1 which sends a NI_PONG

and expects a NI_PONG message (Linux): "niping -c -X1 -H <host>

Connect to Dispatcher

Sometimes the connection test with the Ping/Pong message is not sufficient, because it is not clear if the

dispatcher is running on the other side or another program. With the option –X6 a invalid message is sent to

the partner, the response will be checked against the expected error message from the dispatcher

(Linux): niping -c -X6 -H <host>

6.Other Tests

Hostname Lookup : niping -v -H <Host>

Service Name Lookup

Same as for Hostname Lookups (Linux): niping -v -H <host> -S sapmsEMR ;sapgw00 ;sapdp00

7.Local Interfaces

Print all interfaces which are handled as local by NI. This list of IP addresses is e.g. important for the

Gateway program (Linux):

SYSTEM COPY BY USING EXPORT-IMPORT METHOD

  1.1 Source System

   1.2 Run the sapinst.exe executable from installation master

   1.3Navigate to the above screen and Click on >>Next<<

1.4 Select “Typical” and Click on >>Next<<

1.5 Specify the profile directory i.e /usr/sap/<SID>/SYS/profile and Click on >>Next<<

1.6 Enter the password and Click on >>Next<<

1.7 Create the “New Folder” Name it Export

1.8 Specify the Export location and Click on >>Next<<

1.9 Select the database statistics and click on >>Revise<<

1.10 Select the radio button “Skip statistics update” and Click on >>Next<<

Click on >>OK<<

Export has been completed successfully in the Source System.

1.11 Copy this Export into the Target System

2.1TARGET SYSTEM

2.2 Navigate to the above screen and Click on >>Next<<

2.3 Select “Typical” and Click on >>Next<<

2.4 Specify the SAP SID <TST> and Click on >>Next<<

2.5 Specify the Master Password and Click on >>Next<<

2.6 Select the option “standard System Copy” and Click on >>Next<<

2.7 Specify the Database SID <TST> and Click on >>Next<<

2.8 Specify the Export path that we have copied from the source system and Click on >>Next<<

2.9 Specify Password of ‘DDIC’ in client 000 in the source system and Click on >>Next<<

2.10 Specify the Kernel path and oracle Client path and Click on >>Next<<

2.11 Specify the Solman Key and Click on >>Next<<

Target system installation has been completed successfully.

System Copy is Done Successfully using Export-Import Method.

2.12 Login to the System and Execute “SICK”

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on November 2013.

BC-CCM-MON*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

RZ20 for CPU_Virtualization_Power

- the CPU_Virtualization_Power subtree is in responsibility of the agent

- all other CPU_Virtualization_* nodes are in responsibility of saposcol

This means:

1) agent creates CPU_Virtualization_Power and is responsible for the content
2) fortunately - the data presented in the subnode are gained from saposcol and are reachable in other CPU_Virtualization_*   subtrees
3) agent does some kind of renaming in the nodes, e.g.  "Entitlement" could be found as "Guaranteed Capacity" in CPU_Virtualization_Virtual_System subtree

Summary - the values present in CPU_Virtualization_Power are collected by agent from other CPU_Virtualization_* subtrees, which are maintained by saposcol. It's kind of duplicity. The saposcol is always the originator of the data. There are no additional data in the _Power node which are not present in other virtualization subtrees.

At first in the beginning the EWA report only reported the standard CPU data for the physical server and the data for this is directly collected
by SAPOSCOL in a 24 hour buffer in which for each hour 4 times 60 measurements are stored because SAPOSCOL collects the data every 15
seconds by default.

This means that you can say that in the old EWA reports the OS CPU operating statistics are based on 4x60 is 240 measurements each hour.

After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power
is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need

the CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL

snapshot data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a

SAPCCM4X agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.

Installation and Configuration of SAPOSCOL:
http://help.sap.com/saphelp_nw70ehp1/helpdata/de/c4/3a6bff505211d189550000e829fbbd/content.htm

Operating System Collector SAPOSCOL:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/c4/3a6bff505211d189550000e829fbbd/frameset.htmk

1. sapcontrol -nr 00 -function GetVersionInfo

2. sapcontrol -nr 00 -function GetProcessList

3. sapcontrol -nr 00 -function J2EEGetProcessList

4. sapcontrol -nr 00 -function GetSystemInstanceList

5. sapcontrol -nr 00 -function ParameterValue SAPLOCALHOST

6. sapcontrol -nr 00 -function ParameterValue SAPPROFILE

Below are netstat to check the application which is listening to particular port :It will display in below format:

Format:

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

Example:

nestat -anp | grep 3298

Example:

netstat -anp | grep 3300

Example:

nestat -anp | grep 3200

SAP INSTALLATION ON VMware - PART 1

Installing Sap on vmware is same as we install on physical server. In this following document we are going to learn how to configure vmware, Installing Windows Server 2003 Enterprise Edition on vmware and then followed by sap installation in part 2 another documentation. I am using vmware workstation 9.0.

STAGE 1

Step 1.1

Click Create a New Virtual Machine.

Step 1.2

Select Custom mode and Click Next

Step 1.3

Select Workstation 9.0 from drop down list. Carefully see the limitation if you select older workstations.

Step 1.4

Select radio button for installing operating system later.

Here you need to have operating system DVD or you need to provide an ISO image of operating system

Step 1.5

Following are the operating systems which vmware supports in version 9.0

Select Microsoft Windows radio button and then select Windows Server 2003 Enterprise x64 Edition.

And Click Next.

Step 1.6

Remember here select the highest free space available drive because we are going to install sap.

Give Location and name of folder where you want to save vmware.

Step 1.7

Select Number of processors and Core Processors and click next

Step 1.8

Here we need to provide required RAM (Memory) for Virtual machine.

Keep in mind that even your base operating system requires RAM so don't give full or maximum memory to vmware. In this installation i have given only 4 GB Memory for vmware.

Step 1.9

Select Network address translation (NAT). Click Next.

Note: All this settings can be changed again even after installing operating system.

Step 1.10

Select LSI Logic and Click Next

Step 1.11

Select Create a New Virtual Disk and Click Next

Step 1.12

Select SCSI and Click Next

Step 1.13

Give required disk size depending on what you are going to install in this virtual machine.

Here i am going to install SAP Netweaver and i require 100 GB disk space.

Here i have given only 100 GB but it i will not allocate that entire 100 GB, If you want virtual disk to allocate disk space now then select the check box to allocate all disk space now.

Select virtual disk into multiple file. And click Next.

Step 1.14

Each file limit is 2 GB each, and will be created only if required. ( Because we have selected virtual disk into multiple files in before  step)

Step 1.15

Summary here you can change any settings. ( Remember we still didn't gave DVD or ISO image for Windows Server 2003 Enterprise Edition) Click Finish

Step 1.16

Here our Virtual Machine ( Hardware ) is ready.

Before clicking power on. Click edit and select CD/DVD and then browse and select ISO image of windows serve. Click OK.

Now Click Power on

STAGE 2

Step 1.17

Here you can see Virtual Machine is Booting.

Step 1.18

First Click on the blue screen then press enter to proceed with the windows installation.

To come out of that virtual machine into you base operating system press CTRL + ALT.

Step 1.19

Press F8 to agree and proceed with installation

Step 1.20

Select Un-partitioned  Space and press enter

Step 1.21

Create Required Size disk partition I had give full one drive partition. But you have to decide how many drives you want create.

Step 1.22

Select Partition to install. And Press Enter key

Step 1.23

Windows Server 2003 Enterprise Edition Installation is in Progress.

Step 1.24

Give a Computer Name and Administrator Password

Step 1.25

Select Typical Settings And Click Next

Step 1.26

Windows Server 2003 Enterprise Edition Installation is in Progress.

Step 1.27

Windows Server 2003 Enterprise Edition Completed And Re Starting Windows

Step 1.28

Note here you need to Press CTRL+ALT+INSERT for Virtual Machine

If you press CTRL+ALT+DEL then you will end up in task manager of your Base Operating System.

Step 1.29

Give User name as Administrator and Password

Step 1.30

Here in this image you can see both the operating systems. One is base operating system and other one is Guest ( Virtual Machine ) operating System.

Step 1.31

Install VMware Tools for Better Display and Sharing. This is Mandatory installation.

Goto VM on menu bar and click install Vmware Tool.

Step 1.32

VMware Tools installation Click Next

Step 1.33

Select Typical installation and click Next

Step 1.34

VMware Tool Installation Completed.

NOTE: When virtual machine is in running state and you want to change hardware setting please note virtual machine will Forced REBOOT.  It is Better to power off Virtual machine and then do changes in hardware settings and power on virtual machine.

In Part-2 Documentation (54 Screen snap shots) we will see Sharing of Resources with base operating system and Sap installation.

*********END OF DOCUMENTATION PART-1 ********

It is not uncommon that once BW QA gets refreshed or system copy from BW Prod, the source system connectivity to ERP system breaks. This document shows the step-by-step to restore BW QA to ERP QA.

ERP System:               ERP Quality System (QAS) client 100

BW QA System:          BW Quality System (Q11) client 100

Scenario:                    Source Systems QASCLNT100 is broken in txn RSA1 in BW QA (Q11) after it is refreshed from BW Production. This is a need to restore the connection for transport migration to work successfully.

Pre-requisite:

1. Open clients via txn SCC4, SE06 in ERP QA (QAS) and BW QA (Q11). If not, you will encounter dump DYNPRO_SEND_IN_BACKGROUND when trying to recreate the Source Systems in x11’s txn RSA1. (This step requires Basis authorization and should be done by Basis)

• Logon to ERP QA (QAS) , run txn SCC4 and open client for changes. Repeat for BW QA (Q11).

• In ERP QA (QAS) Run txn SE06, open namespaces so that there is no error when running FM RSAP_BIW_DISCONNECT later on. Repeat for BW QA (Q11).

2. In BW QA (Q11), go to txn WE20, check for ERP QA (QASCLNT100). If it does not exist, create it.If it exists, select the ERP QA's Partner Profile QASCLNT100 and delete RSRQST from outbound and RSINFO and RSSEND from inbound. Save your partner profile. It should look like the screen below.

3. Obtain ALE user-id passwords for to logon to QAS client 100 (ERP) and Q11 client 100 (BW) later on.

Step-by-Step Restore Procedure:

1. In BW QA (Q11), run txn SE11, table RSBASIDOC, narrow the results by putting in your ERP system id only e.g. QAS*

Result

2. In BW QA (Q11), run txn SE37, enter function module RSAP_BIW_DISCONNECT and client Test/Execute button.

This step deletes obsolete BW connections. Repeat this step for all entries in table RSBASIDOC.

Enter the values accordingly and click Generate button.

I_BIW_LOGSYS = BW QA system (Q11)

I_OLTP_LOGSYS = ERP QA system (QAS)

I_FORCE_DELETE = X

Caution: DO NOT enter a value in the field "RFC target sys". This would cause the function module to run in the system specified there!

Result

3. In BW QA (Q11), run txn RSA1 and Create Source System QASCLNT100.

With existing RFC destination and passwords, enter the fields like below:

You will be prompt to logon to QAS client 100. Click Continue button will do.

Click Use button if you are confident that the RFC destination works perfectly. If not, you could click Check button to confirm.

You might encounter a pop up message like this below. Click Delete will do. If this happens, after delete, repeat step 3 again.

4. With existing RFC destination and passwords, you should be able to create the Source System for ERP QA (QASCLNT100) without problem.

Problems that I encountered along the way……..

Problem 1:  DYNPRO_SEND_IN_BACKGROUND when trying to generate Source System QASCLNTxxx in txn RSA1

Solution:     Open clients in txn SE06 and SCC4 in both ERP QA and BW QA systems

Problem 2:  Entry in inbound table already exists

Solution:     

1. Go to WE20 and check whether Partner profile QASCLNT100 exist in LS type,if not just add Parnter profile with same and save.
   Partner profile Name: QASCLNT100
   TYPE: LS
   Give:
   Ty: US
   User: User Name
   Lang: EN
   and Save.
2. Again re-click on Partner Profile: QASCLNT100
   you will see ,there will be some entries in Inbound & out Bound Tabs.
   Delete the following from outbound:
   1.RSRQST
   Delete the following from inbound.
   1.RSINFO
   2.RSSEND
   and save your partner profile.
3. Now execute txn RSA1, it will ask to active Workbench, activate it and it should work.

Lastly, this document is only possible from the two reference below and many other related threads that I had also come cross so I would also like to give credits to them.

References:

OSS Note 886102 – System Landscape Copy for SAP Netweaver BW (Phase 6)

Transfer Structure Prefix error - http://scn.sap.com/thread/170753

The kernel will write the syslog messages which are stored in the SCSA to an OS file SLOG$$ on operating system level. These files are created in

an instance specific directory /usr/sap/<SID>/<INST>/log.

On Windows systems the SCSA is created by the kernel executables. You can use the transaction “ST02>Detailed analysis menu>Additional

functions: Storage>Shared memory details” to see if the SCSA area which belongs to ipc key 05 is correctly created for the ABAP instance.

Starting from 7.02 system release the central syslog sender and collector daemon are not used (supported) anymore (note 1565427). Also starting

from 7.02 the RFC function calls and RFC  communication is not used anymore for the Remote System Log functionality but is replaced by Web

Services methods and SOAP (Simple Object Access Protocol) communication (sending XML based on HTTP or HTTPS or SMTP or FTP). For this

new concept the dispatcher and dialog resources of the remote instance are not used anymore but this is replaced by the SAPSTARTSRV program

which is used to start the ABAP instance. In the SAPSTARTSRV program the Web Services method functionality is implemented and this

functionality can be used by using the SOAP communication protocol.

1508049 - Problems when writing the central system log

1550906 - Information about the system log files
1517379 - Which system log format does the 720 kernel write

Excerpt of note 1041390:
"
                   rslg/central/log/new
The following values are allowed:
0 = old version, that is RSLGCOLL/RSLGSEND
1 = HTTP
2 = HTTPS
If the new profile parameter is not available, the default is 1 (which is HTTP)."
In this system this is the case -> HTTP is set.

The Central syslog no longer work with the sender and collector. This concept was changed with kernel 720 and netweaver > 7.02.

For further information check the notes:

1041390 - SM21: Central system log via HTTP or HTTPS

1741743 - Central syslog as of Basis Release 7.02
1774185  - Welches Syslog-Format schreibt der 720 Kernel

This document explains how to rename an SAP system using the System Rename 1.0 tool, which is based on the installation tool.

System Rename 1.0 tool can be used for adapting:

SAP system ID

Host names

Database ID

Instance numbers of the instances on the SAP system

System Rename procedure is valid for ABAP, Java & Dual-stack (ABAP and Java) systems. Also you can perform the system rename on both central and distributed systems, however high availability & MCOD installation were still not supported till System Rename 1.0 SP03 (which I am using in this document).

Please read Note 1619720 - System Rename for SAP Systems based on SAP NetWeaver& SAP Guide for details.

System rename 1.0 media is available at http://service.sap.com/swdc

Unpack the System Rename archive with SAPCAR and Run sapinst.exe

Follow-up Activities

The follow-up activities for the system rename are identical with the follow-up activities for a system copy described in the system copy guide.

Also perform activities like Re-Configuring STMS, SLD & IGS RFC.

Reference :

http://scn.sap.com/docs/DOC-32851

http://scn.sap.com/docs/DOC-48330

This document contains and explains the jMeter configuration used to test a SAP SMTP service.

• The configuration of the service can be found here
• The telnet test case here and
• The jMeter test case here.

As the last blog describes a jMeter scenario, I am publishing here the example files used by jMeter. This should help everyone to create his/her own jMeter test.

Files

2 files are attached to this document:

• Input.txt
• SAP SMTP.jmx

Please not that you have to rename the file SAP SMTP.txt to SAP SMTP.jmx (thanks Jive) and to adjust the actual path of the SMTP sampler to make the test case work for you. After all, I am providing here an example, not a ready to use version.

Test plan

The test plan SAP SMTP.jmx consists of one thread group, one config element and one SMTP sampler. In JMeter it looks like this:

The test plan is parameterized. A file named input.txt contains the values for the parameters. The content of the file looks like:

Test Subject 1;lorem ipsum 1;

There are 3 columns, separated by ; Each column represents a value for a variable:

• Test Subject 1: Subject line
• Lorem ipsum: Message body
• 94: number for attachment to be included in the email

The variables are defined in the jMeter test. To read the values of the input.txt file, a CSV Data Set Config element is added to the test case.

3 variables are defined:

• Subject
• Message
• Number

The actual test case is defined in the SMTP sampler. This sampler contains the SAP SMTP server connection data:

• Server
• Port
• Mail from
• Mail to

These values are hard coded and have to be changed to match your actual environment.

The second configuration part of the test case is the actual message to be send and makes use of the previous defined parameters.

The subject line, the message body and the attachment are parameterized. That is where the input and variables are linked together. While the subject and message are fully defined by the parameter, the attachment expects a PDF file in the jMeter bin directory of the form message-${number}.pdf. You’ll have to make sure a PDF file with the name message-NN.pdf is there, while NN is a number like 01, 95, etc. The number value must match the entry in the input.txt file.

I found this option very useful. By just executing a Report, we can confirm files available in download basket without using MOPZ transaction.

1. Make sure you User ID & S-User are maintained in AISUSER (this is anyway required).

2. Execute Report /TMWFLOW/RMOBASKETAPPROVAL with SE38.

3. Now you get a new window where you can directly select and Confirm Files of your(S-User) Download Basket.

4. Download your Files

Thank you.

Hello All;

This document describes how to schedule a backup in SAP ERP 6.0 System and how to send it to your backup server.

It also shows you how to prepare, and setup your backup server in order to make it ready to accept, and save the backups which are sent by your SAP System.

The systems that are used:

1- SAP ERP 6.0 EHP 5 running on Windows Server 2008 R2

2- Oracle 11.g

3- Backup Server is a Windows Server 2008 R2 with 1 TB space with 4GB of RAM

Step 1:

DB13 - Schedule of Backups

Go to your SAP System, and run the transaction code "DB13"

In this transaction you schedule the start time for your backup, and the type of the backup.

The following backup types are offered based on the need:

1) Whole database offline + redo log backup (best option - it includes everything)

2) Whole database online backup

3) Whole database offline backup

4) Whole database online + redo log backup

5) Full database offline + redo log backup

6) Full database online backup

7) Full database offline backup

8) Full database online + redo log backup

9) Incremental offline + redo log backup

10) Incremental database offline backup

11) Incremental database online backup

12) Incremental online + redo log backup

13) Partial database offline backup

14) Partial database online backup

In our case we will schedule one Whole database offline + redo log backup every Saturday at 9:00 PM, and one Whole database online + redo log backup every day at 9:00 PM.

To schedule a backup do the following steps:

1) Go to DB13

2) Double click on the day you want to start a backup in

3) In the next screen double click on the database type which you want to start

4) In the next screen specify the exact time when to start the backup

5) No click on the tab recurrences

6) Now make it to be every Day at 9:00 PM except for Saturday. This is for our cas, but in your case you can choose your own scenario which you want to follow.

7) The schedule must look like the following:

Step2:

Background Configurations

The main work will be on the file "initSID.sap"

The location of this file is under D:\app\Administrator\product\11.2.0\dbhome_1\database

In our case it is located under the D drive.

There are three parameters which need to be changes in this file, and they are:

• Backup_dev_type = disk

#This is the storage type of the backup

• Backup_root_dir  =  \\Backup server IP \File name which will hold your backup

# This is the location of the torage for the backups

• Compress = brtools

Make sure that you have enough space on your backup server. For example if your backup size is 150GB make sure that your backup server has more than 150GB disk space on the drive that you are sending your backup to.

Also make sure that your backup server is able to see your SAP server. To double check this point ping your SAP server from your backup server, and then ping your backup server from your SAP server.

Step3:

Mapping the drive of your backup server to your SAP server

In your SAP Server right click on your computer icon --> Map Network Drive

In the next step you will be asked to provide the IP of your backup server then the drive where you want to send the backup to, then click finish.

Step 4:

Check if your backup was finished successfully

To check if your backup was finished successfully go to your SAP system and run DB12. Here you will know the status of your backup.

This concludes the document. Hope it was helpful

Best Regards

~Amal Aloun

Hello All;

In many cases you will need to activate, and define your http, https, and smtp ports. To do that you can check the following steps:

Run the t-code RZ10, and choose your profile, then click on extend maintenance, then click on change

2- Create the following four parameters:

To create the above parameters in RZ10 click on create button at the top of the screen.

In the next screen add the four parameters one by one with the value for each parameter.

Note that you can choose your own time out, and proc time our or you can go with the default values suggested by the system

After providing the parameter name and value click on save to save your changes.

Go back to the initial screen of RZ10, and click save:

You will prompt with a message that you need to restart your SAP service in order for your changes to be activated.

Click on Continue:

Now go and restart your SAP service.

Then go to SMICM transaction and click on edit --> service

If you did not define the HTTP, HTTPS, SMTP at the system yet then at the same screen you exist now click on service create.

After your three ports creation you should be able to see the following:

Now in order to activate the three ports in SMICM you need to run the t-code "STRUST"

On the left hand side of the screen right click on each file, and then choose create. after that you should be able to see a green color next to each one as you can see in the following screenshot:

Now go back to run the t-code "SMICM" --> Goto --> Services.

Click on the first one "HTTP" then Service --> Activate.

Click on the second one "SMTP" then Service --> Activate.

Click on the first one "HTTPS" then Service --> Activate.

Now you should be able to see a green check next to each port:

Hope this was helpful

Best Regards

~Amal Aloun

Following a list with descriptions of SAP Kernel executables:

Yours Faithfully

Juan de la Cruz Arellano Royo

12CODE - CEO

Dear All,

Today i am going to create my first Document on scn community.Hope this document will be helpful for SAP experts also.

Purpose of creation of document is to install certificate on IE browser.Yesterday i searched one discussion over scn sso certificate not installed windows 8.1   

For the solution i also searched lot over service marketplace & on search engines also and provided some solution but every time users getting same issue i.e

Use Automatically select the certificate store based on the type of certificate.

Choose Next to proceed.

Finally click on Finish to get

and dear friends now you can get certificate as like i got under certificates tab

After all these steps you all will be able to logon through IE ,without getting any ActiveX error .

Hope this document will help experts in future as a resolution for this type of issue with IE browser.

Thanks to all for encouraging me to write this document.

Best Regards,

Gaurav Rana