The SSIS packages I am working with were created in Visual Studio 2010 Ultimate.
In my SSIS solution, I have a project level connection manager named 'SSISConfiguration.conmgr'. It is configured to use the 'Native OLE DB\Microsoft OLE DB Provider for SQL Server' provider. The server name is 'mstn-dsql02\sql2005'. The database name is 'Configuration'.
The connection manager can correctly connect to the database server & database. I have a system Environment Variable configured on my Windows 7 machine set up as follows:
Name: SSISConfigurationConnectionString
Value: Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Configuration;Data Source=mstn-dsql02\sql2005
In my configurations I have created an Environment Variable package configuration that points to the connection string of my connection manager. Once I have finished creating the package configuration, I get the following error message if I attempt to go back and edit the configuration:
TITLE: Microsoft Visual Studio
------------------------------
An error occurred while a configuration was being edited.
------------------------------
ADDITIONAL INFORMATION:
The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[SSISConfiguration].Properties[ConnectionString]'. (Microsoft.DataTransformationServices.Design)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%C2%AE%20Visual%20Studio%C2%AE%202010&ProdVer=10.0.40219.1&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ConfigObjectNotFound&LinkId=20476
I've taken several steps to troubleshoot, and I cannot figure out why I am having this issue. Does it have something to do with having a backslash in the server name? I've noticed that when I set up the connection manager that the editor will change the backslash to an underscore. But then when I rename the connection manager, it is renamed in the editor, and in the .conmgr file.
I've also noticed that If I create the same connection manager in the control flow, that the 'Scope' property of the connection manager in the Package Configuration Wizard is zero (0). My project level connection managers have a scope of 1. Does this have anything to do with the issue?
Thank you for your help.
cdun2