pkg goes down because a connection cant be found

db042190 1,516 Reputation points
2020-08-26T22:22:34.637+00:00

hi we run 2014 standard and develop in vs 2013.

i deployed a pkg that has no connector called xxxxxxxx.yyyyyyyyyyy but i get the error the connction xxxxxxxx.yyyyyyyyyyy is not found...oxc001000e...this error is thrown by connections collection when the connection is not found.

i cut out all my configs. searched the code for xxxxxxxx.yyyyyyyyyyy and its not there. i double checked the guid of the the object on which ssis is going down and its connector is a valid ado guid. i issued a new id guid for the pkg.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,502 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. db042190 1,516 Reputation points
    2020-08-26T22:30:50.373+00:00

    i created a separate project, copied the original into a pkg there, did a build after changing the prot level and got no errors.

    0 comments
  2. db042190 1,516 Reputation points
    2020-08-26T23:26:40.263+00:00

    i disabled the container in which the proc call is shown with the error in sql agent's job history and i get the same proc being referenced as calling the same invalid func called dbo.fn_SplitString. while i think that func is in clr, i added a t-sql version of it and still got that error. i always delete the pkg from sysssispackages before deploying. its as if vs is tacking some unwanted config stuff on at deploy or i'm executing old versions of the pkg.

    0 comments
  3. Yitzhak Khabinsky 25,721 Reputation points
    2020-08-27T01:16:42.74+00:00

    SSIS package files .dtsx are in reality files in XML format.
    So you can open up the SSIS package in question in any text editor like Notepad or Notepad++, and search there for the xxxxxxxx.yyyyyyyyyyy connection.

    0 comments
  4. Monalv-MSFT 5,896 Reputation points
    2020-08-27T01:27:23.267+00:00

    Hi ,

    May I know if you use the Protect Level Connection Manager in the package?
    If yes, please deploy the whole project, and then execute the package.

    A connection manager can be created at the package level or at the project level. The connection manager created at the project level is available all the packages in the project. Whereas, connection manager created at the package level is available to that specific package.
    You use connection managers that are created at the project level in place of data sources, to share connections to sources. To add a connection manager at the project level, the Integration Services project must use the project deployment model. When a project is configured to use this model, the Connection Managers folder appears in Solution Explorer, and the Data Sources folder is removed from Solution Explorer.

    Please refer to Package level and project level connection managers.

    Best Regards,
    Mona

    ----------

    If the response is helpful, please click "Accept Answer" and upvote it.

  5. db042190 1,516 Reputation points
    2020-08-27T11:16:00.467+00:00

    i think i found/deduced it. i either accidentally renamed or removed that connector before deploying. the familiar missing connector reference occurred. to top things off an expected clr function was missing and if i'm not mistaken ssis reported both errors.

    what really messed me up as i was trying different options was that i was reading the sql agent job history bottom up. so i kept seeing the same error from the same run over and over. and somewhere along the line i changed something that removed the missing reference from the xml so i had to deduce what happened.