Passing on username and password to non-domain server

• smac

  SSC Eights!

  Points: 855

  More actions

  February 25, 2011 at 1:10 pm

  #246122

  I know the following issues is typically a permissions issue but this is a bit different (I think):

  Code: 0xC001401E Source: Import_LapLine_Protocol_MachX Connection manager "SourceConnectionFlatFile" Description: The file name "\\10.239.130.180\export\NEW PROTOCOL FILE.csv" specified in the connection was not valid.

  I am going out to a server that is not on our domain, so for example I map the drive it asks for a username and passsword.

  So my issue is when I run the package as a job it can't create a new file on this server, so my question is, is there a way to pass the username and password when I connect to the server in my script task:

  Dim Path As String = "\\10.239.130.180\export\"

  I have tried

  Dim Path As String = "\\10.239.130.180\export\", "username", "password"

  Dim Path As String = "\\10.239.130.180\export\, username, password"

  Not sure the direction to take at this point.

  Thanks!!

• Orlando Colamatteo

  SSC Guru

  Points: 182279

  More actions

  February 25, 2011 at 1:55 pm

  #1291761

  Whatever or whoever is kicking off your SSIS package will be forced to authenticate to that network location.

  Can you tell us more about the execution context? Is it a SQL Agent Job? An NT Task calling a batch file to call dtexec? xp_cmdshell?

  There are no special teachers of virtue, because virtue is taught by the whole community.
  --Plato

• smac

  SSC Eights!

  Points: 855

  More actions

  February 25, 2011 at 1:59 pm

  #1291764

  NOPE, I was wrong, my resolution:

  "I decided to read the file off that server then create the new file locally and it works fine.

  Thanks!"

  Did work for the moment then I realized in the future I will need to move the file that I am reading so back to my original issue if anyone can help.

  I have this package scheduled as a job on the SQL Server, I don't know much about user accounts and how the SQL agent (?) gains access

  to the server (that's not on the domain).

  Thanks!