Hello,

I am trying to set up my first sql 2005 Integrations Services package and am
having a problem. My package is set up to:

1.) Run two separate SQL queries to clear some SQL 2005 data tables.
2.) Run a data flow which copies data from an Microsoft Office Access
database on a network drive, to one of the cleared tables from #1 above.

For some reason when I run the data flow I receive the following errrors:

[SQL Server Destination [208]] Error: An OLE DB error has occurred. Error
code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL
Native Client" Hresult: 0x80040E14 Description: "Could not bulk load
because SSIS file mapping object 'Global\DTSQLIMPORT ' could not
be opened. Operating system error code 2(The system cannot find the file
specified.). Make sure you are accessing a local server via Windows
security.".

[SQL Server Destination [208]] Error: Unable to prepare the SSIS bulk insert
for data insertion.

[DTS.Pipeline] Error: component "SQL Server Destination" (208) failed the
pre-execute phase and returned error code 0xC0202071.

I cannot figure out what is going wrong! If I simply do a manual import via
the SQL Server Management Studio everything works fine, and everthing is
imported correctly.

Is this because I am clearing the table in an SQL query, and then accessing
the table again in the dataflow?

Thanks for any help!

Jim

Hi

I encounter exactly the same problem when running a package (with a similar
functionality) in debug mode on my client pc. BUT when running the same
package in debug mode on the server it runs sucessfully.
In my experience this type of error is related to some kind of security
issue, but if this is the case here I don't know...

If anybody can give us any insight to this problem that would be greatly
appreciated.

TIA,
Rune

"Jim" wrote:

I also encountered the problem - until I changed my destination data
object
to an OLE DB Destination object. I WAS using a SQL Server Destination
object - might be native, and can only run on the server?

At any rate, the above change solved the problem.

-Doug

Rune O. wrote:

SQL Server Destination adapter only works on the same box as you are running SSIS. This adapater is a SQL Native for high performance loading but, carries that limitation with it. If you are running remotely, change to the OLE DB Destination adapter.

HTH,
SK