April 8, 2009 at 5:27 am
Hi
I'm busy rewriting DTS packages as SSIS packages. As and when I finish a package I run it in debug mode via Microsoft Visual Studio and then examine the Exection Results to see the messages generated.
Now it may or may not matter how I run the package but the following warning has been generated :-
[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'm one of these people who likes to run programs and get no warnings at all (if it can be helped).
Can someone kindly explain what it means and if I can can get rid of it?
August 16, 2009 at 11:27 pm
I am getting this warning too. Did you ever find out what was causing it?
December 6, 2009 at 9:11 am
I have this same problem and do not understand why this issue has not been answered?
Can someone please help with this?
By the way when I run BID or SSMS as administrator, I can execute my SSIS package. When I don't I get the same error and the package fails. My package is a simple read an Excel File --> Data Conversion --> Sql Server table.
Why would any SSIS package require running as administrator especially since I authored this package using BID on the server that the package is supposed to run on (Windows 2008 x64).
December 6, 2009 at 11:30 am
Sorry, I never did find out! People at my work don't know and never found a solution on th einternet.
December 8, 2009 at 2:34 pm
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
January 25, 2011 at 6:46 am
Thanks for this post. It solved my SSIS-problem. I changed destination to OLEDB type and the error disappeared.
January 31, 2011 at 7:47 pm
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?
July 28, 2011 at 12:44 am
Hi there,
I facing same issue too, anyone of you had solve it?
My SQL version is SQL 2008 R2, SSIS task i create is import multiple worksheets excel into SQL table.
The SSIS run till worksheets no. 12 and stop.
I see at the execution results tab, there got warning message on global shared memory.
In the SSIS package has a script task to check valid worksheets name, if valid then just load to table.
Thanks.
November 2, 2011 at 3:56 pm
My destination already is OLE DB... has anyone found a solution?
I am running this under SQL 2006 Standard, SP2, on a Windows 2008 Server Enterprise - 64-bit
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
November 8, 2011 at 12:49 pm
In case people are looking for a solution to this still, the one thing I did find is that when I received this error, I right clicked on the my SSIS solution name, went to properties, clicked on debugging and changed my value of Run64BitRunTime to True. This seemed to fix the problem and removed the error I was receiving in my execution results.
Hopefully this helps 🙂
November 16, 2011 at 8:05 pm
The MSDN solution for the above reported warning is:
December 1, 2011 at 3:53 am
I had this same problem with this error message of :
[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 have a Dataflow task with datasources Excel and it has been working for months but suddenly it started given this above error.
I worked on it for a whole day no luck trying all technical troubleshooting all to no avail then the second day i decide to go elementary by checking the name on the sheet of the excel and to my surprise the 'The name of the excel sheet' in the Exec Source is the problem, though it looks like the same name in the excel sheet when i opened the excel sheet up on desktop.
Solution: I opened the old successful file (the name on the excel sheet is the same as the one showing in the Excel Source Task), Copy the OLD name of the excel sheet file and paste it on the new file that has not been processed to over write the excel sheet name and it worked.
Future guide: I explained to the analyst that generates and safe the Excel file to be more aware of the name they save it with to always be the same as in the past.
Temmy George
Collaboration yields better solution very quickly
with little input from each individual.
Don't just take...add to it too...
December 9, 2011 at 7:00 am
Hello,
In BIDS, when I execute package I also noticed the warning :
[SSIS.Pipeline] Warning: Warning: Could not open global shared memory[...]run this package as an administrator, or on the system's console.
Workaround : right clic BIDS select Run As Administrator, even if the current user is in Administrators group on local computer :crazy:
a+, =)
-=Clement=-
Configuration :
Windows 7 Professional Service Pack 1 x86
UAC level : max (Always Notify)
Microsoft SQL Server 2008 r2 Service Pack 1 (v10.50.2500.0)
December 9, 2011 at 12:04 pm
I receive the same warning. I already have my project set to run 64-bit and I get the warning anyway.
December 9, 2011 at 12:13 pm
Okay, I went to the Microsoft support link listed above. Does this solution apply to SSIS packages that are NOT running on Windows XP? Also, I believe we have already installed the latest service packs. Finally, we get this error whether the package is running in BIDS or has been deployed to the SSIS package store in SQL Server. Does anyone know of any other potential solutions?
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply