Excel Connection

Hi,
When I create an SQL connection from my workstation within an Excel file, other users are unable to refresh the data.
Error Message:
            “[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified”
The connection string being:
DRIVER=SQL Server Native Client 10.0;
SERVER=SQLSERVER;
UID=*ME*;
Trusted_Connection=Yes;
APP=Microsoft Office 2010;
WSID=0347;
But they are able to refresh the data if I create the connection from their own workstation.
The connection string being:
DRIVER=SQL Server Native Client 10.0;
SERVER=SQLSERVER;
UID=*OTHERUSER*;
Trusted_Connection=Yes;
APP=Microsoft Office 2010;
WSID=0348;
I can refresh any connection from my workstation regardless of who created it.
I need all users to be able to refresh files that I have created from my workstation.
Presumably the issue is the SQL Server credentials, but if someone is able to confirm this and offer a solution I’d be most grateful.

Hi Chris SE23,
According to your description, we need to verify if you want to connect to SQL Server database in Excel workbook. If yes, in the Data Connection Wizard, please ensure that they are right in the server name and logon credentials, we can also set advanced
properties for refreshing the connected data in Properties option. For more information, see:
http://office.microsoft.com/en-gb/excel-help/connect-to-import-sql-server-data-HA010217956.aspx
According to your error message, the problem is probably with the ODBC configuration on the Server itself, I recommend that you check if indeed you have a source (typically a "System DSN") with the same name found in the connection string. For example, source
is probably inexistent or improperly configured in the ODBC Data Source.
There is an example about how to make sure a DSN that has been created.
http://community.microfocus.com/borland/test/silk_test/w/knowledge_base/10737.how-do-i-resolve-error-im002-microsoft-odbc-driver-manager-data-source-name-not-found-and-no-default-driver-specified.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Similar Messages

  • Excel Connection Manager suddenly can no longer connect to Excel from SSIS package

    <p>During the last 3 months, I used 32 bit SSIS 2008 (v 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results (reports) to an excel spreadsheet. Each report is written to a different
    tabbed sheet in the same spreadsheet. </p><p>The package was&nbsp;working just fine until May 9 2013, when suddenly every single&nbsp;Data Flow task with an Excel Destination&nbsp;displayed error icons and raised the&nbsp;following
    error message when opening the Advanced Editor:</p><p>SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". <br />Error at &lt;DataFlow task name&gt;: SSIS
    error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager &lt;Excel connection Manager&gt; failed with error code 0xC0202009. There may be error messages posted before this with more
    information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)</p><p>Originally the error message reported that the Error Code was "0x8000FFFF", but I can't seem
    to reproduce that error code since. Now I am only getting the above error message.</p><p>From the time I created the original package (when it worked fine) until now, I have been using the same computer, writing to a (32 bit) 2010 Excel file in
    a local folder. The filename and location have not changed. The ConnectionString has not changed. The Connnection String I am using is Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion Results_dt01.xlsx;Extended Properties="EXCEL
    12.0 XML;HDR=YES;". </p><p>Now an attempt to create and test a NEW Connection Manager yields me this error. "Test connection failed because of an error in initializing provider. Unspecified error.",&nbsp; whereas before I had
    no problems creating a new connection manager.</p><p>I checked a second SSIS package, which I also built during the past 3 months, which loads multiple sheets from multiple Excel files to a SQL Server 2008 database holding table. It uses the same
    ACE OLE DB 12.0 connection to load the Excel speadsheets and this package continues to work fine on the same workstation.</p><p>In desparation, wondering if the Microsoft ACE OLE DB 12.0 driver had become corrupt (even though the second package
    was raising no errors), I did download and install the Microsoft ACE OLE DB 12.0 driver.&nbsp; That did not solve my problems with the first package.</p><p>I need to get this package running again ASAP as it is targeted for UAT testing in a
    matter of days. Any help with this issue would be greatly appreciated!</p>

    I submitted this issue above and now I am having the same problem again. I am using the same local computer, the same operating system (WinXp v 5.1.2600 SP3 Build 2600) as originally described. I am working with the same SSIS package that
    writes multiple query results (reports) to an excel spreadsheet. This package has been successfully executed multiple times, but now I am suddenly getting the same error as follows:
    Error at 1ConversionContacts [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
    Error at DFlow Write soft deleted duplicate claims to Excel sheet [Excel Destination - write duplicate claim nbrs that have been removed to Excel [61]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method
    call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    The package will not run because of these multiple errors (multiple because it occurs on every single excel destination in the package).
    I have Run64BitRuntime set to false on the project. I have triple checked that the excel file name (which I created and can access) exists with the correct name in the correct path, which is local on my machine. The file is the same file in the same
    location as when the package worked.  I am running the SSIS service under my own network login, as I was when the package worked. I have been consistently getting this same error whenever I change my network password without updating the password
    in the SSIS service, but I have triple verified that the service is using my latest password. If I try to open and edit the Excel Destination in any DataFlow task I get the same error. I can successfully create a new Excel Connection Manager pointing
    to the same excel file. However if I try to assign the newly created Excel Connection Manager in the data flow, I cannot activate the drop down to choose the Excel sheet without getting an 'Unspecified error' message. I then swapped out
    the file with its template version, and ensured the name was updated as correct. I still get the same errors.
    Oh, and the SSIS package is extracting data from a SQL Server 2008 database with an ADO.net Connection Manager using Windows authentication. I have no problems with the SQL Server connection, it has always worked and still does.  It is only
    the connection to excel output file which is locally stored on my machine.
    Has anyone got any suggestions for me?

  • SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

    Hi,
    This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
    Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
    So far I have installed
    http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
    I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
    2012 release.
    Here is the detail of error message:
    TITLE: Package Validation Error
    Package Validation Error
    ADDITIONAL INFORMATION:
    Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection
    Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
    Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
    Error at Data Flow Task: There were errors during task validation.
    Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
     (Microsoft.DataTransformationServices.VsIntegration)
    Here are my environment details:
    SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
    Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
    Services Project2\Integration Services Project2\Package.dtsx.
    Does this kind of Shared drives have any impact to give this issue?
    Thanks in advance!
    Ketan
    P.S.: I had look at this forum question -->
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

    Hi Arthur,
    Thanks for your response.
    Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
    1) Some times excel source files cannot be parsed by excel source connection manager.
    2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage  while destination mapping.
    3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file.  <-- For
    this we tried IMEX setting also
    4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
    I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
    As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
    Do you think it is advisable to convert Excel into CSV or Flat file.
    Thanks,
    Ketan

  • CAn you use excel connection manager to connect to a folder that is protected with a username and password?

    I have folder on my server that my ssis package needs to get into. I have an excel file that I am connecting to using Excel Connection Manager. My ssis package is unable to connect to the folder. How do I get this to work. Thank you

    Hi RythmMusic,
    I am not sure how the folder is protected with username and password, Are you talking about folder is at restricted access and rest it ask you to punch window credential. In that case you need to run the ssis package with account which have access to that
    folder or use a proxy account to run under.
    If it protected from third party software then it need to decrypted by that third party software only. SSIS won;t be able to help here.
    Regards Harsh

  • AcquireConnection method call to the connection manager Excel connection Manager failed

    I used VS Studio 2008 (BIDS version 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results to different tabbed sheets of a single excel spreadsheet. The package was working just fine and has run
    successfully multiple times, but all of a sudden when opening the project, every single Data Flow task with an Excel Connection Manager displayed error icons. Each raises the following error message when attempting to open the Advanced Editor:
    SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at DataFlow task name: SSIS error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
    call to the connection manager Excel connection Manager failed with error code 0xC0202009. There may be error messages posted before this with more information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)
    From the time I created the original package (when it worked fine) until now:
     1) I have been using the same computer, the same login account and the same permissions.
     2) I have been writing to the same (32 bit) 2010 Excel file (which I created) in a folder on my local machine.
     3) The filename and location have not changed; a template file is used each time to move and overwrite the previous file. Both are in the same locations.
     4) I can independently open the target Excel file and the template Excel files with no errors.
     6) The ConnectionString has not changed. The Connnection String I am using is
      Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion\Results_dt01.xlsx;Extended Properties="EXCEL 12.0 XML;HDR=YES;".
     7) Run64BitRuntime is set to False.
    8)  Delay Validation is set to true
    9) This is not running under a SQL job  
    10) There are no child packages being run
    I CAN create a NEW Excel Connection Manager, assigning it the exact same target Excel spreadsheet, successfully, but when I attempt to assign it to the Data Flow destination this error occurs:
    "Test connection failed because of an error in initializing provider. Unspecified error."
    Thinking that the driver might be corrupt, I opened a second SSIS package, which also uses the Excel Connection Manager (same driver) and this package continues to work fine on the same workstation with no errors.
    I have searched online for causes of this error for many hours and found nothing that helps me to solve this issue.
    Does anyone have any suggestions for me?

    Yes, I have verified that the Excel file is not in use or opened by anyone, including me. It has been two months since I opened this particular package, although I have been working with other packages in this project. I just discovered that another
    package in the same project has the same problem - all Data Flows that output to an Excel Destination now have the same error icons. This second packages outputs to an entirely different Excel file than in the first package.  A summay:
    Package #1 has error on every Excel Destination and uses templateA to overwrite fileA and then writes to fileA
    Package #2 has error on every Excel Desintation and uses templateB to overwrite fileB and then writes to fileB
    Package #3 has no error on any Excel Destination and is linked to multiple files (none are A or B)
    Package #1 and #2 are in the same project, but Package #3 is in a separate project .
    I will try replacing the Excel files with new ones for Package 1 and 2.

  • [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

    Error
    [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There
    may be error message
    I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
    My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
    But the error still occurs .
    I checked on Google and  many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
    Mudassar

    Thats my connection string
    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
    Excel 2010 installed and its 32 bit edition
    Are you referring to install this component -AccessDatabaseEngine_x64.exe?
    http://www.microsoft.com/en-us/download/details.aspx?id=13255
    Mudassar
    You can try an OLEDB provider in that case
    see
    http://dataintegrity.wordpress.com/2009/10/16/xlsx/
    you might need to download and install ms access redistributable
    http://www.microsoft.com/en-in/download/details.aspx?id=13255
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Excel connection manager - Error after Installing Office 2013

    Hi Team,
    My SSIS package used to work fine until I Upgraded my Office 2010 to Office 2013. After upgrading to 2013, the SSIS package which is created using SQL 2012 is throwing error for Excel Connection manager. Below is the error what I see
    TITLE: Microsoft Visual Studio
    Could not retrieve the table information for the connection manager 'Excel Connection Manager'.
    Failed to connect to the source using the connection manager 'Excel Connection Manager'
    BUTTONS:
    OK
    FYI, I am running the package with Run64BitRunTime property = False.
    Do let me know the solution please. It will be of great help as we are proposing this tool in a migration project.

    I found the solution. Thanks
    You don't need office on your server (not recommended and not supported). You should install
    Microsoft Access Database Engine 2010 Redistributable for excel (xlsx) files and then use the Excel
    This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and *.accdb) files and Microsoft Office Excel 2010 (*.xls, *.xlsx, and *.xlsb) files to
    other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats.

  • SSIS 2012 EXCEL Connection manager error

    Hello all,
    When i try to make any excel connection manager in ssis 2012 its show below error.
    "Could not retrieve the table information for the connection manager 'Excel Connection Manager'. Failed to connect to the source using the connection manager 'Excel Connection Manager' in ssis 2012 error"
    I try for it EXCEL source and EXCEL destination. Both time same error happen. 
    Before i m use ssis 2008 then its work well bt after install 2012 its start this problem. I m also change debug 64 bit in false from true.
    Thanks for help

    Hi is there any way to install 32 ACE OLE DB in 64 bit system without uninstall my other software .
    I tried yesterday to instal 32 bit ACE but its told me u need to uninstall 64 bit software first :(
    thanks
    When using the command line, you can force the installation of the 32-bit version while the 64-bit version has already been installed.
    http://blogs.lessthandot.com/index.php/datamgmt/dbprogramming/mssqlserver/force-ace-installation/
    MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

  • Sql server agent job failing to connect excel connection manager of SSIS package by 32-bit mode run time

    I am unable to succeed with sql agent job, I am trying to execute the SSIS package through sql agent job by ticking 32 bit runtime check box in 64 bit machine , even it does not worked..
    could any one helpme on this?
     Source: Excel Load Connection manager "Excel Connection Manager"    
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class
    not registered".  End Error   TS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There may be error
    messages posted before this with more information on why the AcquireConnection method call failed.  End...  The package execution fa...  The step failed.

    Hello Keerthi,
    Can you please modify settings and set delay validation for Excel connection manager? I think its validating connection and failing because it might be picking that from some variable.
    Alternatively, please run package using below and see what happens.
    EXEC master..xp_cmdshell 'DTEXEC.exe /SQL "Folder\Package" /SERVER Servername'
    I will recommend you to follow steps in below link.
    http://www.sqlhammer.com/blog/running-ssis-packages-in-32-bit/
    Regards,
    Vishal Patel
    Blog: http://vspatel.co.uk
    Site: http://lehrity.com

  • SSIS package fails because of excel connection manager when deploying package from development to production

    Hello,
    When I move the package from development to production package fails due to excel connection manager.
    Error message---
    Message
    Executed as user: Answers\Administrator. ...lt: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
    Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE
    DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
    Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE
    DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".  End Error  Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source...  The package execution
    fa...  The step failed.
    Any help would be appreciated.

    Hi Vinay,
    As Visakh mentioned, the issue usually occurs because the package runs in 64-bit runtime, however, the Excel driver is 32-bit. According to your another thread, it seems that you use SSIS 2005, right? In SSIS 2005, there is no “use 32 bit runtime” option
    for the package executions of a SSIS package job step. In this condition, you have two choices:
    Install the 64-bit Microsoft ACE OLE DB 12.0 Provider on the production server. Here is the download link (AccessDatabaseEngine_x64.exe):
    http://www.microsoft.com/en-in/download/details.aspx?id=13255 
    Create a CmdExec type job step instead of SSIS Package job step, so that we can call 32-bit DTExec.exe to execute the package within command line. For more information, please see:
    http://support.microsoft.com/kb/934653/en-us 
    Regards,
    Mike Yin
    TechNet Community Support

  • SSIS excel connection datatype issue

    HI
    Please find data below
    ColA            ColB
    74378             11213
    312             21312
    34                 234
    7329             27924
    23423             224353
    42342             13243
    54245             32321
    25423             6483
    5234             84379
    dmf             934293
    52                 9549
    49                 439879
    ads             asdf
    asd             aesdf
    asd             asdf
    asd             asdf
    asdf             asdf
    sadf             asdf
    asdf             sadf
    Using excel connection to load data to SQL Server When I try doing this character data is loading as nulls, I have tried by putting IMEX=1 property in connection string and removing IMEX=1 property from connection string , in both cases it is showing nulls,
    in the data viewer which i have placed after Excel source. I have also tried using the OPENROWSET which for some reason does not create an adhoc connection. I also tried changing the Datatypes in the advanced editor which again throws error. I tried all possible
    ways of fixing this issue but no luck yet. Could you please help resolve this. For some reason SSIS excel connection reads only the first 8 rows and decides a datatype and rest showup NULL.

    The problem with your data is that Excel is attempting to guess the data type of the columns.  By default, the TypeGuessRows property is set to 8, which means it will sample the first eight rows.  In your data, the first eight rows are all numbers,
    so Excel interprets the entire column as numeric.  When it encounters text, it decides it can't convert text to numbers, so it provides SSIS with a NULL.
    IMEX has no effect in the above scenario (with the default TypeGuessRows value) because IMEX applies when Excel finds "mixed types" in the columns - and in your case (with eight rows) it does not.
    TypeGuessRows can be modified (as Reza suggested) but only for values from 0 to 16.  In your specific case, setting it to 16 would have an effect.  Excel would read your file, see some numeric AND text values, and decide those columns have "mixed
    types".  NOW the IMEX attribute comes into play.  If you DON'T specify IMEX=1, then Excel will choose a data type based on majority wins.  In your specific case, it would still choose numeric for column A and column B, because most of the values
    in the first 16 rows are numeric.  If you specify IMEX=1, then Excel behaves differently.  Instead of "majority wins", if multiple data types are detected, it ALWAYS picks text.
    So - in your specific case, with this specific file, increasing TypeGuessRows to 13 or more, AND using IMEX=1 will allow you to read both columns as text, and not receive NULLs.
    Talk to me now on

  • Dynamic excel connection string

    Hi, 
    I have excel file as source, where the file name can be anything; so to fetch the data from the excel file, I wanted to create a dynamic excel connection string. 
    So these are the following steps I have followed:
    1. For Each Loop: 
    Step 2:
    Step 3: Excel Connection string
    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\Product\Marketing__Products___Services.xlsx;Extended Properties="EXCEL 12.0 XML;HDR=YES";
    Connection String Expression : @[User::SourceFolder]+ @[User::SourceFile]
    And Below is the error I'm getting
    TITLE: Microsoft Visual Studio
    The component reported the following warnings:
    Error at PlanningIT_Service [Connection manager "Excel Connection Manager"]: The connection string format is not valid. It must consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string
    with zero components is set on database connection manager.
    Error at PlanningIT_Service: The result of the expression "@[User::SourceFolder]+ @[User::SourceFile]" on property "\Package.Connections[Excel Connection Manager].Properties[ConnectionString]" cannot be written to the property. The expression
    was evaluated, but cannot be set on the property.
    Choose OK if you want to continue with the operation.
    Choose Cancel if you want to stop the operation.
    BUTTONS:
    OK
    Cancel

    Hi,
    *) Make sure file names are retrieved properly:
    A.txt if you have Name and extension under Collection tab - > Retrieve file name
    A  if you have Name only under Collection tab - > Retrieve file name
    C:\Users\sathya\Desktop\Source_Folder\A.txt  if you have Fully qualified under Collection tab - > Retrieve file name
    *) variable property - Set EvaluateAsExpression = True
    Try below links for examples:
    http://msdn.microsoft.com/en-us/library/ms345182.aspx
    http://mikedavissql.com/2013/09/16/loop-through-excel-files-in-ssis/
    http://www.allaboutmssql.com/2012/09/sql-server-integration-services-rename.html
    sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

  • Excel Connection Manager input only getting SALES$ and NOT SALES

    Hello, 
    I am creating a SSIS package to import a Excel file to SQL server and create a table. 
    On Excel connection manager once I've selected the Excel file, on the bottom Name of the Excel sheet I am getting SALES$ and NOT SALES. 
    Could anybody advise?
    To add I am getting error. 
    [Excel Source [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager 1" failed with error code 0xC00F9304.  There may be error
    messages posted before this with more information on why the AcquireConnection method call failed.
    Best regards, 
    Mohan

    Delete the existing excel connection and create a new one to get rid of your error. You should be able to see the second sheet in the dropdown

  • Excel Connection Manager

    Does Excel Connection Manager suppose to work for Excel 2007? Or Do I have to use OLE DB connection
    manager against the Access 12.0 provider?  I tried both Excel Source and Excel Destination, but I was not able to load the spreadsheet from the Excel file.  When select the dropdown under Name of the Excel sheet, it said "No tables or views
    could be loaded." Then popup an error "Could not retrieve the table information fo rthe connection manager..."
    newbie

    You need to use Access 12.0 to connect to Excel 2007. w
    hats the type of file you're connecting to? xlsx,csv or xlsm? 
    see
    http://msdn.microsoft.com/en-us/library/cc280527(v=sql.100).aspx
    http://www.bidn.com/blogs/DevinKnight/ssis/2782/using-excel-macro-xlsm-enabled-files-in-ssis
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • 3 blue lights - excellent connection - yet still s...

    hi
    I have three blue lights, supposedly excellent connection. Yet connection grinding to a halt periodically - every 15-20 minutes.. Skype calls also failing when this happens which is a big problem for me.
    Can you help please.
    Thanks

    ADSL Line Status
    Connection Information
    Line state:
    Connectedppp0_0
    Connection time:
    0 days, 02:13:35
    Downstream:
    4.93 Mbps
    Upstream:
    655.7 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.5 Annex A
    Latency type:
    Fast
    Noise margin (Down/Up):
    14.5 dB / 12.4 dB
    Line attenuation (Down/Up):
    34.7 dB / 20.9 dB
    Output power (Down/Up):
    20.2 dBm / 12.6 dBm
    FEC Events (Down/Up):
    0 / 0
    CRC Events (Down/Up):
    1792 / 83
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    2062 / 139
    Error Seconds (Local/Remote):
    70028 / 10689
    Hide details

  • Local EPM Excel Connection not responding when working with proxy server.

    Hi All ,
    We were working on a server . Due to some issues we had to use proxy server to connect to the Backend.
    But the Local Connections that were made in Excel to log in via EPM Tab is no more working.
    Is it something related to Proxy Server.
    In that case , how to configure the Local Excel Connections.
    Regards,
    SHUBHAM

    Hi Andy ,
    When we connect to EPM Office Add in link in Web Admin , We get basically 3 options, out of which we choose connect EPM Office Add-in for Excel. But that option is not coming. Rather it asks to install EPM addin, while it has been already installed . This problem has been present for a very long time .
    So in case of Connecting to  Excel Interface , if this option was fine then we could have easily gone to System generated link in Web Admin to connect to EPM Excel interface. But since this option isn't coming so we had to go through making Local Connections.
    But given the Proxy server settings the earlier Local EPM Excel Connections are not working.
    Regards,
    SHUBHAM

Maybe you are looking for