cancel
Showing results for 
Search instead for 
Did you mean: 

Shared Memory Ceation error when we install NW04S Java Stack.

Former Member
0 Kudos

Hi.

I trying to install NW04S Java Stack in Windows 2003/ MS SQL but We got error to starting enqueue service for Java WAS.

Error is

[Thr 4364] Sun Mar 12 23:13:34 2006

[Thr 4364] *** ERROR => ShmDelete: Invalid shared memory Key=34. [shmnt.c 719]

[Thr 4364] *** ERROR => ShmCleanup: ShmDelete failed for Key:34. [shmnt.c 793]

[Thr 4364] initialize_global: enqueue server without replication

[Thr 4364] Enqueue: EnqMemStartupAction Utc=1142172814

[Thr 4364] *** ERROR => [CreateOsShm] CreateFileMapping(37,36 KB) failed with Err=5

ERROR_ACCESS_DENIED: Access is denied. [shmnt.c 2174]

[Thr 4364] *** ERROR => ShmCreate: Create (37,37664,1) failed [shmnt.c 506]

Anyone have idea for fixing this problem ?

Reagrds, Arnold.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Arnold,

Kindly check if the User SAPService<SID> is a member of

the local administrator group. If not add manually and

try again.

Hope it helps.

Regards

Srikishan

Former Member
0 Kudos

Hi Srikishan.

I checked member but User SAPService<SID> is aready a member of the local administrator group.

Is there anything to check ?

Regards, Arnold.

Former Member
0 Kudos

Hi Arnold,

Could you also check if the SAPService<SID> has "full

access" control over the ..\usr\sap\<SID> directory in the

directory security properties. If not grant them and

retry.

Regards

Srikishan

Former Member
0 Kudos

Note 82751 may also help. Granting access should solve

the problem.

Regards

Srikishan

Former Member
0 Kudos

Hi Srikishan ,

today I had the same problem (W2003/MSSQL2005) and your suggest really worked!

Thanks

Giovanni Lippolis

Former Member
0 Kudos

hi giovanni..... u said u were able to fix this issue...

what exactly did u do ?

0 Kudos

I have the same issue.

I checked all permissions on saplog and sapmnt, and did a general check on the user. I saw nothing wrong.

I temporarily solved the problem registering the service via sapstartsrv with the SAP local admin (sidadm) instead of SAPServicesid.