May 6, 2011 at 8:57 am
I'm having this error:
Option "Source=ServerName;Initial" is not valid. The command line parameters are invalid. The step failed.
I have created a credential and a proxy that gives access to all the subsystems. Is there some principals that I have to make sure I add or some references that I have to make sure I add so that I'm able to run the SSIS package from the SQL Server Agent? Thanks in advance.
May 6, 2011 at 9:12 am
stormsentinelcammy (5/6/2011)
I'm having this error:Option "Source=ServerName;Initial" is not valid. The command line parameters are invalid. The step failed.
I have created a credential and a proxy that gives access to all the subsystems. Is there some principals that I have to make sure I add or some references that I have to make sure I add so that I'm able to run the SSIS package from the SQL Server Agent? Thanks in advance.
The link below are the accepted accounts pay attention to the foot notes and when using proxy account it is better to use a proxy of System Admin because the proxy is just a clone. If you are connecting to both Oracle and DB2 an admin account in both systems is also required when using the Agent for SSIS automation.
http://msdn.microsoft.com/en-us/library/ms345380.aspx
Kind regards,
Gift Peddie
May 6, 2011 at 9:24 am
Thanks for the prompt reply, but I do not have the SA password and whenever I do run the job it runs under my user name. I have added all the same rights that the SA has to my user name as well. Even though I've done that I still get the same error as before. Do you think that there might be something else that I'm not checking or doing?
May 6, 2011 at 9:42 am
stormsentinelcammy (5/6/2011)
Thanks for the prompt reply, but I do not have the SA password and whenever I do run the job it runs under my user name. I have added all the same rights that the SA has to my user name as well. Even though I've done that I still get the same error as before. Do you think that there might be something else that I'm not checking or doing?
If this is not production you may have to restart the SQL Server service and the Agent. And the job when you are running it manually it runs in the context of your permission and when the Agent runs it, the job is running in the context of the Agent so it may still be related to permissions.
Kind regards,
Gift Peddie
May 6, 2011 at 9:48 am
Ok, I see where you are getting it, you might be right, when I run the job manually it runs fine because its running under my user because obviously I'm running it. How would I assure that when the job runs through the agent that it runs under my user? When I check the owner of the job it says my username and when the job fails it says that the job ran as my username. This issue is really bothersome when I have exhausted a lot of options and still the same error.
May 6, 2011 at 9:59 am
stormsentinelcammy (5/6/2011)
Ok, I see where you are getting it, you might be right, when I run the job manually it runs fine because its running under my user because obviously I'm running it. How would I assure that when the job runs through the agent that it runs under my user? When I check the owner of the job it says my username and when the job fails it says that the job ran as my username. This issue is really bothersome when I have exhausted a lot of options and still the same error.
I would not say you have exhausted a lot of options if your proxy definition and execution context is not correct relative to the Agent, check below to see if your setup is correct.
http://msdn.microsoft.com/en-us/library/ms190698.aspx
Kind regards,
Gift Peddie
May 6, 2011 at 10:04 am
Yeah I know what you mean, but after spending too much time on this issue it sure feels that way 😛
I'm going to spend some time making sure my settings are like the link you sent me and I'll post back my results in a few minutes. Thanks again for your help.
May 6, 2011 at 10:16 am
stormsentinelcammy (5/6/2011)
Yeah I know what you mean, but after spending too much time on this issue it sure feels that way 😛I'm going to spend some time making sure my settings are like the link you sent me and I'll post back my results in a few minutes. Thanks again for your help.
I am glad I could help.
🙂
Kind regards,
Gift Peddie
May 6, 2011 at 10:17 am
That link you sent in your last post is one that I was looking at earlier to verify what I was doing earlier, but I created a new proxy, checked to make sure msdb for my username had SQLAgentUserRole, SQLAgentReaderRole and SQLAgentOperatorRole selected. I even created a new credential profile and selected that one and I'm still getting the same error. If you don't mind can you walk me step by step how you do it to assure that I am not missing out on any steps?
May 6, 2011 at 10:33 am
stormsentinelcammy (5/6/2011)
That link you sent in your last post is one that I was looking at earlier to verify what I was doing earlier, but I created a new proxy, checked to make sure msdb for my username had SQLAgentUserRole, SQLAgentReaderRole and SQLAgentOperatorRole selected. I even created a new credential profile and selected that one and I'm still getting the same error. If you don't mind can you walk me step by step how you do it to assure that I am not missing out on any steps?
I don't know why Microsoft defined those roles but if you look at the docs those roles do not have permissions to run proxy, only system admins. Here is a visual configuration of the proxy account use it to correct issues as needed.
http://www.codeproject.com/KB/database/SQL_Server_Agent_Proxy.aspx
Kind regards,
Gift Peddie
May 6, 2011 at 10:53 am
I keep on finding something strange when I'm trying to add my username as a SQL Login in the "principals" section of the proxy settings. This is how it goes, I check the checkbox next to my username and click add, then I hit OK. When I double click the proxy to just view the "principals" again, my username is gone. Is that an intended result or is something not letting me add my username to the principals section?
May 6, 2011 at 10:59 am
I keep on finding something strange when I'm trying to add my username as a SQL Login in the "principals" section of the proxy settings. This is how it goes, I check the checkbox next to my username and click add, then I hit OK. When I double click the proxy to just view the "principals" again, my username is gone. Is that an intended result or is something not letting me add my username to the principals section?
May 6, 2011 at 11:01 am
Posted the same reply twice because I thought it didn't post the first time. :hehe:
May 6, 2011 at 11:12 am
I know why my username doesn't show up, its because my username is sysadmin already and users with sysadmin rights automatically have access and thus won't show up on the list. With that said is there anything else I should be looking at?
May 6, 2011 at 11:28 am
stormsentinelcammy (5/6/2011)
I know why my username doesn't show up, its because my username is sysadmin already and users with sysadmin rights automatically have access and thus won't show up on the list. With that said is there anything else I should be looking at?
Yes go into configuration manager and check what account is used to run the Agent, if it is Network Service that may be your problem you need an account with more permissions.
Kind regards,
Gift Peddie
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply