rmarshall82
asked on
Executing SSIS package with Execution utility, "send mail" task cannot run on this edition of integration services. It requires a higher level edition.
Environment: SQL Server 2005, Business Intelligence Studio 2005, Windows XP.
When running the package in Visual Studio, it executes with no problem. When trying to execute from Integration services, or from Windows scheduled task, I receive the error above: "cannot run on this edition...."
Any ideas on how to get the package to run?
When running the package in Visual Studio, it executes with no problem. When trying to execute from Integration services, or from Windows scheduled task, I receive the error above: "cannot run on this edition...."
Any ideas on how to get the package to run?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try this, Create a SQL Server Agent job on the server that will execute the package that you have created.
Here are the steps (assuming you know how to schedule jobs on SQL Server):
1. Create and save your SSIS package on the server
2. Open up SQL Mgt Studio and under SQL Server Agent cerate a new job.
3. In the job create a step and choose the step type as "Transact-SQL Script"
4. Type this in the SQL Query box: EXEC xp_cmdshell 'dtexec /f "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Imp ortManulif eData\Pack age.dtsx" '
5. Save and close the job wizard.
6. Run to see if it works.
Also, please note the EXEC xp_cmdshell, the path is subjective to where you store your package.
Hope this helps.
P.
Here are the steps (assuming you know how to schedule jobs on SQL Server):
1. Create and save your SSIS package on the server
2. Open up SQL Mgt Studio and under SQL Server Agent cerate a new job.
3. In the job create a step and choose the step type as "Transact-SQL Script"
4. Type this in the SQL Query box: EXEC xp_cmdshell 'dtexec /f "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Imp
5. Save and close the job wizard.
6. Run to see if it works.
Also, please note the EXEC xp_cmdshell, the path is subjective to where you store your package.
Hope this helps.
P.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER