Warning: Could not open global shared memory to communicate with performance DLL

Question

Post reply

Warning: Could not open global shared memory to communicate with performance DLL

Welsh Corgi

SSC Guru

Points: 116520
More actions
March 20, 2012 at 4:47 pm

#149865

I'm a Local Admin on this Database Server but I get the following warning?
[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Any ideas?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

sam.dahl Hall of Fame Points: 3112 More actions · Answer 1

I get this error on one particular client site.

Google has plenty of suggestions, but given that we were not impacted by the error we never bothered resolving it.

To quote Todd McDermid here:

http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/d3c33c35-8c94-457d-9031-7b19803080d0

This is only a warning.
SSIS packages attempt to update performance counters on the machine they are executing on. But write access to those performance counters is restricted in order to prevent malicious use. Typically, packages are not executed with administrative priviliges, which are the default access level for writing to those counters.
To resolve, you can:
Ignore the message. You probably aren't monitoring those counters anyway.
Give the account your packages are executing under permission to update those performance counters.
Change the account your packages are executing under to grant them admin privileges.
I'd recommend #1 unless you need those counters.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

Ok, Thanks.:-)

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

brian.geregach SSC-Addicted Points: 406 More actions · Answer 3

did you ever resolve this issue? I'm experiencing the same issue.

Thanks

Brian

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 4

I was not able to resolve the issue.

It is not a permission issue.

I'm ignoring the message.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/