Check Role permissions.  Access is granted to not just the program (VI tasks) but also by the source / destination module.

Double Check Security Role under Module Options Tab to confirm the user has "allow access to Visual Integrator Job Imports" and the "export" one also.  

They are Sage 2019.  All boxes are checked on each tab in Role Maintenance.  We set up a new Role and a new User, but still have the same issue.

That is odd. 

Verify Windows read-write permission (NTFS and Share) for the MAS90 folder.

Their IT checked and says Full Control all the way down.  Here's an interesting development.  If they attempt to run an old job they get an Error 18, Program not loaded/invalid program format.  If they attempt to run a job we just created they get You are not authorized to access this program.  I am starting to feel like maybe the VI program has gotten corrupted...

Be sure to set AV exclusions.  I've seen strange things with AV software blocking things related to VI. 

(There is a Sage KB article on recommendations).

I'm working with a Senior Tech at Sage on this one.  It seems to be one not easy to resolve.  I will let you know what they come up with.  Thanks for all your help! 

We were able to work with Sage to determine the issue.  It appears that when Avalara was installed it replaced a file in the MAS90\VI folder called VI_ImportJobComplile.pvc.  IF we rename that file and copy back in the default Sage file the VI jobs are able to run again.  We contacted Avalara early last week with the question, Can we leave the default Sage file installed or do we need an update to the Avalara program?  They requested a conference call to review the issue.  We were told during that call that they would get back to us with an answer.  Then they scheduled another conference call two days later, but did not attend.  So we are still waiting for an answer.  Does anyone know if it is ok to use the Sage file instead?  

This is holding up another project and is very frustrating!

Thanks.

Sue