March 15, 2022 at 11:00 am
this is driving me nuts....
i am trying to get data from a csv file which is stored on a different server but for gods sake i can not manage to get this to be executed in a job
Here is what i have done so far:
Not sure if important, but i guess:
And this is where i can not get any further no matter what i tried and i dont know what else to try:
I have no idea how i am supposed to continue from here...
I canfirmed in the ssis exection that its the same user running the job.
I am not really suprised it is not working with the browsing feature through an added network, but i need to know how i can make it work to get the data from a connection string...
I found some Script Task Stuff but only walls of code of which most seem to do alot i dont actually need, but its hard for me the judge since ive never used C#
I want to be the very best
Like no one ever was
March 15, 2022 at 11:12 am
Try using the full UNC path, eg:
\\servername\c$\folder\filename
(after verifying that the user running the job can access that path)
Also check that your proxy is being picked up properly by checking the All Executions report.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
March 15, 2022 at 1:31 pm
Try using the full UNC path, eg:
\\servername\c$\folder\filename
(after verifying that the user running the job can access that path)
.
i used tried the connection string including the full path of the file: \\tsclient\Z$\P90\spool_2_mp\ZRW\ZRW_FW.csv
the connection manager does not recognize the file, unless i click the browse button and then im in the folder i want to be
once i change datatype form txt to csv and select the file the string is changed back to this
\\tsclient\Z\P90\spool_2_mp\ZRW\ZRW_FW.csv
i tried using the connection string in the manager and in the connection string expression
for both manual execution in VS works like before, but trying to execute package via job results in the same error as before, i attached in screenshot
Also check that your proxy is being picked up properly by checking the All Executions report.
All Executions tab for "Caller" is the same as the user which can run the packet in VS.
Not sure if this was the right approach but when creating credentials for the propxy i just set the same pass the login uses for the login in SQL Server.
I want to be the very best
Like no one ever was
March 15, 2022 at 1:40 pm
Unless Z is a local drive on the server, those are not UNC paths. You should avoid mapped drives when doing this.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
March 18, 2022 at 7:27 am
Unless Z is a local drive on the server, those are not UNC paths. You should avoid mapped drives when doing this.
I went to our infrastructure asking for the complete path
After getting the wrong path from them i was mad even more
I solved the issue the following way:
Now i feel stupid, but the good feeling of finding the solution is > the shame currently
I want to be the very best
Like no one ever was
March 18, 2022 at 8:30 am
Well done on solving it. There's no shame in this, it was a learning experience 🙂
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
March 18, 2022 at 10:38 pm
I agree with Phil. You can kick your own butt if you want (heh... I've got a sore butt from doing the same) but you learned something different and then shared it with us! You learned, we learned, and, not that it matters, you "earned some stripes" in the area of "absolute honesty". Well done!
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply