SSIS job package is not connecting to MS Access

I am experiencing an SQL 2014 Job Package that is not connecting to MS Access when the package is either scheduled or manually running it. The package connects and runs fine when I developed it in VBS with no errors. The package dtsx was deployed to SSIS in the Integration Services Catalog SSISB.

Connection String value:  Data Source=\\xxxx\xxxx\xxxx\Databases\Mmaster.mdb;Provider=Microsoft.Jet.OLEDB.4.0;
Server Name:  \\xxxx\xxxx\xxxx\Databases\Mmaster.mdb
UserName: admin
Password: [left blank as there is no mdw and the mdb is not password protected]
InitialCatalog: NULL
RetainSameConnection: False

These are the Connections available through the Connection Manager, once I select the OLEDB, then I selected the Microsoft Jet 4.0 OLE DB Provider. It tests and connects with VBS, just not in the SSIS Server Agent Jobs.
Connections-1.jpg Connections-2.jpg
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.

You have not provided any error message, but I suspect a permissions problem.  The service-account that invokes the SQL-Agent-Job probably does not have access to the folder containing the Microsoft Access database file.
edrz01Author Commented:
The follow error message was received:

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted

05/03/2019 16:30:54,pkg_Import_Appl_Gen,Error,,SQL,pkg_Import_Appl_Gen,,,The job failed.  
The Job was invoked by User xxxx\NetAdmin.  

The last step to run was step 1 (pkg_Appliance).,00:00:04,0,0,,,,0

05/03/2019 16:30:54,pkg_Import_Appl_Gen,Error,1,SQL,pkg_Import_Appl_Gen,pkg_Appliance,,Executed as user: xxxx\NetAdmin.

Microsoft (R) SQL Server Execute Package Utility  Version 12.0.6024.0 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    

Started:  4:30:54 PM  Package execution on IS Server failed. Execution ID: 219<c/> Execution Status:4.  

To view the details for the execution<c/> right-click on the Integration Services Catalog<c/> and open the [All Executions] report  Started:  4:30:54 PM  Finished: 4:30:58 PM  Elapsed:  3.453 seconds.  The package execution failed.  The step failed.,00:00:04,0,0,,,,0

Change your SQL Agent job to use 32-bit runtime

SQL Agent - Job Step Properties

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
edrz01Author Commented:
PERFECT!!!! One very simple step. The Access is 32-bit and SQL is 64-bit, never took that into consideration. I was able to add Step-2 to the job and both jobs ran perfectly. Thank you very much for your assistance.
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
VB Script

From novice to tech pro — start learning today.