Unanswered Unanswered SSIS Posts “Could not open global shared memory . . .”

Question

Unanswered Unanswered SSIS Posts “Could not open global shared memory . . .”

wrlucas

SSC Veteran

Points: 298
More actions
December 6, 2009 at 9:23 am

#228393

There are several posts concerning the below issue dating back to April of 2009. Why has no one replied. Is there no solution?
[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.

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

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

RBarryYoung SSC Guru Points: 143329 More actions · Answer 1

Not necessarily. It just means that none of us answering happen to know the answer.

[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung [font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]

wrlucas SSC Veteran Points: 298 More actions · Answer 2

Well I guess I am going to have to spend the money and contact Microsoft Support on this one.

Thanks for the reply.

wrlucas SSC Veteran Points: 298 More actions · Answer 3

Here is a follow up for others who experience this problem:

The quote below is from Microsoft Support replying to my email stating that changing from a SQLDB data destination to an OLEDB destination worked.

"Yes, according to the defect description, OLE DB should work, the warning only says that the package does not have access to the SSIS related perfmon counters.

I was able to reproduce the failure in almost all environments (All OS versions with UAC ON i.e. Windows Vista and above). The defect documentation also says that this error should happen if the executing User does not have SeCreateGlobalPrivilege on Windows. User-mode applications represent this privilege as the following user-right string: “Create Global Objects” and I remember we already granted that. So this might be a regression, I am going to pursue this with Product Group to see if there is/would be a fix available to this otherwise it might limit Sql Server Destination task to a great extent.

As of now, it seems the only work around without any security breach is to switch to the OLE DB Destination component."

WRL

KoldCoffee SSCoach Points: 18971 More actions · Answer 4

My destination is already an OLE DB.

RECAP of whan I started to get this error:

I started to get this error after adding a Script task to my Control Flow. I added a "MessageBox.Show("Script Task ran!"); to the public void Main() section of the MS Visual C# script task.

RECAP of error:

"[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 am on a laptop that I have installed BIDS onto, and I am a secondary administrator of the machine. I believe this error has to do with permissions, but I don't know which permissions specifically I need to obtain to get around the error you have been discussing here. Does anyone know which permissions I need to give myself, or what modification I can make, so that I can execute MS visual c# code in script task?