November 6, 2008 at 3:29 am
Hi, I've set up a SSIS package on 2005 (SP2) which takes data from a table and populates a spreadsheet, all very simple. I run it in debug mode and it works, populating the spreadsheet as expected.
However when i run it as a job (using the 'file system' as the package source) I get the follownig error
Option "Source=\\Euwmdc01data01\71\BIS\Core" is not valid. The command line parameters are invalid. The step failed.
The spreadsheet is on another server hence the full path name and there is more to the file name after the word Core, however there is a space between Core and the next word. I've tried editing the excel connection and putting double quotes round the excel path but it then complains about somethnig else in the string being invalid 8:00;HDR !! After this it doesn't like the fact I put quotes around the excel file path anyway and I can't edit the step.
Any help please !!!! It works fine in SSIS debugger ?!?! The account it runs as is the Agent and has change rights on the .xls
November 6, 2008 at 10:53 am
hmmm... I had a similar problem.. or I think it was similar..
and I went to the sql server agent service in services on my pc and change the "Log on as" account from local system account to my lan id which would have the rights to browse to a network share..
or you can grand the account used in the sql service account the rights in that network share..
or you can get a service account created that will have the rights.. then you can grant that the required rights in sql also..
Hope that helps..
November 6, 2008 at 11:18 am
I am working on something similar now.. here's an additional option using sql proxies.. look down on this link.. the user Abha had some suggestions..
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=175775&SiteID=17
here's the except that i'm specifically referring to that might help you..
Hey Even I was facing the same problem but i could solve it .. Just with the few steps below:
1. Go to SQL server Management Studio. under Security ->Credentials->Create New Credential. Give any Credential Name e.g 'Job Account' . Fill your own Windows account in identity column. domain\account. Password Give ur own passowrd
2. After creating 'JobAccount' as Credential Goto SQLServerAgent->Proxies. Create a new proxy. Give any proxy name.e.g give 'JobProxy' . Credential should be the one which u created in the above step.Here in this case it is JobAccount'. In subsystems. Check Sql Server Integration Servive Package.
3. Now when you create a job it should run under 'Jobproxy' instead of 'SQL Agent Service account'.
November 7, 2008 at 8:22 am
This is just a thought, but I've had issues in the past where I was using double quotes instead of a single tic around items. Have you tried it with single tics?
November 7, 2008 at 9:36 am
Hi, thanks both for your input. Well tried the proxy solution and that made no difference. I also edited the command line string of the job step to add single quotes. also tried double quotes and other combo's. None of these worked unfortunately.
The account I'm using runs the SSIS service, the SQL Agent Service, is a SQL sysadmin and the job owner and has rights to update the spreadsheet (I've proved this by logging on with this account and updating it manually)...I can't give it anymore access....so frustrated.
Any more suggestions please !?!?!? :crazy:
November 7, 2008 at 9:48 am
Recently we had a windows scheduled service that wouldn't work because it didn't have rights to windows\system32\cmd.exe. Since you are using SSIS instead of windows scheduling it may not be the same but it sounds like you are having a security issue that is causing this to fail. I would check to on the windows security of the id you are using.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply