Is there any additional logs generated when SSIS package would be running? I mean generic logs not error handling that would be added to the package itself

Sql services are using built in account so NT service\mssqlserver, nt service\sqlserveragent and nt service\msdtsserver140

Ssis package is being ran using the SQL agent account. The job owner was using a...

Should it just be the SQL agent account or SQL service and SSIS account?

Do you know specifically what folder locations?  I have given to SQL server program files folder. Should it have any access to files on C drive like C:\Windows?

Should the account need access to any folders relating to SQL services specifically?

NT Service\SQLSERVERAGENT

This is what is was using on the old server

I tried with proxy account is well but didn't make a difference

I select Type SQL Server integration Services Package. Then for package source choose file system and provide the location of the package

It is running as a SQL job. This is the way it was running on the previous server so would prefer to use SQL agent than windows task

Ok so the only possible issue is permissions are missing somewhere?

I have checked the file using notepad and any locations mentioned I have given full control so I am lost

I have given the account all the access it should require but still getting the 3 errors

No, I presume when I move a package from one server to another it should work when the SQL version isn't changing

I thought once the account is in the local admins group for the server it should have all the required access to SQL directories iswell

I provided the account with explicit permission but still the same errors

User is part of the local admin group of the server so should have all the access

Yes it works when you script it