etl file operations

The VM that was housing our production ETL started having net bios issues.
We generated a new vm windows server r2. I downloaded the new version 9.1.2 and istalled it, and pointed it against the production etl sql database.
I went to the scheduler, change the machine name and everything seems to work except the file operation
All our packages execute from the scheduler
I does not seem to be able to find files and move them when executed from the scheduler. However if I go to the same package in edit mode it works perfectly.
I have tried deleting and rebuilding the file operations, I may go back to creating DOS commands, but am hoping you have the solution.

When the scheduler executes the package te file operations do not work, with a message could not find files
If I go to the package in edit mode and execute, it works perfect.

Are you using mapped drives?
Are you using agent?

Mapped drives do not exist in windows services word please use UNC path instead

If this does not help please post some screenshots

here are picture, look at in order
trying to show the job executed from the schedule, files were present.
the file process use the unc path
error message files not found
i ran the same package, opened in edit mode, everything worked perfectly
when i drill to the folder from the package they find the data
these packages have been running for year, using unc
the only change was installing the new download on a new server, and executing

I will be the office around 5AM EST. I would love to get someone on y machine via teamviewer.
Let me know if this can work and who I need to contact

OK let's do a remote session later.
One of us will be available

just let me know.
I had to go back to my original server.
All inbound and outbound processes were failing because directories could not be found, if the main package was executed by the scheduler.
If I opened the main package and executed it, it worked
My production server a2bf-app is having issues.
we have a new vm a2bf-app1
I am using the same etl-sql database
I installed 9.1.2 on the new server a2bf-app1
I install all the appropriate ODBC and connections
I go to the scheduler and change a2bf-app to a2bf-app1
was hoping all would be good.
I remember when I did our first upgrade this happened, someone on your team found a leading space or null in front of the UNC values

Are you using agent for execution?

May be the user you use to run agent no longer has enough access rights?