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

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

How to open the SSIS packge in 2005 which opened in 2008

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

Hi I have a package which was done in SSIS 2005 and I have opened that in SSIS 2008. I want to open this back in 2005 but its throwing an error. How to Open this package back in 2005.

The error message: Error 1 Error loading Package.dtsx: The version number in the package is not valid. The version number cannot be greater than current version number.  C:Processing\Operational Packages\Package.dtsx1 1 

View Complete Post

More Related Resource Links

Diffrences in SSIS 2005 and SSIS 2008?

Hi All,   How to convince interviewer in  major differences in ssis 2005 and ssis 2008.In my system I have ssis 2008.Can I install ssis 2005? How to install? Thanks CMK…

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

Copy SSIS packages from 2005 to 2008

I have both vs 2005 and vs2008 on the same pc. When i try to copy the package from the BIDS 2008 from file Copy as i get an error

 Storing or modifying packages in SQL Server requires the SSIS runtime and database to be the same version. Storing packages in earlier versions is not supported.

Do you know how to fix this issue.

Cannot open SSIS 2005 package


HI, one of developers gets the folowing error when he tris to open a SSIS 2005 pacjage:

Could not load type 'Microsoft.SqlServer..Dts.Design.IDtsPipelineEnvironmentService' from assembly 'Microsoft.SqlServer.Dts.Design. Version=

Is there something I can do to resolve this issue?

Thank you,

Christian Cote

SSIS on Cluster also 2005 packages and 2008 db connections and jobs?


Hi, multipart questions.

We have a SQL 2008 Cluster where we do not want to install SSIS.  We have a SQL 2005 SSIS instance on another server  for packages.

here goes

1. Can we configure jobs on the SQL 2008 custer to point to the 2005 SSIS instance? and do we need SSIS installed on the SQL 2008 cluster to do this?

2. Can we run jobs on a SQL 2005 instance, pointing to a SQL 2005 SSIS instance/packages on a third server that connect to a SQL 2008 DB instance . I know that sounds crazy, but where exactly is the CPU and memory load in that design.. job on one server, package a seperate server and db on a third server.?

3. As mentioned, I have SQL 2005 SSIS instance.  I have local admin on that server and can connect to the ssis instance from my sql 2005 sql client on my desktop.  I added a new user to the server and added them to the SSIS and users group. I also made sure they could write to the folder where they will deploy packages. However, they get some kind of access denied while trying to connect, unless I give them local admin on the server.  What more access do they need than to be in the users and SSIS group and have write access to an SSIS deployment folders?


Many Thanks.

Visual Studio 2008 and SQL Server 2005 SSIS packages


My home machine has sql 2005  and Visual Studio 2005 installed. I uninstalled VS 2005 (RTM) and installed VS 2008 (RTM) in its place. I then found that the SSIS templates were missing. Lesson: don't uninstall VS 2005 if you want to use SSIS 2005!


1. Is there any "workaround" to this issue?


2. (If the answer to 1 is "No") I will install VS 2008 side-by-side with VS 2005 on the same box.  When the SSIS issue is finally resolved, can I uninstall VS 2005 without doing damage to the VS 2008 install?










Executing SSIS 2008 in SQL 2005


I've created a SSIS package in SQL 2008. I tried running the package in SQL 2005 but was prompted with the error below.


"The version number in the package is not valid. The version number cannot be greater than current version number."

"Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number."


Is there any method that I could use to enable the package to be executed in SQL 2005?

SSIS 2005-2008 web service task limits



I'm finding some articles or white papers about the limits or incompatibilities of SSIS 2005-2008 web service task.

Any suggests to me, please? Many thanks

Merge Join in SSIS 2005 Vs 2008



I have a process which reads from 2 tables (using two connection managers) and "merge join" them to a third table by using left outer join.

This process is implemented on SSIS 2005 and SSIS 2008 identically, however, for some reason I get less records at the third table at the 2008 process.

When implementing this merge join on Sql Server 2008 and Sql Server 2005 I get the same result as I got at the SSIS 2005 process - so it seems like the problem is at the SSIS 2008 process.
I've checked the merge join properties - they look similar on 2005 and 2008.
Does anyone knows if the 2008 merge join object should be configured differently than the 2005 merge join?
I have nulls on some the fields that connect the two tables - do you think it's got to do with it?
What else can I check?

Using Conditional Split data Transfer in SSIS 2008

This article uses the Integration Services Conditional Split Data Transformation element to filter and transfer data from a set of flat text files to SQL Server database table. The concept can be easily extended to apply to any other source or destination such as Microsoft Excel. This scenario is useful in creating denormalized database tables in a reporting and analysis situation.

Converting Crystal Report 2005 to 2008 - Please Tell Me I'm Stupid :)


Hello peeps,

  I have a series of Crystal Reports that I can view/edit using Visual Studio 2005 with no issues.  The method I'm using is to simply click on the *.rpt file and it opens in the VS crystal editor with no issues.  The problem I'm having is that we are upgrading to Visual Studio 2008, and when I open the *.rpt file in 2008 it opens as a binary file.  I guess I'm used to everything else in Visual Studio prompting me to convert the older version to the newer version, so I'm not sure what to do in this case.

  Is this normal?  Is there an easy conversion method that I'm simply overlooking?  Am I screwed?  Who invented liquid soap, and why?

Answers to any of these questions would be greatly appreciated...

Convert 2005 RDLC to 2008 using VS2010


Hi and thanks.


I'm getting an error on serveral reports that I built  in VWD2005 (express) using the reportviewer control.  Trying to edit the rdlc file in VS2010, VS2010 asks if i want to convert the file to RDLC 2008 format and I click ok.  When I build the site, I get this error (and of course also when the report is ran):


Error 1 The report definition is not valid.  Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded. C:\inetpub\wwwroot\mastercardlcm\Reports\WorkLists\OpenSRStatus.rdlc 1 


Here is my web.config concerning the RDLC assemblies, etc.

			<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
		<compilation debug="true">
				<add assembly="Microsoft.ReportViewer.WebForms, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="Microsof

VS 2005 to 2008


Hi folks

Am in the process learning C#, My instructor uses Visual C# 2005 Express and on my side I have Visual Studio 2008 Pro.

Do you think it will affect me in my Coding practice due to the different IDE Versions? Wha do I have to heed when coding?



SQL server 2005 2008


i cant install sql server 2005 nor 2008 on my windows 7 os

i read about somthing like adding new account when installing sql 2008 to provision the server or so, but didnt know how,,,

can you plz help me??


Installed Visual Studio 2005 on new laptop - can't open C# web services project solution.

Installed Visual Studio 2005 on new laptop - can't open C# web services project solution - get the 'project not supported by this installation' error. Tried re-installing to no avail. Have run various flavors of devenv as recommended in various posts. Still the same message. I can open the solution fine on my old laptop.    Update: We re-installed service pack 1 for VS and the problem was resolved.

Issues with SSIS and SQL 2008 - Integration services not running

Hey guys, I installed SQL 2008 with complete BI studio including Integration Services. When i check in my services - i cant see my integraiton services in there When i try to connect to Integration Service using localhost, I cant connect it And when i try to run setup of SQL 2008 - It shows that Integration Services already installed and that what i checked when i fetched my Installation tool report from SQL Server to verify i have it installed. Why can i access Integration services, if i already have it, Please suggest with ideas, checks i can make to ensure every setting is in place. Thanks. Would appreciate for quick response.  

Output parameters in OLEDB Command component - SSIS 2008

I have a package that I developed in SSIS 2005 and recently ported to 2008. Everything runs great except an OLE DB Command component that calls a stored procedure that uses output parameters. When I try to run this, I get this error: Error: 0xC0202009 at Data Flow Task, OLE DB Command [100]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Syntax error, permission violation, or other nonspecific error". Error: 0xC004701A at Data Flow Task, SSIS.Pipeline: component "OLE DB Command" (100) failed the pre-execute phase and returned error code 0xC0202009. When I do the same thing in SSIS2005, it works fine. So I setup a new package with 1 data flow. In that data flow, I added a source component, an OLE DB Command, and a destination.  I then tested this with a stored procedure that took no parameters. It worked fine. I then tested it with a stored procedure with 1 parameter defined as OUTPUT. This generated the error.   Is there an issue with output parameters in an OLE DB Command in SSIS 2008?   Thanks!http://bobp1339.blogspot.com
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