on 04-08-2009 6:46 AM
Hi:
We have installed SAP NW 7.0 on Windows 2003 64bit environment with Microsoft Cluster architecture. As per new cluster architecture, we have installed our app server locally on Node A and Node B whereas ASCS is running on cluster with system number 01 on Node A. Database is running on Cluster too on Node B.
App server CI (Node A) and DB (Node B) are installed with system number 00 and ASCS is installed with system number 01.
We are trying to setup STMS with virtual host name of ASCS with system number 01 but it doesn't accept it. As per our understanding, it is supposed to use virtual hostname (ASCS) and through message server it should do load balancing. If we use application server hostname with system number 00 it works but than we will have SPOF.
Please help.
Thanks,
After applying logon load balancing, we started getting following error.
WARNING: System PIP. Warning. 20090413141440 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PIP
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System PIP. Warning. 20090413141540 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System PIP. Warning. 20090413141551 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PIP
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System PIP. Warning. 20090413141723 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PIP
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
START tp_getprots PIP P 20090413141723 VORAM SAPPIPDB 20090413141422661
WARNING: System PIP. Warning. 20090413141840 :
ERROR: The following call returned with exit code 7:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PIP
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
Thanks,
Miral.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Miral,
check in the file dev_evt. If you find an error message like this one : cannot determine ms server; then create a system profile for your HA system in a shared directory like
<SAPTRANSHOST>\sapmnt\trans
This file should have the following content
# This profile is needed to be able to trigger sapevents during transports
# DO NOT DELETE IT
rdisp/mshost = <virtual ASCS host name>
rdisp/msserv_internal = 39<instance number>
SAPSYSTEM = <instance number>
Name the file like DEFAULT.<SID>
Then, start the transaction STMS in client 000 of your TMS domain controller
Click on the Systems button. Select the HA system.
Go to tab Transport Tool and add the parameter SYSTEM_PF =
<SAPTRANSHOST>\sapmnt\trans\DEFAULT.<SID>
After these steps, events should be triggered again in your HA SAP installation.
Seb
Hi Miral,
I know the problem is already solved by other means, but you could have solved the issue by other means...
As your CI and DI has the same instance number and they are running locally on each cluster node you could have defined STMS with virtual ASCS hostname but, instead of ASCS system number, with CI (or DI) system number. This is to say, instead of ASCS:01 you could have defined with ASCS:00.
Regards,
Nuno Raposo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Miral,
In High Avalability/MSCS SAP environment STMS requires an excellent dialog-supporting server as a communication partner for each system. This is usually the central instance.
Please apply the following Snote and correction instruction in into all systems of the TMS landscape. You must at least implement the corrections in the TMS domain controller and in the HA systems. In this case, you must manually create the 'TMS_MGR_LOADBALANCING' report.
This report allows you to activate or deactivate load balancing for communication with TMS targets. The default user group 'SPACE' is used as a target group.
Note 943334 - TMS setup in high availability systems
Regards
Rayees Palot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.