Click here to Skip to main content
14,635,626 members
Rate this:
Please Sign up or sign in to vote.
See more:
1. we create a package first at VS 2010, it use flat file source to get log files from remote PCs and can store data to local DB success;

2. then we deploy the package to Integration Services Catalogs -> SSISDB;

3. we use SQL server to create a SSIS job to run the package, but it didn't work, and shows the follow error 'The job failed. The Job was invoked by User sa. The last step to run was step 1 (L3_Z1A).';

What I have tried:

1. we try to get log files from local PC, the job run success,
but when we change the flat file path to remote PC, it failed;
Updated 18-Feb-17 23:54pm
Richard Deeming 18-Feb-17 8:44am
So look at the details of step 1, and see what error was logged.

1 solution

Rate this:
Please Sign up or sign in to vote.

Solution 1

The SQL server engine is running as a Windows service which is assigned to a local system account by default. Local accounts have no access to network ressources - this might be the reason why you can't access files from another computer. Try to change the Windows account of the service to an Admin account with network priviliges.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100