Post reply

Copying package from one solution or project to another does not work

  • May 12, 2010 at 4:03 pm

    #140862

    I've created a package in a Project 'X'. When I run that package it runs fine without any issues. When i copy that package to a different project 'y' in BIDS it is giving me an error saying

    '[Excel Destination 1 [74105]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager 1" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. '

    I appreciate if some one can tell me what's causing that error.

  • May 13, 2010 at 1:45 am

    #1166682

    Hi,

    Ok... a few basic things you could check:

    1. Are projects X and Y on the same machine? Is the package able to access the Excel file from Project Y? Look at path issues, etc..

    2. After moving the package to Project Y, you could try double-clicking the data source and pointing to the file manually (by clicking Browse and re-selecting the file). Check if the error occurs again.

    3. Is the file in use? Try closing/re-open/re-run the package. Another way to ensure that the file is not in use is to install this tiny piece of software called Unlocker (http://ccollomb.free.fr/unlocker/). Once you install this, right-click on the Excel file and choose Unlocker. It will let you know the list of processes that are using the file. Once you kill those processes, re-open the package and try running it again. It should work.

    Regards,

    GS

  • May 13, 2010 at 10:05 am

    #1167025

    Hi, First of all thanks for the reply. I could resolve the issue. This is a popular runtime error on 64bit: "Class not registered"

    I was testing the package on a 64 bit machine. However, Office Excel (including most of the office products) does not have 64bit provider and hence the error above on Excel connection.

    To correct the issue, I changed the setting “Run64bitRuntime” from True to False in the project properties dialog page, the error was gone.

    Thanks once again.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply