EventID: SAP_TRIGGER_RDDIMPDP

 Error below in stms > Import overview > SAP system > Go To > TP system log
Trace File of External Event Raiser (Level=2, Append=0)
EventID: SAP_TRIGGER_RDDIMPDP
*** ERROR ***: Cannot determine mshost

3. Error below in the AL11 > DIR_HOME > dev_evt file log
EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: [SAP Server]
SAP message server service (new): 39XX [XX=message number]
SAP message server service (old): sapms[SID]
Event sent to server [SAP Server]

Cause: Problems with transport process and involved parameters and components

Solution: 

1.0 Review SAP notes 642464 & 449270. Check if transport parameters are set correctly in the default profile DEFAULT.PFL. 

This can be found in \usr\sap\[SID]\SYS\profile\DEFAULT.PFL

Add following parameter in your DEFAULT.PFL

SAPSYSTEM = [nn](this is the system number)
rdisp/msserv = sapms[SID]

2.0 Add the correction parameter [SID]/system_pf to transport profile.

As suggested in SAP note 449270 please add following parameter in
transport profile(TP_DOMAIN_[SID].PFL)

- there should be entry for [SID]/system_pf

Maintain the transport profile parameter [SID]/system_pf. Your
transport profile will be TP_DOMAIN_[SID].PFL is located in
DIR_TRANS/bin. The system_pf parameter should be the path to the
DEFAULT.PFL for that SID. Example:

A11/system_pf=d:\usr\sap\A11\SYS\profile\DEFAULT.PFL
B12/system_pf=/usr/sap/trans/bin/DEFAULT.B12

Both are valid paths, assuming that the profiles are maintained.

Please make sure after you make an entry in the transport profile end
this with a enter and then save otherwise the entry will not be read
properly.

3.0 Verify services file 

Check if sapmsSID port is open. 

Go to C:\WINDOWS\system32\drivers\etc for Windows.

Check the services file for the sapms[SID] entry. This entry
should have the format:
sapms[SID] 3600/tcp > Note that last 2 digits is your SAP system number
If your entry looks like this:
sapms[SID]###3600/tcp
The '#' marks indicate the beginning of a comment, and all text after
this will be ignored. Remove them or duplicate the entry without the
comment marks.

4.0 Make sure that hosts file of all the systems are having specific
entries for all the systems in the landscape.

Go to C:\WINDOWS\system32\drivers\hosts

Verify if working by doing a network ping.

5.0 Restart the SAP instance after these changes and then try the imp

Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL

Symptom

SSO between a AS Java and AS Abap system fails. Looking at the traces on the abap side (SM50) we see the following error:

"Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL "

Problem

The cause of the problem is that the ticket accepting system does not recognise the issuer of the Login Ticket.

Solution

The soloution is to run the SSO2 wizard again, export the certificates and reimport them to the Ticket accepting system

SAPCAR: format error in header

Common Error in SAPCARSAPCAR terminates when you process a SAR archive with the following
error messages:
non-unicode SAPCAR: format error in header
unicode SAPCAR: Illegal byte sequence

Solution :

Either use SAPCAR 700 or download the latest SAPCAR 640 patch from SAP Service Marketplace at 

http://service.sap.com/patches -> Support Packages and Patches -> Entry by Application Group -> Additional Components -> SAPCAR

Hardware Migration

Prerequisites

· Download required software and patches from service market place

· Compare filesystem space with source system database

· Set page memory

Actions on Target server

· Install Oracle RDBMS software

· Apply RDBMS patch to the source patch level

· Install SAP NW2004 with ABAP content

· Install Java add in on ABAP

· Request and Install SAP license for new hardware

· Start J2EE on new server

· Upgrade Kernel to the source patch level

· Take full backup of database

· Take java filesystem backup

· Bring down target server along with DB

· Stop all the services related to oracle and SAP

· Delete data from sapdatas , origlogs and mirrlogs in target system

Actions on source server

· Request Downtime for source server

· Suspend jobs using report btctrns1 in source server

· Bring down application along with DB in source server

· Stop all services related to Oracle and SAP in source server

· Start zipping of sapdatas, origlogs and mirrorlogs

· Zip J2EE filesystem j2EE,SCS, SYS folders.

· Copy the zipped data manually via Wan to target server

Actions on target server

· Unzip the zipped files and place or overwrite them according to the structure

· Change hostname in ABAP according to SAP note 8307

· Change hostname in RZ70

· Change hostname in j2ee config tool according to SAP note 757692

· Start DB,

· Delete source ops$ users and recreate for target server and change the password

· Start SAP and J2EE

· Re Install SAP license

· Reconfigure SMLG,RZ10,RZ04,RZ12, DB13 etc.. accordingly

· Check RFC connections and reconfigure if required

· Reconfigure STMS

· Reconfigure SLD and JCO destinations using visual admin tool.

· Restart cluster for changes to be affected

· Check SLD and portal

· In SLD change hostname in profile and server settings if required

· Reschedule jobs using report btctrns2

· Configure backup strategy

· Take full database backup along with J2EE filesystem.

Register a program on SAP Gateway

RFC connection test in SM59 might give error similar to this

———————————————————————————————————

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: program not registered

Error Details LOCATION: SAP-Gateway on host / sapgw

Error Details DETAIL: TP not registered

Error Details COMPONENT: SAP-Gateway

Error Details COUNTER: 16793

Error Details MODULE: gwr3cpic.c

Error Details LINE: 1694

Error Details RETURN CODE: 679

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Mon APR 17 13:08:02 2009

Error Details VERSION: 2

———————————————————————————————————

The program in the above error should be registered in the gateway for this connection test to complete successfully. The server program rfcexec is responsible for its registration on the gateway.

To register the program login into the OS level as sudo su - adm and execute the following command.

rfcexec –g -a -x 

rfcexec is the server program name, the can be obtained from SM59, it is case sensitive and should match with the entry in SM59. Theand can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.

The connection will fail once this command is terminated or the user executing this command logs off

To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini

To do this, execute the following command

sudo su - adm

rfcexec –D

is the RFC destination name in SM59

So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.

In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered)

There can be many reasons due to which we might get this error saying server program is not registered, once such instance which I faced was where in the TREX server, a new RFC destination was defined, the TREX server creates a new program id each time this RFC destination is defined. This program id was not changed in TCP/IP connection is SM59 which was the reason why the destination was failing

SAPPFPAR : tools

SAP kernel has a little part called sappfpar. This little program is used to check whether your SAP profile has already well configured or not. It will suggest gave you a suggestion if there are any of your set parameter on SAP profile is not fit or not good enough.

To run this command, you need to log on as adm user. 

Syntax :

adm$sappfpar check pf=/directory_where_profile_reside/profile_to_check

Here are the sample :


host:adm 6> sappfpar check pf=/sapmnt//profile/_DVEBMGS10_host