Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Warning: Could not open global shared memory to communicate with performance DLL Expand / Collapse
Author
Message
Posted Tuesday, March 20, 2012 4:47 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 7:06 AM
Points: 4,196, Visits: 4,268
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/

Post #1269931
Posted Tuesday, March 20, 2012 5:19 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 8:23 PM
Points: 367, Visits: 822
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.
Post #1269945
Posted Tuesday, March 20, 2012 5:29 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 7:06 AM
Points: 4,196, Visits: 4,268
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/

Post #1269951
Posted Wednesday, November 14, 2012 1:20 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, August 1, 2014 9:03 AM
Points: 27, Visits: 25
did you ever resolve this issue? I'm experiencing the same issue.

Thanks

Brian
Post #1384833
Posted Thursday, November 15, 2012 7:14 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 7:06 AM
Points: 4,196, Visits: 4,268
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/

Post #1385145
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse