Hi Team,
Our company has one main Production instance and two application instances for load balancing.
However we restarted our both application servers without restarting the main PRD Server but from that time our application servers are not starting.
I even raised the instance to SAP an i got the below response.I am not able to move forwardPleae help and can someone tell what is the centrally shared SAP run directory?? is it \usr\SAP or anything else.Please go through the reply that i have pasted below and help.
Our main PRD Server is: MIGPRD and application servers are MIGPRDAPP1 and MIGPRDAPP2.
analyzing D13 and D14 start-up problems is complcated, these two
instances are not correctly configured,
we can clearly see that the SAP services and SAP kernel configuration
was not done as the " SAP ERP 6.0/Windows" Installation recommend.
It took me long time to find out thta the root cause is a problem with
sapcpe.
You can see it red marked (sapcpe cannot be started!) in SAPmmc.
- ------------------------------------ -
What is sapcpe.exe?
"In a homogenous SAP system distributed across multiple hosts,
all files and Kernel executables from the physically shared
directories under \usr\sap (Windows) are distributed across the
remaining instances by sapcpe by default.
SAPCPE program set up to copy SAP executables from globally-shared to
local directories.
SAPCPE is used to install and maintain up-to-date copies of SAP
executables locally on a particular host system for a particular SAP
instance. In the documented usage, SAPCPE is set up to start
automatically when an instance is started. The user is advised to
rename the central shared SAP "run" directory to "ctrun" and to create
an empty local "run" directory.
The first time that SAPCPE starts, it copies required SAP executables
from the central executables directory ("ctrun") to the local "run"
directory in host system.
After SAPCPE has run the first time, then the server is started as
normally and runs with the newly copied local executables. In
subsequent instance starts, SAPCPE makes sure that the executables in
the local run directory are up to date.
- ----------------------------------- -
If we try to start-up D13 and we check the D13 sapstart.log we can
read the following:
-
------------------------------------------------------------------------- -
SAP-R/3-Startup Program
Starting at 2015/07/07 19:51:52
Startup Profile: "D:\usr\sap\MIP\SYS\profile\MIP_D13_MIGPRDAPP1"
Starting Programs
(2868)
CreateProcess(\\MIGPRD\sapmnt\MIP\SYS\exe\uc\NTAMD64\sapcpe.EXEpf=\\MIGPRD\sapmnt\MIP\SYS\profile\MIP_D13_MIGPRDAPP1) failed(5). EIO*:
Input/output error OR: Access is denied.
(2868)
CreateProcess(\\MIGPRD\sapmnt\MIP\SYS\exe\uc\NTAMD64\sapcpe.EXEpf=\\MIGPRD\sapmnt\MIP\SYS\profile\MIP_D13_MIGPRDAPP1
list:\\MIGPRD\sapmnt\MIP\SYS\global/syb/NTAMD64/cpe_sybjdbc.lst
source:\\MIGPRD\sapmnt\MIP\SYS\global/syb/NTAMD64) failed(5). EIO*:
Input/output error OR: Access is denied.
.
. .
-
------------------------------------------------------------------------- -
The problem with sapcpe occurs beacuse of the failed access to the
shared disk, as it is shown in sapstart.log :
(2868) CreateProcess(\\MIGPRD\sapmnt\MIP\SYS\exe\uc\NTAMD64\sapcpe.EXEpf=\\MIGPRD\sapmnt\MIP\SYS\profile\MIP_D13_MIGPRDAPP1) failed(5).
EIO*: Input/output error OR: Access is denied
Please involve your Basis and Windows team,
make sure that \\MIGPRD\sapmnt\MIP\SYS\exe\uc\NTAMD64\sapcpe.EXE is
accessible by SAPservice<SID> user and from/to MIGPRDAPP1 server.
Once the sapcpe can be started, D13 will successfully start up.
(Please check this on D14 as well).