cancel
Showing results for 
Search instead for 
Did you mean: 

Error to execute Dtrace

Germano
Level 3
Partner Accredited

Hello guys,

I have a problem to execute a Dtrace in EV 10.0.4.

When I run the "monitor" or "log" command the following error appears:

ERR: {SharedMemorySink::initialiseMemoryObjs:#217}
Status: 80.070.005

I've reviewed all of the server's virtual memory configuration, VSA user permission and the VSA's TEMP folder permission.

Any idea what it could be?

I have several calls open and can not collect the logs because of this problem.

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

daveoflave
Level 4
Employee

As a reference for anyone who might have this issue in the future, we worked with Germano in EV support to resolve this issue.  As Chris Langevin mentioned above, it was indeed permissions-related. Specifically it seemd like the VSA didn't have access to the block of active memory that dtrace was running on, which doesn't make much sense.

   Our solution was to remove the VSA and the EV server from all GPO's by making exclusions for them both in each object.  We then forced a GPUpdate.  For good measure, we rebooted the server, though the GPUpdate should have sufficed.  After that the problem subsided.  I don't know the nature of all of the GPO rules pushed out in that organization, so I could not say what rule and on which GPO the problem originated from.

   Thanks for working with us on it, Germano!  I'll work on publishing something that this can be referenced to in the future. 

Thanks,
Daveoflave

View solution in original post

3 REPLIES 3

VirgilDobos
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi Germano,

Have you tried restarting the EV server and reattempt setting the dtrace?

--Virgil

ChrisLangevin
Level 6
Employee

Error 80070005 means Access Denied. I know I have seen this error before when running the dtrace as a user who is not the VSA (e.g., another type of admin assigned using RBA). It sounds like you might be having a similar problem.

If you need to know exactly what object on a computer you're being denied access to, Process Monitor is a great tool to use.

 

--Chris

daveoflave
Level 4
Employee

As a reference for anyone who might have this issue in the future, we worked with Germano in EV support to resolve this issue.  As Chris Langevin mentioned above, it was indeed permissions-related. Specifically it seemd like the VSA didn't have access to the block of active memory that dtrace was running on, which doesn't make much sense.

   Our solution was to remove the VSA and the EV server from all GPO's by making exclusions for them both in each object.  We then forced a GPUpdate.  For good measure, we rebooted the server, though the GPUpdate should have sufficed.  After that the problem subsided.  I don't know the nature of all of the GPO rules pushed out in that organization, so I could not say what rule and on which GPO the problem originated from.

   Thanks for working with us on it, Germano!  I'll work on publishing something that this can be referenced to in the future. 

Thanks,
Daveoflave