Import Warning Message

Discussion:

(too old to reply)

Med

2009-07-08 00:23:56 UTC

Hi,

My Source DB is on a hosted remote sql server 2005. I created an exact
database on my local SQL 2008 Developer. I use SSIS to import data from
remote SQL 2005 to local DB (SQL 2008 Dev) , which deletes rows in
destination tables and allows Identity Insert. As far as I can see, all
rows of all tables are imported, but I also get the following Warning:

Warning 0x80049304: Data Flow Task 1: 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 googled this problem, but couldn't find any useful answer. I also
thought this might be permission issue and I used my local sa login, but
still got the warning.

Does anyone know what is causing this warning?

Kind Regards

Med

Todd C

2009-07-08 12:42:02 UTC

Permalink

This is just a hunch, but take a look at your local SQL Server Configuration
manager. Under the SQL Server Network Configuration node, for the local
instance (may be more than one instance on your machine, like a SQL Express
install) check the status of each Protocol. Is Shared Memory enabled? Check
the same for your SQL Native Client 10.0 COnfiguration.

HTH
=====
Todd C

Post by Med
Hi,
My Source DB is on a hosted remote sql server 2005. I created an exact
database on my local SQL 2008 Developer. I use SSIS to import data from
remote SQL 2005 to local DB (SQL 2008 Dev) , which deletes rows in
destination tables and allows Identity Insert. As far as I can see, all
Warning 0x80049304: Data Flow Task 1: 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 googled this problem, but couldn't find any useful answer. I also
thought this might be permission issue and I used my local sa login, but
still got the warning.
Does anyone know what is causing this warning?
Kind Regards
Med

Med

2009-07-08 14:05:57 UTC

Permalink

Hi Todd,

Thanks for replying. I only have one instance of SQL 2008 Dev.I checked and
by default "Shared Memory" were enabled for all.

Regards

Med

Post by Todd C
This is just a hunch, but take a look at your local SQL Server
Configuration
manager. Under the SQL Server Network Configuration node, for the local
instance (may be more than one instance on your machine, like a SQL Express
install) check the status of each Protocol. Is Shared Memory enabled? Check
the same for your SQL Native Client 10.0 COnfiguration.
HTH
=====
Todd C

Andrew

2009-07-30 05:00:01 UTC

Permalink

Hi Med,

I had the same problem when I set up a proxy account to use the ssis service
through the SQL server agent.

I deleted the proxy account and it seemed to work fine for running a
straight import
I re-created the proxy account and

Regards,

Andrew