Warning: Could not open global shared memory

Question

Warning: Could not open global shared memory

Leo.Miller

SSChampion

Points: 13051
More actions
June 28, 2012 at 10:16 pm

#258216

Hi all,
Apparently this error was fixed in CU12 for SQL 2008, but it seems to have raised it's head again in SQL 2012.
[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.
I've got a client who is seeing it. but I've not seen a fix in CU1 or CU2 for 2012. Has anyone else seen this in 2012, and is there a fix around?
Cheers
Leo
Nothing in SQL Server is ever so complicated that with a bit of work can't be made more complicated!
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.

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

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

Robert Davis One Orange Chip Points: 28027 More actions · Answer 1

Contact PSS and let them know you are seeing this in SQL 2012 and request a hotfix.

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

SID_ SSC Enthusiast Points: 165 More actions · Answer 2

Hi,

I am seeing this as well.

Here is my test.

I have a package that uses 20+ data flows from oledb source database to oledb destination database. The databases source and destination are on the same sql server 2012.

Each data flow data from a source table to a destination table

The table properties are exactly the same from source to destination. There are no Foreign keys.....

Everything work fines except 2 data flows both returning

"[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.

"

The data does not get copied for the problematic tables this is although just a warming.

When I Save my package and Open it again. The Source and Destination OLDB components

on the problematic data flows are no longer available in the package.

Also, I get the same warning when I use the Import Wizard but the data get copied OK.

Saving the Import wizard package did not help. As I get package corrupted when i try to open the package.

Has any one seen this type of errors?

JudithK SSC Veteran Points: 286 More actions · Answer 3

I concur with Robert that this should be raised with PSS...

Previously Kaushik posted on his blog the work-around for 2008, perhaps this will also work with 2012?

http://saveadba.blogspot.co.uk/2012/02/could-not-open-global-shared-memory-to.html

seddy2765 SSC Enthusiast Points: 106 More actions · Answer 4

This isn't Microsoft's fix but it gave me what I really needed - to verify if a (simple data transform - sql query to flat file) task completed successfully. To do this, follow exactly what the message states ... "or on the system's console". [The admin resolution required too many hands in the pot when all I needed was verification of results].

'or on the system's console':

IE, from VS menu - do not run 'Debug>Start Debugging' but run 'Debug>Start Without Debugging'. This will open the 'console' (ala, command window). The execution results will echo to the screen. Navigate/explore expected results. Mine were where expected and data was as expected.