.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Package moved from R2 to 2008 won't run because of ADO

Posted By:      Posted Date: September 19, 2010    Points: 0   Category :Sql Server

Put an ADO destination in a package under R2, move it to a 2008 (non-R2) system, and it won't run, complains yada yada about some connection.  This article documents a workaround:


My questions are two.  First, if I do this workaround, does it still work the same, does it still use bulk insert when possible?

Second, isn't a more elegant workaround possible, just loading the newer ADO driver on the 2008 (non-R2) system?  Or will that break a bunch of old 2008 packages or have some other nasty side-effects?



View Complete Post

More Related Resource Links

Easy install package vs MsSQL server 2008

Is there anything i wont be able to do if i use SQL Server Express Database from the downlod install package offered on asp.net? Ive used MSSQL server 2008 and 2005, but to be honest i think it might be overkill cause im not very familiar with those applications. I just need the database for creating websites. Will i be able to remote connect to my webbhotel host and remotely modify the database on the remote server?Now i have a mess, i have installed both MsSQL 2005 and 2008 and im not even sure wich database is created with what. I would love to just have one simple setup, but im not sure if i can manage to migrate the databases to the new computer with this easy install package.The easy install package contains: ASP.NET and ASP.NET MVC Visual Studio 2010 Express Development Tool SQL Server Express DatabaseThanks for your time!

How to create a SSIS package to import records form SQl Server 2008 tables to text files

I am a newbie to SSIS and would like to create a package to accomplish the task referenced in the above title. Will appreciate any links and pointers in the right direction.   Thanksakoranteng

SQL Server 2008 R2 Express Bootstrapper Package for Setup Projects

Has anybody got a workaround for the issue mentioned here: https://connect.microsoft.com/SQLServer/feedback/details/560030/sql-server-express-2008-r2-bootstrapper-package?wa=wsignin1.0 ?    

Package Configuration Problems SQL 2008 R2

I have an SSIS package that is using a SQL Server configuration to store connection strings for the other connection managers used by the package.  The connection string for the connection manager used to get the SQL Server configuration data is passed to DTExec when the package is executed.  The SQL configuration sets the values of variables that hold the connection strings and the connection managers use the variables in an expression to set the connection string.  I'm doing this so that I can move the packages from dev to qa then to production.  I also need to have the child packages use the same connection strings as the parent package so each child package has a parent package variable configuration containing the connection strings.  It uses these to set the values of child package variables which are then used to set the connection string property of the connection managers using an expression. I tested my packages by connecting to the development SSIS server, clicking on the package and selecting run package.  I select the connection managers tab so that I can change the connection string of the connection manager that points to the SSIS Configurations table which contains the development connection strings.  This works great. I deployed my packages to the production server and again tested the packages by running them from the pr

SSIS 2005 & 2008 BIDS and VS2005/2008 Will VS2010 work with either SSIS package?

I've read the old posts about having to have the BIDS version match the SSIS package version. My question is with VS2010 is there any change? Can I edit either of the old versions of SSIS packages in VS2010 or do I have to have 3 versions of Visual Studio/BIDS on my machine? TIA J

SSIS 2008 - Excel Source using SQL Connection cancels as soon as package runs.

Let me preface this by saying I'm brand-new to SSIS development. I'm using 64-bit SSIS 2008 and I'm trying to read an Excel spreadsheet using OLE DB. I've already run into and corrected the Run64BitRuntime problem.  Now when I invoke the Package it cancels immediately with the following output: SSIS package "Lesson1X.dtsx" starting. Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning. SSIS package "Lesson1X.dtsx" finished: Canceled. The program '[5400] Lesson1X.dtsx: DTS' has exited with code 0 (0x0). When I edit the Excel Source component itself there are no errors and I am able to Preview the results successfully.  If I use Table or View to access the file, the package runs successfully. Any suggestions will be greatly appreciated. Thanks

accessing package level variables in a Script Component in 2008 version


how to access the package level variables within a script component in SSIS 2008

SSIS Package / SQL Agent Job never ends on SQL 2008 R2



I have run into a strange problem and hoping someone may have a suggestion.

We have a set of SSIS packages that are developed in BIDS 2005. The packages are all executed by SQL Agent Jobs on a scheduled basis. These packages have been running on numerous SQL 2005 instances for the last year or so with no issues being experienced.

