Edwin M SarmientoUpgrade – Edwin M Sarmiento https://www.edwinmsarmiento.com Intentional Excellence Mon, 13 Apr 2026 21:00:49 +0000 en-US hourly 1 84283043 Watch Out for Microsoft TechDays Canada 2011 https://www.edwinmsarmiento.com/watch-out-for-microsoft-techdays-canada-2011/ https://www.edwinmsarmiento.com/watch-out-for-microsoft-techdays-canada-2011/#respond Thu, 20 Oct 2011 19:04:54 +0000 Edwin M Sarmiento http://bassplayerdoc.wordpress.com/?p=499

If you happen to be in Canada, you probably have heard about Microsoft TechDays – the premier technical conference for IT professionals and developers. This year, three cities – Vancouver, Montreal and Toronto – will be hosting this 2-day event. Two years ago, I did a presentation “on SQL Server on Hyper-V” as well as “free/cheap tools for IT professionals.  This year, I will be delivering a presentation on Upgrading to SQL Server R2 and SQL Server “Denali” (now officially announced as SQL Server 2012) in Toronto on the 26th of October 2011. If you’re in town, let’s catch up for a cup of coffee as I will be at the Data Platform booth the whole day (except during my presentation) answering questions and providing guidance on how you can maximize your investments on the SQL Server platform. I’ll see you there.

]]> https://www.edwinmsarmiento.com/watch-out-for-microsoft-techdays-canada-2011/feed/ 0 499 Watch Out For SSIS Package Migration/Upgrade Errors https://www.edwinmsarmiento.com/watch-out-for-ssis-package-migrationupgrade-errors/ https://www.edwinmsarmiento.com/watch-out-for-ssis-package-migrationupgrade-errors/#respond Sun, 19 Jun 2011 03:09:00 +0000 Edwin M Sarmiento http://bassplayerdoc.wordpress.com/2011/06/19/watch-out-for-ssis-package-migrationupgrade-errors After successfully upgrading a multi-instance SQL Server 2005 Failover Cluster to SQL Server 2008 R2, I got woken up today by a page from a SQL Server Agent job failure. Knowing that the job was created by one of my colleagues, I ignored it for a while since it only runs once a week and is not really that critical since it only performs tasks for reporting purposes. However, I just can’t seem to get it off my head that what seems to be a successful upgrade caused some issues on the SQL Server Integration Services (SSIS) components. I checked the SQL Server Agent Job History for more information but only found this bit of information in the error log

The package failed to load due to error 0xC0010014

After a quick search on Google, I found this blog post on the MSDN Blogs site that explains what could be a possible cause for the error. While the blog post defined a different error number from the one I had, I was sure that this was it. Knowing that I had SQL Server 2005 Failover Cluster before, I had a feeling that the DTExec.exe executable file was still hanging around. True enough, I saw the EXE file. And the SQL Server Agent job that failed points to the old version of the DTExec.exe file. I immediately changed the path from within the SQL Server Agent job to point to the new version of the DTExec.exe file. The command which points to the old path looks like this
C:Program Files (x86)Microsoft SQL Server90DTSBinnDTExec.exe

After modifying the path, I now have this

C:Program FilesMicrosoft SQL Server100DTSBinnDTExec.exe

One thing to look for after upgrading a SQL Server 2005 instance to SQL Server 2008/R2 (whether it is a failover cluster instance or not) is to make sure that your SSIS packages are reconfigured to point to the new path of the DTExec.exe executable and test them accordingly 
]]> https://www.edwinmsarmiento.com/watch-out-for-ssis-package-migrationupgrade-errors/feed/ 0 233