I have a script component in a data flow of my SSIS pacakge that uses the package connection manager to connect to the database. Up until now, the connection manager was using a trusted connection to a local SQL Server and was working fine.
I had to switch the connection to non-trusted and use a SQL account to access a development SQL Server on another domain and now my script component won't validate giving me the error: "Login failed for user 'SSISUser'"
Other components in the same package are able to access the data using the same connection manager with no problem (e.g. an OLEDB Source).
Code in the Script task is establishing the connection to the SQL Database like this (FYI...Connections.UtilityConnection.Connectionstring is the reference to the SSIS Connection Manager):
oledbConn = New OleDbConnection(Connections.UtilityConnection.ConnectionString)
oledbConn.Open()oledbCmd = New OleDbCommand
oledbConn.Open()oledbCmd = New OleDbCommand
Is there a reason that the code in the script component can't use a non-trusted connection or is there some other way I should be establishing the connection?
FYI...The connection string is coming from a configuration file and I have confirmed that the connection manager is being configured when the package loads.