I have an SSIS (super) package that consists of several (about) 40 packages, each of which has several data flow tasks, most of which load some excel data into the sqlserver database. Thus, I have several excel source connection managers, one per excel file. This always worked until recently: I have to change the excel source in one of my packages (the column was added to excel, which should be loaded into the target sqlserver table), but I cannot edit the excel source in SSIS: when I click on the "columns " I get a window with the error "DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER". So this is a development-time problem, not a run-time problem. I saw such a question in stackoverflow, but did not answer. Does anyone have an idea?
- I already deleted office 2007 and reinstalled office 2003 on my machine, but that didn’t help
- it has nothing to do with the 64-bit mode, which I read about here.
- Is there a limit on the number of connection managers in ssis?
- Most of my connection managers were created with copy / paste and therefore they have the same identifier, although they point to different excel files. Could this be a problem?
I should also note that the package works without any problems, so it only “edits / changes” the package that does not work. At the moment, I will get around this problem by disabling the data stream that is supposed to change, and replacing it with the sql statement, which rigidly inserted the data from excel into the destination table. Perhaps one more interesting thing: I can create a new package, add and modify excel sources without problems, but then again, when I try to copy this excel source to my package, I cannot edit it.
source share