Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Executing package through Job scheduler fails

Status
Not open for further replies.

zdonev77

Programmer
Dec 16, 2008
5
US
Hi all,

I developed a package which runs fine under BIDS but as soon as I run it through a job I get following message:

Executed as user: domain\zoran. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:32:18 AM Error: 2009-01-21 09:32:19.19 Code: 0xC0202070 Source: Import_coitem Connection manager "coitem_flat_file" Description: The file name property is not valid. The file name is a device or contains invalid characters. End Error DTExec: The package execution returned DTSER_SUCCESS (0). Started: 9:32:18 AM Finished: 9:32:19 AM Elapsed: 0.844 seconds. The package executed successfully. The step succeeded.

I tried to encryption with password and to load the package to the server. Nothing worked so far.
I have full right to the unc path. Are there any issues with SSIS and UNC paths because it works when i set the import path to be locally (C:\..)
To mention is that I query a table to receive the path and set it to a variable!
-----------------------------------------------------------

Environment:

SQL Server 2005
Windows XP
Developer user: domain\zoran
SQL Agent Account: domain\zoran

UNC path: \\testserver\Exportfolder\coitem.csv

What do I miss?

I appricate any help! I am strugeling a hole day whit this porblem.
 
it probably has to do with the \\ in the unc path you may need to escape it. thry /\\path.
 
i didn't fix my problem but I think I found the cause of the issue.

The network share that I am pointing to is a Novell share, if I do the same thing to a windows share everything works fine.

does anyone has experienced this before?
 
that would probably be the problem. Is there anyway to have the file(s) pushed to your server? and process them locally.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top