DTS Through ASP Page permissions

#1

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#2

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#3

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#4

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#5

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#6

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#7

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#8

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#9

Tim,

What version of SQL Server are you running? When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. (SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000) or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cavins (AT) gmail (DOT) com> wrote

Quote:

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim

#10

Russell,

Thanks for the response and sorry for the late response. My priorities
got shifted for awhile and now I'm back on this.

I am using SQL Server 2000. I currently have a stored procedure that
is using xp_cmdshell to run DTSRUN.

I was trying to get the procedure to start a SQL Agent job but was
unsuccessful that way.

Also, do you know of a way to return an error if the DTS fails? I have
no way of knowing except to compare the number of rows in the table
before and after the job runs.

Thanks,

Tim

On Dec 9 2008, 9:41*am, "Russell Fields" <russellfie... (AT) nomail (DOT) com>
wrote:

Quote:

Tim,

What version of SQL Server are you running? *When you say "running a DTS
through a stored procedure", do you mean that you are starting a SQL Agent
job, using xp_cmdshell to run DTSRUN.exe, or something else?

If it is a SQL Agent job running as a sysadmin account, then the DTS would
be running as the SQL Server service account. *If a SQL Agent job is running
as a non-sysadmin, then the job will run as a proxy account. *(SQL Server
2000 only has one, but 2005 allows you to define many SQL Agent proxy
accounts.)

If you are running it via xp_cmdshell, the SQL Agent Proxy Account (2000)or
(2005) the ##xp_cmdshell_proxy_account## credential's domain login identity.

RLF

"Tim" <tim.cav... (AT) gmail (DOT) com> wrote in message

news:a43ab758-2549-4392-bab0-24866d742745 (AT) x38g2000yqj (DOT) googlegroups.com...

I'm running a DTS through a stored procedure called from an ASP page
on Server B.

Server B is also the SQL Server.

The DTS package is supposed to access a file on Server A.

I'm having permission issues in running this through the web. I've
tried giving IUSER_ServerB and IWAM_ServerB full permission on the
file but that didn't work.

What account needs permissions on the file? Do I need to add it
differently that I would the IUser/IWAM accounts?

Tim- Hide quoted text -

- Show quoted text -