December 1, 2008 at 11:53 am
I designed an SSIS package it runs from Visual Studio 2005 will not run from SQL Job agent or from Execute Package utility
December 1, 2008 at 12:04 pm
I have to ask, what edition of SQL Server 2005 are you using?
December 1, 2008 at 12:09 pm
SQL Server 2005 Standard edition
Microsoft SQL Server Management Studio9.00.1399.00
Microsoft Analysis Services Client Tools2005.090.1399.00
Microsoft Data Access Components (MDAC)2000.085.1132.00 (xpsp.080413-0852)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.5512
Microsoft .NET Framework2.0.50727.1433
Operating System5.1.2600
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727 SP1
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41475
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41475
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41475
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41475
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0000007-41475
Microsoft Visual Web Developer 2005
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB937060)
This Security Update is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this Security Update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/937060
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.1399.00
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
December 1, 2008 at 12:18 pm
You are getting an edition error. This basically means you are running a package containing a component that is only allowed on a higher edition of SSIS than what you have installed an running.
You say you have the Standard Edition of SSIS running, so I will assume that is the case.
Is it running on the machine the execute package utility is running on? You have to double-click it from the server - SSIS does not have a built in remote execution utility, so if you run the package with the execute package utility or the command line from your workstation, you must have the appropriate edition of SSIS installed on the WORKSTATION, not the server the package is being stored on.
The same goes with the SQL Agent - if you installed SSIS on one server and MSSQL on another, the SQL Agent on the second server cannot run packages. Since the SQL Agent is running on the server that SSIS is not installed on, it cannot run anything beyond the basic maintenance plan tasks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply