Basis Errors and Solutions

Symptom

You cannot activate the Virtual Machine Container (VMC) on Windows platforms. In the dev_w* trace files, errors are visible in the Es2 memory layer:
X *** ERROR => Es2WinPreCreateFind: Window JAVA_SHARED created with
different parameters [es2xx.c 1988]
X *** ERROR => Es2WinCreate: Window has different address as precreated
window [es2xx.c 2189]
X *** ERROR => Eg2CtxCreate: Es2WinCreate failed [eg2xx.c 752]
M *** ERROR => DpEmInit: Eg2HeapCtxCreate (2) [dpxxdisp.c 10297]
M *** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 10154]
M *** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

Other terms

VMC, SM52
Reason and Prerequisites

In rare cases, the memory window for the VMC memory management cannot be created at the same address in all work processes. This is usually because of a reloaded DLL, which moves the memory windows in the address area. The VMC is not operational as a result.
Such problems often occur in connection with database backups.

Solution

You can use a profile parameter to move the VMC memory window to an address area that is not used by other applications. The largest possible address is determined and the system searchs downwards from there for an available address area. The address area that can be used by applications currently consists of approximately 8TB. The addresses that the system uses intensively are those between:
0×00000000000 – 0×00200000000
0×7FE00000000 – 0×7FFFFFFFFFF
Using the following profile parameter
vmcj/winAdr = 0×70000000000
For the VMC, the system uses only memory addresses below 0×70000000000.
You obtain the exact memory use by using the command:
sapntkill.exe -MEM where is a valid PID of an SAP work process. This command creates a file with the name adrscp_* in the work directory of the instance with the current memory use.
You can use the profile parameter as of the kernel
Release 7.00 patch level 205
Release 7.10 Patch level 152
As of Release 7.01 or 7.11, the error no longer occurs.