November 26, 2008 at 6:03 am
i've posted this discussion in SSIS section but may be here is the best place. anybody can help me?
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
December 10, 2008 at 1:59 am
check if your "system" account is having access to scrun.dll file which is used by scripting engine to create fso objects. It will be in system32 folder.
Sometimes Antivirus or other security services may stop you from using FSO objects.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply