Getting import error when attempting to import files into sql server via deployed ssis package

I have created an SSIS package that import text and excel file from a central network location into tables on an SQL Server 2016 .  It execute flawlessly using the sql Data tools 2015. I then deployed the the project to the sql server.  The deployment went fine.  However, when I try to execute the import package I get the following error.  I've also attached the error report. I've checked the files and they are not open.  The Sql Server has been given the permissions to the file folder in question.  Just to cross my t's and dot my i, what types of permission does the sql server need in order to import files from a network location

RPS Import:Error: 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: "The
Microsoft Access database engine cannot open or write to
the file '\\Bfs\departments\CORPORATE\DQM\ONLINE
RPS TEST DATA\Online BCM Tool Files\6. Change
Report Type\Change Report Type.xlsx'. It is already
opened exclusively by another user, or you need
permission to view and write its data.".
Juan VelasquezAsked:
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.

Jose TorresSenior SQL Server DBACommented:
Are you running the package on the server as 32 bit, there is no 64 excel driver
How are you running the deployed package
0

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
Juan VelasquezAuthor Commented:
Hello Jose,
I tried running it in 32 bit .  I went to the project menu, selected properties\Configuration Properties\debugging\ and set 64 bit runtime to false. I still getting the same results.  I'm new at ssis.
0
Juan VelasquezAuthor Commented:
I just heard from the SQL server team and the package is being run  in 32 bit mode.
0
Juan VelasquezAuthor Commented:
I have some more information.  I've been doing some testing and have found that the problem occurs when importing Excel and text files
0
Juan VelasquezAuthor Commented:
Basically I found that the service account under which the ssis project was running did not have sufficient permissions
0
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
SQL

From novice to tech pro — start learning today.