![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. No quite sure though... Perhaps googling on this might help you further. |
#4
| |||
| |||
|
|
I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. No quite sure though... Perhaps googling on this might help you further. |
#5
| |||
| |||
|
|
I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. |

#6
| |||
| |||
|
|
Frans van Bree wrote: I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. You can compare the editions at http://www.microsoft.com/sql/prodinf...-features.mspx Only the standard and enterprise editions come with Integration Services (there're also express, developer and workgroup editions). The enterprise edition additionally has Integration Services Advanced Transforms, but I don't think that the file system task belongs into this group ![]() greetings, Gerald |
#7
| |||
| |||
|
|
Frans van Bree wrote: I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. You can compare the editions at http://www.microsoft.com/sql/prodinf...-features.mspx Only the standard and enterprise editions come with Integration Services (there're also express, developer and workgroup editions). The enterprise edition additionally has Integration Services Advanced Transforms, but I don't think that the file system task belongs into this group ![]() greetings, Gerald |
#8
| |||
| |||
|
|
I have the Standard edition installed. I can run the package just fine from Integration Services GUI, its just when I go to an Agent job that things stop functioning. Gerald Aichholzer wrote: Frans van Bree wrote: I believe this is a version problem. Read it somewhere some time ago. There are different version of SQL Server 2005, like there where in 2000 (standard, personal, msde). I believe that if you have SQL Server 2005 MSDE then it is not possible to schedule the command line executable of SSIS as a job. You can compare the editions at http://www.microsoft.com/sql/prodinf...-features.mspx Only the standard and enterprise editions come with Integration Services (there're also express, developer and workgroup editions). The enterprise edition additionally has Integration Services Advanced Transforms, but I don't think that the file system task belongs into this group ![]() greetings, Gerald |
#9
| |||
| |||
|
|
I have the Standard edition installed. I can run the package just fine from Integration Services GUI, its just when I go to an Agent job that things stop functioning. |
#10
| |||
| |||
|
|
Is your development machine (with the SSIS GUI) the same machine as SQL Agent is running? I found this post on sqlserver central, perhaps that helps you some more: Hmm... this error seems familiar. If memory serves, this would indicate that you're trying to run this from the command prompt instead of the BI Studio client tools. What this means is that you have the client tools installed on the computer you're trying to run this from, but not SSIS itself. I believe you need to run the SQL Server installer and just install SSIS on the computer you're trying to run this from... assuming my assumption that you're trying to run this from the command prompt is correct. I have the Standard edition installed. I can run the package just fine from Integration Services GUI, its just when I go to an Agent job that things stop functioning. |
![]() |
| Thread Tools | |
| Display Modes | |
| |