We recently has our first customer start running SQL 2008 R2 and we have internally upgraded to SQL 2008 R2 in our development environment. We are not converting the packages to SQL 2008 as we still need to support customers who are running SQL 2005. The problem is that in both our dev environment and at this particular customer, we have seem a random issue where the SQL Agent job never seems to end. Most of our jobs normally execute in less than 2 minutes, but occasionally (one or twice a week) a random job will just not end until we manually cancel it. We don't know if it is the SSIS package that is not ending or the SQL job.

We never experienced this on SQL 2005.

Anyone have any ideas what may be causing this? Any suggestions for troubleshooting?

Any help will be much appreciated


Craig Bryden - Please mark correct answers

SQL Server 2008 R2 Installation Problem - The language ENU is not supported by this setup package.


I am trying to install SQL Server 2008 Standard R2 on a Windows Server 2008 R2 64bits machine (all updates applied)... 

I run the setup.exe on the command line and I get the following error :

The language ENU is not supported by this setup package.
An error occurred during the SQL Server 2008 R2 Setup operation.

Error result: -2067529698
Result facility code: 1220
Result error code: 30

For more information, review SQL Server 2008 R2 Setup logs in your temp folder.

There is no log generated.

My regional settings + locale are all English-US

Any ideas?



Cannot download Cumulative update package 2 for SQL Server 2008 !


Hi all,


I currently need to install Cumulative update package 2 for SQL Server 2008 service pack 1.

It is located at :


When i click on View and request hotfix downloads it has the following error :

Unfortunately it says "The system is currently unavailable. Please try back later"


Where can i fin this package ?


I need to install this to finish off the installation of Sharepoint 2010.


SQL Agent - Running SSIS Package - Windows Server 2008/Windows 7 - Messenger Services


We have tried to run a SQL job for SSIS Package. But it failed during the execution with the error "[364] The Messenger service has not been started - NetSend notifications will not be sent". But in the job, no notifications have been configured and in windows server 2008/Windows-7 there is no messenger service at all.

When we search for the the messenger service in windows 7/windows server 2008, we found that service is not in both the OS and it was replaced by msg.exe. 

Any help or workaround would be appreciated.

Thanks in advance.

PS: The normal SQL jobs other than SSIS are working fine without any error.

Vijay Pandurangan

BIDS Error loading 'Package.dtsx' in 2008


So everything was working grand. I had both SQL2005 and 2008 installed and were working together just fine. Then I installed 2008R2. And everything was still fine minus the fact that I couldn't run anything with the dtexecui.

I have 2 computers that mirror each other in what's installed on them. SQL2005/2008/R2 were installed on both of them. Then when I started having package issues, I uninstalled R2.

Computer A works fine. After I uninstalled R2, I reinstalled the components from the sql2008 disk and packages work/open/run with dtexec/ui

On Computer B (which is the more important one of course) I get this error when trying to open a package (in bids).

Error    4    Error loading 'Package.dtsx' : Could not load type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackageSigning100' from assembly 'Microsoft.SqlServer.DTSRuntimeWrap, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91'..

And then it gives me the little red x in the right corner.

I tried re-registering everything based on this post http://social.msdn.microsoft.com/Forums/en-IE/sqlkjsetupandupgrade/thread/5ed7480b-2ca5-48de-bd3b-4b3752237c31 and that didn't work.

Then I uninstalled SQL2008, reinstalled, applied SP1, it still didn't work. Then I re-registered things again and it still d

BIDS 2008 hanging when opening package


Ideas are extremely welcome here.

I have a fresh install of windows 7/64, sql 2008 sp1, visual studio 2008 sp1. Fresh as of last week. BIDS installed just fine - nothing to worry about there. Everything was working fine with my packages and then suddenly now they practically won't open.

If they decide to open I get the nice little "Visual Studio is busy - if you encounter this problem often please report this to Microsoft" error in my tray while it's trying to open. So I wait. And finally it will open but I can't do anything. On all of them DelayValidation = True.  It does this both on "Work Offline" and "Work Online". And thing is they were working just fine. I imported them into a new project. Same deal.

When I restart my computer and try to open them again I get the same response. I've nuked my suo file before opening every time. Same deal though. I don't have any addon installed (no resharper - no bids helper).

Visual Studio isn't pegging the processor or ram - just what I normally would see.

Is there some magic setting that I need to flip to make them work again?


'Package.xsd' Error when creating a Slipstreamed, Prepared Instance of SQL Server 2008 R2



I am trying to create a Prepared Instance of SQL Server 2008 R2 using an install that is Slipstreamed to include SP1. I followed Option 1 as described here http://msdn.microsoft.com/en-us/library/dd638062.aspx and then was creating the Stand-Alone Prepared Instance as described here http://msdn.microsoft.com/en-us/library/ee210664.aspx. The System Configuration Checker passed with no errors, and then I hit this error:

SQL Server Setup has encountered the following error:

The element 'Package' in namespace 'http://www.microsoft.com/sql/slp/Package.xsd' has invalid child element 'Rules' in namespace 'http://www.microsoft.com/sql/slp/Package.xsd'. List of possible elements expected: 'Properties, Datastore, Extensions, MsiPatches, RuleGroups, Sequences' in namespace 'http://www.microsoft.com/sql/slp/Package.xsd' as well as any element in namespace '##other'.

Error code 0x84B10001.

Any ideas as to the problem and solution?






Schedule problem with SSIS package on SQL Server 2008

Hello there

Step 1 - I created my first SSIS package (simple ole db source to file destination scenario) in BIDS 2008. I created and run this on the SQL Server 2008 - SP1(on Win2k3 SP2 - 64 bit machine). This integratin scenario creates a flat file with some records in it (records modified today). This packages runs ok from BIDS.

Step 2- After deploying this SSIS package to the SQL Server 2008, I was able to run it successfully. The package created a flat file with some records.

On the two occasions above, the ssis package did exactly what I wanted it to do.

I tried to create SQL Server Agent job selected the Type as SSIS package, allowed this package to run under Windows Authentication (service account - same account used as in Steps 1 & 2). Before scheduling, I thought why not run this manually. The job ran successfully (looked at the success message and the history of the job), but a flat file was created (as expected) without any records (not as expected!)

Please note I have tried the default protection level ("EncryptSensitiveWithUserKey") as well as ("DontSaveSensitive") on the package.

I am suspecting that when the SSIS package is scheduled the SQL Server Agent is unable to pass the authentication to the SSIS package !?

Some help will be appreciated.


Cannot Install Microsoft Visual C++ 2008 SP1 Redistributable Package (neither 32 nor 64 bit)


I'm trying to download Microsoft Visual C++ 2008 SP1 Redistributable Package and I keep getting this error message:

Error1935.An error occurred during the installation of assembly ‘Microsoft.VC90.ATL,version=“9.0.30729.1”,publicKeyToken=“1fc8b3b9a1e18e3b”, processorArchitecture=“x86”,type=“win32”’. Please refer to Help and Support for more information. HRESULT: 0x080070424.

I'm not sure what to do, if anyone could help me through this I would really appreciate it.

SSIS package runs very slow on SQL 2008 R2 server, runs very quickly on virtual XP machine


Hi All,

I've been troubleshooting this issue on and off for a few weeks now.  I've scoured these forums and looked through sqlis.com, but I'm just about out of ideas.  Here's what's happening.

I have a *very* simple integration services package I developed on a  virtual Windows XP machine running on my workstation.  The package uses a script task to simulate a one-row source with four columns (int, char(64), varchar(512) and char(2)) and then passes that off to a fuzzy lookup.  The fuzzy lookup is running against a table of only about 6,000 rows.  The package then inserts the results into a table and exits.

When I run this from my virtual XP machine, it completes in 1-2 seconds.

When I execute this on the server (either as a job or through DTExec) it takes 14-18 seconds.  The server stores the package in MSDB and is also the location where the fuzzy lookup happens.

I've tried using the 32-bit runtime, creating 32- and 64-bit aliases to the server, changing the name of the server from the name to the IP address and port, stopping/restarting SQL Agent and SSIS Services... none of this seems to change the execution time.

The one thing I've found is that if I enable package logging on the logging tab of the job, using the SSIS Log Provider for SQL Server and pointing it to the same connection st

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend