Hi ,
We are using SSIS 2005 and have a Flat File Connection in a package.
The connection is pointing to a Mapped network drive (let see
S:\file\myfile.txt) amd the package is running fine.
Now in the Connection ConnectionString property I replaced the pathname
using UNC (let see \\sww\web - sss\file\myfile.txt) but the package can not
find the file anymore. I even tried to create a brandnew Flat file connection
by entering the UNC in the dialog box but it keeps telling me that the file
name is invalid.
Any clue ?

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J

On Apr 3, 3:54*pm, Truc H. <Tr... (AT) discussions (DOT) microsoft.com> wrote:
Hi Truc,

If you're using a property expression to set your filename, check that
the "\" characters have been escaped correctly. You might also want
to check that the spaces in the "web - sss" portion of the filename
isn't causing an issue.
Other than that, I would usually guess this was a permissions issue,
but if you have permissions to browse to the file via the UNC and are
trying to run the package from within VS then the package should be
using your credentials when looking for the file :-/

Good luck!
J