Sql-server – Error trying to run SSIS Packages in SQL Server 2008 SQL Server Agent

Although you don't mention it in the question, I assume that the reason you're using an SSIS package rather than simply executing the stored proc from a SQL Agent job is that there are other steps in the process. My other assumption is that you schedule the SSIS package using a SQL Agent job.

The first error message implies that you are creating an OLEDB connection to your Access database but that the database could not be found. It's possible that this is a security problem, and that the Windows account under which the SSIS package is running does not have permissions to the file system location where the Access database is stored.
The second error message seems to back this up - when executing the SP, the linked server connection could not be opened.

To confirm this as the issue, you need to try running the SP in SSMS using the same account under which the SQL Agent service runs.

If this is the problem, you will need either to change the permissions of the SQL Agent service account to allow access to the target location, or copy the access db to a location that the account can access (possibly the local disk) before running the package.

EDIT - in response to additional details:

Now that permission and Networked Drive are mentioned, I think this may be the problem. However, I am still confused as to why I am able to manually execute the Stored Procedure from within SQL Server with the Access DB on a Network Drive?

The Acess linked server is configured to use the security credentials of the account executing the query. When you execute the procedure from SQL Server Management Studio, you are doing so in the context of your Windows account, which must have permissions to the network share.
When the same query is executed by the SQL Agent service, it uses the security context of the service account under which the service is running, which does not have access to the share.

Finally, how can I apply this suggestion? Meaning where in SQL Server do I configure this feature:

change the permissions of the SQL Agent service account to allow access to the target location

You can find out and change the account under which the SQL Agent service is running in the SQL configuration manager (should be found under Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools. Find "SQL Server Agent" in the list of SQL Server Services and see the "Log On As" column). You may need to switch this to a domain account to get access to the share.

It is an SSIS 2008 package running on a SQL Server 2008 instance. My package security is DontSaveSensitive.

You have to save the package with EncryptAllWithPassword using a password.

Then schedule it using SQL Agent Job as below :

"DriveLetter\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /FILE "SSIS_Package_Location\bin\Package.dtsx" /DECRYPT "PasswordStrong007" /CONFIGFILE "Location_to_Config_file_If_any\Config.dtsConfig" /CHECKPOINTING OFF /REPORTING E

Now the user account that you use should have permissions on the database server instance.

You can check the permissions using below T-SQL :

SELECT [Login Type] = CASE sp.type
        WHEN 'u'
            THEN 'WINDOWS Login'
        WHEN 's'
            THEN 'SQL Login'
        WHEN 'g'
            THEN 'GRP'
        END
    ,convert(CHAR(45), sp.NAME) AS srvLogin
    ,convert(CHAR(45), sp2.NAME) AS srvRole
    ,convert(CHAR(25), dbp.NAME) AS dbUser
    ,convert(CHAR(25), dbp2.NAME) AS dbRole
FROM sys.server_principals AS sp
JOIN sys.database_principals AS dbp ON sp.sid = dbp.sid
JOIN sys.database_role_members AS dbrm ON dbp.principal_Id = dbrm.member_principal_Id
JOIN sys.database_principals AS dbp2 ON dbrm.role_principal_id = dbp2.principal_id
LEFT JOIN sys.server_role_members AS srm ON sp.principal_id = srm.member_principal_id
LEFT JOIN sys.server_principals AS sp2 ON srm.role_principal_id = sp2.principal_id