Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbradish
Starting Member
24 Posts |
 Posted - 2010-01-08 : 16:43:33
|
| Could someone please tell me how to upgrade my Microsoft (R) SQL Server Execute Package Utility (MSSEPU)? I have two SqlSrv, both running SSIS 2008 MngSt v10.0.2531 with SSIS v10.0.1600. However, the MSSEPU versions are different.Srv1 --> is running Pkg Util v9.00.3042.00 for 32-bitSrv2 --> is running Pkg Util v10.0.2531.0 for 32-bitSrv1 was upgraded from SQL05. Srv2 was a fresh install.All of my SSIS packages on both servers run fine via scheduled jobs or the MSSMS SSIS "Run Package" menu. However, only Srv2 will execute the following code without error:DECLARE @i_Result intEXEC @i_Result = xp_cmdshell 'dtexec /SQL "\SSISfolder\PackageName" /SERVER Srv1'PRINT @i_ResultWhen you run this script on Srv1, you get the following error:Could not load package "\MSDB\SSISsfm\ImportForecast" because of error 0xC001404A. Description: While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80040E14 (Could not find stored procedure 'msdb.dbo.sp_dts_getfolder'.).The only difference between server config I can come up with so far is the MSSEPU version. Any help would be appreciated. |
|
|
dbradish
Starting Member
24 Posts |
Posted - 2010-01-11 : 17:45:08
|
| SOLUTION: Apparently SQL Server 2005 was still installed on Srv1. After uninstalling all SQL2005 components, the MSSEPU version is now reporting 10.0 and the dtexec is running without error. (I did not re-install any SQL2008 components.) |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-11 : 17:49:04
|
v9.00.3042.00 is SQL Server 2005.Maybe you have two folders where dtexec is stored - one maybe in ..\90\DTS\ and another in ..\100\... and your PATH points to the older dtexecOr you have no newer dtexec. In this case you should install again.
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-11 : 17:50:29
|
Aah - too late.But fine that it will work for you now 
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
dbradish
Starting Member
24 Posts |
Posted - 2010-01-12 : 08:15:36
|
| Just out of curiosity, where is the path that "points to the older dtexec" stored? I am working on live production servers so uninstalling software that may be in use by some unknown object was not my first choice. Thanks to Arshad Ali on http://www.mssqltips.com/tip.asp?tip=1893 for providing a nice little chart showing how the procs changed names between 2005 and 2008. It confirmed my suspicion that SQL08 on Srv1 was continuing to use old SQL05 files. |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-12 : 08:46:37
|
PATH is to find in environment variables.
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
Execute Package Utility Version & dtexec Command