permission problems during the execution of a vbscript step.

[no.mercy]

Hi all,
time ago i've created some dts packages to load excel files into my
db. Last week my boss asked me to adapt this packages to the new
sqlserver installed in our site. For time reasons i've choosen to do
it importing the packages into 2005 instead of develope all the
packages using SSIS.
The import work was really quick and all the packages are wotking in
the new server.
I also developed a procedure to launch this packages from an sql query
windows. The problem is that launching the packages using this stored
procedure tha package fail. The failure always happen in the same step
(a vbscript task just executing the creation of file system object.).
what i found was that launching the dts from the designer this step is
executed using my login name, while if the package is launched by the
stored procedure the step is executed using the "system" user. so this
mean that the system user cannot create an fso. now... i really don't
know how to solve this situation: is the last step to finish a work
and i really don't know what direction i have to follow. any
suggestion??
thanks in advance and sorry for my english, hope i was clair in
explaining the problem.
Luciano

[Todd C]

Luciano:

You need to grant FSO permissions to the account that is running SQL Server.
If it is "Local System" and the FSO's will be on a network share somewhere,
you are out of luck as a "Local System" account will not be recognized
outside the machine. You may need to create a special Domain login for the
purpose of a SQL Service Startup Account.

Read Books On Line for more info on SQL Starup accounts.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

Post by no.mercy
Hi all,
time ago i've created some dts packages to load excel files into my
db. Last week my boss asked me to adapt this packages to the new
sqlserver installed in our site. For time reasons i've choosen to do
it importing the packages into 2005 instead of develope all the
packages using SSIS.
The import work was really quick and all the packages are wotking in
the new server.
I also developed a procedure to launch this packages from an sql query
windows. The problem is that launching the packages using this stored
procedure tha package fail. The failure always happen in the same step
(a vbscript task just executing the creation of file system object.).
what i found was that launching the dts from the designer this step is
executed using my login name, while if the package is launched by the
stored procedure the step is executed using the "system" user. so this
mean that the system user cannot create an fso. now... i really don't
know how to solve this situation: is the last step to finish a work
and i really don't know what direction i have to follow. any
suggestion??
thanks in advance and sorry for my english, hope i was clair in
explaining the problem.
Luciano