April 5, 2007 at 12:04 pm
Hi all,
I'm in trouble with a DTS package. I built a package that transfer a file to a specified path. So, I give this path throught global variables. When I execute the package on my machine, it works fine. But when I execute the package on another machine, it executes just to the middle of package. I have looked for a possible mistake on it, but everyting is ok.
I dont know why its doing it, I'm calling the dts throught C#, Microsoft.SqlServer.DTSPkg80.dll. This dll exists in both machine.
There's no reason to stop execution on the middle...
Anyone can help me?
Thanks!
Ju
April 5, 2007 at 12:36 pm
Are you using a mapped drive in the file path? If so, try using a UNC path. Does the Package fail and generate an error message?
Greg
Greg
April 5, 2007 at 1:05 pm
These are the steps that the package does
- Set global variable of access path (Ex. C:\test.mdb)
- I clean this MDB tables (Ex: DELETE Tab_1)
- I do some inserts from Oracle to Access table (based on the path that is passed to access it)
- Here is the point, before to end all these inserts, it executes successufully on another machine, but just three or four tables of ten or more that really have data. When I execute this package on my machine, all tables been populated, and the MDB file, successufully go to destination path (Ex: C:\ETL\).
I'm not using mapped drive, I'm using local drive, like C:\. I'm using the same directory for source and destiny.
I'm really don't understanding.
April 5, 2007 at 3:01 pm
So, is the file path on the server the same as the path on your local machine? In other words, is there a C:\ETL\ or C:\test.mdb on the server?
If the location is there, do you have permission to access it on the server? I suggest you enable package logging:
Open the package in DTS Designer
Click on Package and select Properties
Click on the Logging tab check the box next to "Log package execution to SQL Server"
Run the package then right-click on the package in Enterprise Manager and select Package Logs
You should see any error messages generated during the execution of the package.
Greg
Greg
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply