Note that there are some explanatory texts on larger screens.

plurals
  1. POSSIS Package runs from SSIS but not from Job
    text
    copied!<p>I have built an SSIS Packaage that imports data on a daily basis. </p> <p>i have tested it in BIDS and it runs fine, i have deployed it to the the SSIS server and it runs fine, but when i schedule it to run as a job it Errors out. i get the errors below. i've added the srvSQLagent account to the the correct group to have access to the folder that causing the problem.. am i missing something stupid here?</p> <p>===================================================================</p> <p>Date 03/07/2013 14:55:06 Log Job History (Import SN2 Data)</p> <p>Step ID 1 Server STX-RPT Job Name Import SN2 Data Step Name Run Import Package Duration 00:00:09 Sql Severity 0 Sql Message ID 0 Operator Emailed<br> Operator Net sent<br> Operator Paged<br> Retries Attempted 0</p> <p>Message Executed as user: INT\srvSQLagent. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.<br> Started: 14:55:06<br> Error: 2013-07-03 14:55:15.69<br> Code: 0xC001401E<br> Source: Servicenet Data Import Connection manager "Downloaded"<br> Description: The file name "\\FILE\Groups\ISG\England\Servicenet Data\Downloaded" specified in the connection was not valid. End Error<br> Error: 2013-07-03 14:55:15.69<br> Code: 0xC0202070<br> Source: Servicenet Data Import Connection manager "Downloaded"<br> Description: The file name property is not valid. The file name is a device or contains invalid characters. End Error<br> Error: 2013-07-03 14:55:15.69<br> Code: 0xC0029163<br> Source: File System Task File System Task<br> Description: File or directory "\\FILE\Groups\ISG\England\Servicenet Data\Downloaded" represented by connection "Downloaded" does not exist. End Error<br> DTExec: The package execution returned DTSER_FAILURE (1).<br> Started: 14:55:06<br> Finished: 14:55:15<br> Elapsed: 9 seconds.<br> The package execution failed.<br> The step failed.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload