Error while Configure SSIS Job
Hi, I have created one package on my local station which point to aactaul server to get the files and dump into sql server table. When i run this package manually, it runs smooothly. This is first time i would like to schedule my job. I have copied and paste an actual package from local system to Server. I went to SQl Servre Agent to create new job... General Tab - i type name, give my user id (sysadmin) then leave unauthorized local Stpe - create new step, give name, in type - specify SSIS package, Down in general tab i select file system and browse to the path where i pasted my package... then i try to click ok and again ok.."the specified !sunsystem' is invalid". what does this error mean? i looked on google but did not get proper ans. I have not actual deply my packge.. just did copy and paste from ly desktop to server. How can i resolve this error or please let me know if i am missing any step. One more thing... i have SSMS installed on ly station with SQL server Agent. SO i connect to server and then trying to schedule from my station. I am not log in to actual server and sheduling. Thanks, Shalin
July 18th, 2011 2:32pm

what is protection Level of package? I think you deployed it with default protection level, which is EncryptSensitiveWithUserKey, and as sql server agent job runs as another account which is different than the account which package developed, the package couldn't load sensitive data like connection passwords, you should try with EncryptSensitiveWithPassword, and set a package password, a good picture tutorial on deployment a package with correct protection level and run it as sql server job is here: http://www.protalk.in/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/http://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 2:42pm

There is not protection level. I use windows authentication and i have not used any encrypt passowrd to protect that package. Again i have not deployed package. What i did, just copy and paste from my station to server and trying to browse that path in AGent Job. Do i need to deploy a package? Thanks, Shalin
July 18th, 2011 2:47pm

There is not protection level. I use windows authentication and i have not used any encrypt passowrd to protect that package. Again i have not deployed package. What i did, just copy and paste from my station to server and trying to browse that path in AGent Job. Do i need to deploy a package? Thanks, Shalin So if you used windows authentication; the account who runs sql server agent under it should have access to databases which is provided the ssis package. or you should create a proxy account and run job under it. http://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 2:54pm

I am suppose to tun this job by connectin that sevre using SSMS and run it from SQL Agent. I think i am missing proxe settings. How can i set up my account to proxy? Thanks, shalin
July 18th, 2011 3:05pm

here you can find out how to create and use proxy accounts in jobs: http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/69441/ just note that the account who is connected to this proxy should have enough permissions on underlying databases which used in ssis package.http://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 3:09pm

This link is really awesome. Here is the one place i got stuck. I have created credential successfully. Now when i am trying to create proxy, i get an error , it says "The specified @subsystem_id('11') does not exixst." What does that mean? Thanks, Shalin
July 18th, 2011 3:44pm

Now when i am trying to create proxy, i get an error , it says "The specified @subsystem_id('11') does not exixst." Subsystem id 11 is DTS Pakage Execution. It is used by SSIS. It should have been added to the msdb..syssubsystem table when SSIS was installed. Run select * from msdb..syssubsystem and see if there is an entry for subsystem_id 11. or verify that SSIS has been installed. reference: http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_22553747.html http://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 3:51pm

ssis has been onstalled on my station. When i try to run your select statement, it sayas invalid object. i tried to run it against master, msdb and my dev DB but did not work. and the reference link also did not work. When i click no that there are 2 more links and further i clink on those link it says... no additional information available. Do you what i am missing? Thanks, Shalin
July 18th, 2011 4:07pm

try this on msdb: select * from syssubsystems maybe a SSIS re-install solve it.http://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 4:18pm

Yes actually there is not entry for 11. Now how can i add it or fix this issue? Thanks, Shalin
July 18th, 2011 4:27pm

try to re-install SSIShttp://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2011 4:36pm

Alright. I will do that. IS there any way to run SSIS packge by T SQl statement? I really appreciate all your help!! Shalin
July 18th, 2011 5:22pm

Alright. I will do that. IS there any way to run SSIS packge by T SQl statement? I really appreciate all your help!! Shalin you can run it with DTEXEC command line, http://msdn.microsoft.com/en-us/library/ms162810.aspxhttp://www.rad.pasfu.com My Submitted sessions at sqlbits.com
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2011 2:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics