I am also getting the same error and I can not get rid of it.

I have 5-6 pkgs that uses the same Connections so I created DataSourceat Solution Level and in Connection manager used "New connection from DataSource"

It is annoying and I can't seem to find a way to get rid of this..

I edited all the pkg config file and still.....

Easiest way to get rid of it? Delete the connection managers, then recreate them without using the data source.

I too ran into this issue. Here is what I discovered. The <project>.dtproj project file is an xml file which contains connection string information about each of your Data Sources. So, if you change the data source information in a package but not in the project file, you will get the "Synchronization..." dialog everytime.

Here's the really cool part. So what I have done is created a "Configuration" in the project for each of my deployment scenarios (development, QA, staging, production.) When I created the configuration I copied the previous configuration. Next, I opened the <project>.dtproj file in notepad (or your favorite xml editor because there is no IDE that enables you to work with the details of the configuration) and modified the connection strings for each configuration to match my deployment scenario. Now all I need to do to switch connections in my data sources is to change my configuration for my project!

There is an even easier way. Just delete the value in the DataSourceID property. That seems to break the link to the data source.

i guess it is not connection manager configuration issue. Delete and Recreate is not a good solution. I guess SSIS has cache issue. Once we change the connection manager it will not refresh.
Anyone know how to clear cache memory for SSIS packages in Visual Studio. sometimes if we restart system it works but sometimes even that will not help.

Please provide me option to refresh cache or buffer so that it will point to new connection.

Thanks in advance

Ramana Cheripally

i guess it is not connection manager configuration issue. Delete and Recreate is not a good solution. I guess SSIS has cache issue. Once we change the connection manager it will not refresh.
Anyone know how to clear cache memory for SSIS packages in Visual Studio. sometimes if we restart system it works but sometimes even that will not help.

Please provide me option to refresh cache or buffer so that it will point to new connection.

Using SQL Server 2008 and this issue is still present. Is this 'normal' behaviour or what. I supposed that Microsoft should have solved this.  Not using datasources doen't seem a solution to me. Why is it developed like this way anyway?

Greetz,
Hennie

Can you tell me where the DataSourceID property is that I'm suppose to delete?  This seems to work, but it's a pain to do for every connection manager.  I found you can also, repoint to a different data source, then point back and that fixes as well.  Neither are good solutions.

Any resolution on this?  I have the same problem and a huge solution with tons of connection managers and data sources all pointing a master config project where I should be able to edit them all.

 

Thanks in advance if you have anything.

Hi Jamie,

Could you explain how you do that. At this moment I'm having the same problems with the "Synchronize Connection Strings" Msgbox.

Regards,

Mark

I ran into the same issue but fixed it without deleting or recreating anything.  The problem is, the 'new' and 'old' connection strings may NOT be identical.  "Data Source=LocalHost" is different than "Data Source=localhost" I found. 

When you get the popup mentioning the sync issue, copy down the 'old' connection string in notepad or something similar.  Highlight it, and copy.  You should now have the 'old' connection string in your clipboard.  Next, double click the Data Source in the Project and where it displays the Connection String, click the arrow to view the available drop down list and select the <Paste from Clipboard> option.   Click ok and save your project. 

Reopen the project and load any of the packages that you were previously having problems with.  It should no longer display the sync message.

 

Jeff.

Well i had the same problem today and i think i found a "solution"

The Old Connection String is stored on dbo.SSIS Configurations....on the Database u use as source for dimensions...at least this was my case....i changed it and Voila....hope it Helps

Sorry to resurrect such an old thread, but I recently had to do some work on a 2005 project that uses Data Sources and package configurations. The issues described in this post were annoying, so I identified the exact issue and resolved it. I didn't remove the Data Sources as suggested here because I needed to change as little as possible but, I was tired of seeing the warning everytime I opened a package.

The project file persists the connection strings for its Data Sources in its *.dtproj file. The package persists the connection strings for its Connection Managers in its *.dtsx file. When the two do not match, you receive the message described in this post. When they match, no problem. The issue will arise when your package uses an underlying configuration, e.g. SQL Server or XML configurations, and it overrides the package's Connection Manager connection string to a value that does not match the Data Source. Visual Studio compares the package Connection Manager connection string with the respective project's Data Source connection string, and tells you it's going to update the Connection Manager connection string with the value of the Data Source's connection string.

This is very misleading because the value in "Old Connection String" is actually your current and correct value (pulling from your configuration source and reflected in the packages Connection Manager) and the value in "New Connection String" is the value persisted in your project file, in most cases your old and incorrect value. To top it all off, when your package runs it will use the value from your configuration source, i.e. the correct one. So this is good, just confusing; if you open the Data Source or Connection Manager connection it still displays the incorrect value persisted in the project file.

To resolve this annoying issue without having to touch every package, I opened the project file in notepad and updated the respective connection strings to match the current values in my configuration source. This is a simple, short-term fix. Obviously, if your configuration source or its values change, you will have to update your project file to match. In the example below, I highlighted the Id and Name of the Data Sources. The value you will want to update is the connection string value inbetween the <Value /> tags.

If you have the luxury of time and autonomy with your legacy project, then removing the Data Sources altogether is a better approach.

• Edited by binyacom Thursday, September 19, 2013 8:00 PM Typo & clarity

I had the same issue.

Found out that in the SSIS Package Configuration, I had specified not only the connection string but the whole branch of configurations for the datasource.
Once I put the configuration to only include the connection-string, the error message disappeared.