SQL Server Developer Center >
SQL Server Forums
>
SQL Server Integration Services
>
Job does not start because of product version
Job does not start because of product version
- I have scheduled a package to run through the SQL Server Agent, and when the package is supposed to be executed, the job fails and the following is written in the job history:Executed as user: DOMAIN\user. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:05:05 AM Error: 2009-11-04 00:05:58.82 Code: 0xC00470FE Source: Accounts SSIS.Pipeline Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The component "Row Count" (738) cannot run on installed (64-bit) of Integration Services. It requires Standard Edition (64-bit) or higher.So the package throws the error on a simple row count step...the strange thing is, that on both the deployment server and the development machine I have the Enterprise Edition installed... and when I run this package in debug mode from my development machine, everything works allright.Any help is much appreciated!Thanks.
-
Answers
- so you are saying that it works in SSIS but wont work when you call the package through a Job? am i right?? if so
How are you calling the package though a Job ? please type the syntax.
check
http://technet.microsoft.com/en-us/library/ms139805(SQL.90).aspx
http://sqlserverpedia.com/blog/sql-server-bloggers/quick-reference-ssis-in-32-and-64-bits/
http://dougbert.com/blogs/dougbert/archive/2008/06/10/64-bit-considerations-for-sql-server-integration-services-final.aspx
http://msdn.microsoft.com/en-us/library/ms141766.aspx
Sincerely SH -- Please kindly don’t forget to mark the post(s) that answered your question and/or vote for the post(s)- Marked As Answer byYao-Jie Tang - MSFTMSFT, ModeratorWednesday, November 11, 2009 5:51 AM
All Replies
- What if you open the package and run in debug mode on the server? Are the server and your dev machine both 64bit?
- Hi Erik,
Can you give more details like which editions are using 32 bit or 64 bit ? Areusing any Excel connection in the Package?
Thanks,
SatBI http://Satishsharing.blogspot.com - so you are saying that it works in SSIS but wont work when you call the package through a Job? am i right?? if so
How are you calling the package though a Job ? please type the syntax.
check
http://technet.microsoft.com/en-us/library/ms139805(SQL.90).aspx
http://sqlserverpedia.com/blog/sql-server-bloggers/quick-reference-ssis-in-32-and-64-bits/
http://dougbert.com/blogs/dougbert/archive/2008/06/10/64-bit-considerations-for-sql-server-integration-services-final.aspx
http://msdn.microsoft.com/en-us/library/ms141766.aspx
Sincerely SH -- Please kindly don’t forget to mark the post(s) that answered your question and/or vote for the post(s)- Marked As Answer byYao-Jie Tang - MSFTMSFT, ModeratorWednesday, November 11, 2009 5:51 AM


