Prev: To update a clr dll should I drop the assembly?
Next: Percent of advance in Restore database
From: ujjc001 on 1 Jul 2008 12:49
Please let me know I'm not crazy.
I have a NAS that I want to back up to. It has a user account, we'll
call him Bob. Lets say I have a folder \\NAS\Backuphere\ which, if
I'm logged into my computer as "bob" with the same password that bob
has on the NAS, I can get to the share just fine.
In SQL I can't backup to that share directly but I want to be able to
backup to it by using a proxy on ssis package. I create a proxy with
the username and password for bob but it still fails. I've given the
bob proxy as much rights as I can, but it seems it's not using that
account for the remote login to the share.

Thoughts? Please please help.

Thanks!
Jeff
From: Todd C on 2 Jul 2008 12:22
Jeff:
In order to create the Proxy, you first set up the Credentials for "Bob",
yes? You may need to verify his password. If it's not right, he won't be able
do do anything.

When you say "Bob" has as much rights as you can give him, how high up did
you make him? sysadmin would do it.

Are you trying to execute the SSIS Package from SQL Agent? If so, are you
selecting Run AS in the JoStep setup?

Keep us posted
--
Todd C



"ujjc001(a)gmail.com" wrote:

> Please let me know I'm not crazy.
> I have a NAS that I want to back up to. It has a user account, we'll
> call him Bob. Lets say I have a folder \\NAS\Backuphere\ which, if
> I'm logged into my computer as "bob" with the same password that bob
> has on the NAS, I can get to the share just fine.
> In SQL I can't backup to that share directly but I want to be able to
> backup to it by using a proxy on ssis package. I create a proxy with
> the username and password for bob but it still fails. I've given the
> bob proxy as much rights as I can, but it seems it's not using that
> account for the remote login to the share.
>
> Thoughts? Please please help.
>
> Thanks!
> Jeff
>
From: ujjc001 on 2 Jul 2008 23:42
On Jul 2, 11:22 am, Todd C <To...(a)discussions.microsoft.com> wrote:
> Jeff:
> In order to create the Proxy, you first set up the Credentials for "Bob",
> yes? You may need to verify his password. If it's not right, he won't be able
> do do anything.
>
> When you say "Bob" has as much rights as you can give him, how high up did
> you make him? sysadmin would do it.
>
> Are you trying to execute the SSIS Package from SQL Agent? If so, are you
> selecting Run AS in the JoStep setup?
>
> Keep us posted
> --
> Todd C
>
>
>
> "ujjc...(a)gmail.com" wrote:
> > Please let me know I'm not crazy.
> > I have a NAS that I want to back up to.  It has a user account, we'll
> > call him Bob.  Lets say I have a folder \\NAS\Backuphere\ which, if
> > I'm logged into my computer as "bob" with the same password that bob
> > has on the NAS, I can get to the share just fine.
> > In SQL I can't backup to that share directly but I want to be able to
> > backup to it by using a proxy on ssis package.  I create a proxy with
> > the username and password for bob but it still fails.  I've given the
> > bob proxy as much rights as I can, but it seems it's not using that
> > account for the remote login to the share.
>
> > Thoughts?  Please please help.
>
> > Thanks!
> > Jeff- Hide quoted text -
>
> - Show quoted text -

Credentials made, yes, same password, yes sys admin in the proxy and
just about every thing but deny data reader / deny data writer-
probably more then just those two, but really almost everything. Yes,
agent is running the ssis package in a job, yes the step was run as
"bob". Works if the target for the backup is local, but not remote
and I double checked all passwords. It's like "credentials" and
"proxys" don't apply to - pass through to - network share permissions.
From: Todd C on 3 Jul 2008 08:49
If everything is correct, then it has to be a permissions issue.

If you have the rights to do so, try these techniques:
1) Grant rights on the backup folder location to EVERYONE, Full Control.
Then run the job from SQL Agent. Does the job succeed? (Remember to remove
the EVERYONE permissions afterward!)

2) Create a Cerdentials and Proxy with some all-powerful account like Domain
Admin if you can. Run the Job Step with that new Proxy. Does the job succeed?
(delete the proxy when finished)

If the job succeeds under either of these two scenarios, then it is
permission based.

--
Todd C


"ujjc001(a)gmail.com" wrote:

> On Jul 2, 11:22 am, Todd C <To...(a)discussions.microsoft.com> wrote:
> > Jeff:
> > In order to create the Proxy, you first set up the Credentials for "Bob",
> > yes? You may need to verify his password. If it's not right, he won't be able
> > do do anything.
> >
> > When you say "Bob" has as much rights as you can give him, how high up did
> > you make him? sysadmin would do it.
> >
> > Are you trying to execute the SSIS Package from SQL Agent? If so, are you
> > selecting Run AS in the JoStep setup?
> >
> > Keep us posted
> > --
> > Todd C
> >
> >
> >
> > "ujjc...(a)gmail.com" wrote:
> > > Please let me know I'm not crazy.
> > > I have a NAS that I want to back up to. It has a user account, we'll
> > > call him Bob. Lets say I have a folder \\NAS\Backuphere\ which, if
> > > I'm logged into my computer as "bob" with the same password that bob
> > > has on the NAS, I can get to the share just fine.
> > > In SQL I can't backup to that share directly but I want to be able to
> > > backup to it by using a proxy on ssis package. I create a proxy with
> > > the username and password for bob but it still fails. I've given the
> > > bob proxy as much rights as I can, but it seems it's not using that
> > > account for the remote login to the share.
> >
> > > Thoughts? Please please help.
> >
> > > Thanks!
> > > Jeff- Hide quoted text -
> >
> > - Show quoted text -
>
> Credentials made, yes, same password, yes sys admin in the proxy and
> just about every thing but deny data reader / deny data writer-
> probably more then just those two, but really almost everything. Yes,
> agent is running the ssis package in a job, yes the step was run as
> "bob". Works if the target for the backup is local, but not remote
> and I double checked all passwords. It's like "credentials" and
> "proxys" don't apply to - pass through to - network share permissions.
>
From: ujjc001 on 3 Jul 2008 09:06
On Jul 3, 7:49 am, Todd C <To...(a)discussions.microsoft.com> wrote:
> If everything is correct, then it has to be a permissions issue.
>
> If you have the rights to do so, try these techniques:
> 1) Grant rights on the backup folder location to EVERYONE, Full Control.
> Then run the job from SQL Agent. Does the job succeed? (Remember to remove
> the EVERYONE permissions afterward!)
>
> 2) Create a Cerdentials and Proxy with some all-powerful account like Domain
> Admin if you can. Run the Job Step with that new Proxy. Does the job succeed?
> (delete the proxy when finished)
>
> If the job succeeds under either of these two scenarios, then it is
> permission based.
>
> --
> Todd C
>
>
>
> "ujjc...(a)gmail.com" wrote:
> > On Jul 2, 11:22 am, Todd C <To...(a)discussions.microsoft.com> wrote:
> > > Jeff:
> > > In order to create the Proxy, you first set up the Credentials for "Bob",
> > > yes? You may need to verify his password. If it's not right, he won't be able
> > > do do anything.
>
> > > When you say "Bob" has as much rights as you can give him, how high up did
> > > you make him? sysadmin would do it.
>
> > > Are you trying to execute the SSIS Package from SQL Agent? If so, are you
> > > selecting Run AS in the JoStep setup?
>
> > > Keep us posted
> > > --
> > > Todd C
>
> > > "ujjc...(a)gmail.com" wrote:
> > > > Please let me know I'm not crazy.
> > > > I have a NAS that I want to back up to.  It has a user account, we'll
> > > > call him Bob.  Lets say I have a folder \\NAS\Backuphere\ which, if
> > > > I'm logged into my computer as "bob" with the same password that bob
> > > > has on the NAS, I can get to the share just fine.
> > > > In SQL I can't backup to that share directly but I want to be able to
> > > > backup to it by using a proxy on ssis package.  I create a proxy with
> > > > the username and password for bob but it still fails.  I've given the
> > > > bob proxy as much rights as I can, but it seems it's not using that
> > > > account for the remote login to the share.
>
> > > > Thoughts?  Please please help.
>
> > > > Thanks!
> > > > Jeff- Hide quoted text -
>
> > > - Show quoted text -
>
> > Credentials made, yes, same password, yes sys admin in the proxy and
> > just about every thing but deny data reader / deny data writer-
> > probably more then just those two, but really almost everything.  Yes,
> > agent is running the ssis package in a job, yes the step was run as
> > "bob".  Works if the target for the backup is local, but not remote
> > and I double checked all passwords.  It's like "credentials" and
> > "proxys" don't apply to - pass through to - network share permissions.- Hide quoted text -
>
> - Show quoted text -

Not to sound stupid, but can you verify you can do this. The NAS is
NOT active directory based. It's works for everything else by just
using the active logged in credentials- i.e. as long as you're using a
login that is the same username and it has the same password- it just
works. Can you try to set up some similiar test on your end. Backing
up to a folder that is shared and has permissions of only "local"
users- given that the usernames and passwords are the same. (This
also takes AD out of the equation).
Thanks, and I'll try your suggestions to narrow this down too.
Jeff
 |  Next  |  Last
Pages: 1 2
Prev: To update a clr dll should I drop the assembly?
Next: Percent of advance in Restore database