SSIS Job Won't Run with SQL Agent

Posted on 2014-08-28
Last Modified: 2016-02-11
I have created a SSIS job to transfer data from an Excel Spreadsheet to a SQL Server 2012 table.

When I run the package in Visual Studio, everything executes without a problem.

When I try running the job in SQL Server using SQL Agent, I get an error message to check the error Log. Nothing appears in the error log.

When I try running the job from a command prompt, I see the error as follows: "DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager DailyLogExcel" failed with error code 0xC0209303.

I have already set “Run64BitRuntime” property to false.

Any suggestions?
Question by:yonbret
    LVL 4

    Expert Comment

    by:Randy Knight, MCM
    Does the SQL Server Agent Service Account have permissions to the Excel file?

    Author Comment

    To rule out a permission error, I granted Modify permission to Everyone on the Excel spreadsheet.

    Everyone should include the SQL Agent Account
    LVL 4

    Expert Comment

    by:Randy Knight, MCM
    Log on to the server console using the SQL Agent Account and see if it can access the file.  That will tell you for sure if the permissions are working or not.

    Accepted Solution

    I had to call Microsoft for resolution.

    The problem was that when creating SSIS jobs there is a Project Data Source option. It makes Data Sources available for all packages in your project. In runs perfect in the SSIS developer software, however, when you move those SSIS packages to run using the SQL Server Agent the Project Data Sources are not copied as part of the SSIS package.

    So I had to change all of the SSIS Data Sources to be just for one package.

    Short answer, if you are planning to deploy the packages outside of Visual Studio, don't use the Project Data Connections.

    Author Closing Comment

    I had to call Microsoft for a resolution

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Suggested Solutions

    JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
    For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
    Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
    Via a live example, show how to setup several different housekeeping processes for a SQL Server.

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now