SSIS Job Won't Run with SQL Agent

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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Randy Knight, MCMPrincipal ConsultantCommented:
Does the SQL Server Agent Service Account have permissions to the Excel file?
yonbretAuthor Commented:
To rule out a permission error, I granted Modify permission to Everyone on the Excel spreadsheet.

Everyone should include the SQL Agent Account
Randy Knight, MCMPrincipal ConsultantCommented:
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.
yonbretAuthor Commented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
yonbretAuthor Commented:
I had to call Microsoft for a resolution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.