Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2012 Forums
 SSIS and Import/Export (2012)
 seeking good example of secure UNC destination

Author  Topic 

Hommer
Aged Yak Warrior

808 Posts

Posted - 2014-04-22 : 12:35:02
Hi,

I am in need of a good example of how to access a flat file destination on a secured network location for my ssis 2008 to 2012 upgrade.

These are the questions I badly need helps with.

1. in VS2012, where can I save or pass in my windows credentials?

2. is there a way during the dev, to connect to it as a service account user with saved password?

and, 3. deployment related complications.

Thanks!

Hommer
Aged Yak Warrior

808 Posts

Posted - 2014-04-22 : 16:18:32
I have solved my Q1, and Q2.

Here are Q3, trying to run it on the server and errors I got.

I built/deployed the project without error.

On the SQL 2012 server, through my remote SSMS,
A) Execute.. dtsx under the SSISDB tree, got Cannot open the datafile "\\mynetwork\folder\file.txt"

Why it failed? I thought I was running it using my windows acct.

And, B) going through next steps to setup agent job for it.

1) created credential using the domain service acct, 2) created proxy pointed to that credential, 3) created agent job for ssis run as the proxy.
Start job at Step...run into next:
Error: Login failed for user "myDomin\myserviceacct"

Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2014-04-23 : 09:39:39
Ok, now I have resolved above A). We have two domains, domainA and domain.
I have to start the SSMS Run as different user to enter domainB because I logged in windows under domainA.

And I am fighting B).

Unable to start execution of step 1 (reason: Error authenticating proxy domainB\svcacct, system error: The user name or password is incorrect.). The step failed.


Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2014-04-23 : 10:23:21
Finally, I got the agent job to execute the package.

For those of you who are reading this, it is as simple as copy/paste password during the creating of credential that did not get the right password. Because it only shows wildcards, it is hard to notice the difference.

Also, I kept messing with following due to this setting is new in 2012, but that turned out to be irrelevant.
Job Step Properties, Configuration, Connection Managers, UserName and Password.
Go to Top of Page
   

- Advertisement -