June 15, 2008 at 10:58 pm
Hi All,
Following is the Error message ia m getting after executing BULK INSERT TASK
[highlight=#ffff11][Bulk Insert Task] Error: An error occurred with the following error message: "Cannot bulk load because the file "C:\Documents and Settings\pavan.sunkara\Desktop\Audit Destination.txt" could not be opened. Operating system error code 3(The system cannot find the path specified.).". [/highlight]
In source i am selecting flat file and what ever the columns i found in Source i am creating empty table with the columns in the source, when i execute the package i am getting ht e above said error,
kindly provide me solution for this
June 17, 2008 at 7:03 am
What machine are you running the package from? I think you have to be on the server to use bulk insert in SSIS. That's how I got it to work, but i did not use a bulk insert, I just used a dataflow with a sql server destination.
June 17, 2008 at 7:18 am
Try by keeping the file on C: not something like a desktop
June 17, 2008 at 7:21 am
are you pointing to the correct machine? it should be something line \\machinesource\dirive\folder\file\import.txt
there should also be a map layout of your file on the ssis package.
hope this helps.
"We never plan to Fail, We just fail to plan":)
June 25, 2008 at 11:28 am
there are several approches to this. make sure that the folder is a share folder and that the file does exist(no spelling horrors!).
second make you have the rights to access the folder from the workstation. you must have the proper rights to the file. if you are executing the BCP from the cmd line, make sure are spelling it correctly. (many mistakes are made from the command line vs the Query editor)
hope suggestion helps.
"We never plan to Fail, We just fail to plan":)
July 21, 2008 at 2:54 am
Hi,
Both myself and the SQL admins are basically new to SQL 2005, and it feels like trying to find the light switch in the dark on this.
Could someone please take the time out to explain exactly what and where it needs to be done, so that I can solve this problem ?
Thanks in advance
July 22, 2008 at 10:12 am
Basically, you have to understand the which process is running the SSIS package (which machine) and is the authentication set up correctly. If you've installed SQL Server locally on your own PC as well as the server and you're attempting to run/start it from your machine, there's lots of opportunities to get it wrong. (Aside from using incorrect definitions in your SSIS package!)
When you're just starting out, here's what I generally counsul people to do:
- Decide which machine you're going to run on and run everything (Visual Studio, SQL Server, SSIS, etc.) from that machine. This eliminates all of the cross machine issues and you can focus on getting your package right. For your local machine, it's simple, for a server, use Remote Desktop.
- Once you get the Package working to your satisfaction (don't forget about error checking!), you can make it a little more complicated / robust. Run the package from your machine wioth the database on the server. You need to consider the following:
a) From Visual Studio, the package runs under a process called DtsDebugHost. This'll run under your credentials. From a job, it'll initiate from SQL Server Agent.
b) The process running the package must be able to reference the resources. Typically, this means that the name must be resolveable (UNC names are best in this case) and the process must have security access (be running under an ID that can gain access to the resource).
c) BULK INSERT is run by sending the statement to SQL Server. Therefore that process (that machine) must have two things:
- A file access path to the source file.
- Rights to open the resource.
I suspect that the file existed on your local machine (not the server) so the C: driver reference didn't make sense to the server. Plus, I suspect that the server account SQL Server was running under wouldn't have had access in any case (typical senario).
Move the file to the server running SQL Server and use UNC name (to make the process more portable).
Hope this helps.
March 9, 2010 at 12:47 am
you need to keep the flat file source in the server not from u r machine or u r machine should act as a server.
March 9, 2010 at 1:26 am
I sure hope that the original poster found the solution to his problem two years ago...
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply