This is usually related to the command line and/or argument in the published app itself.
i.e if sage is published by referring to \\server\c$\sage , the user might not have access to that C$ . Instead verify the published path is something like \\server\sage$\mas90\... , or even c:\sage\mas90\... would also work for the published app.)
Is this the only user getting the error?
Also if it's the only user, make sure that the permissions in the collection, as well as the permission on the published app is also correct for this user (including the ACLs to the appropriate sage folders)
------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com | 877-888-5525
http://gotomyerp.com/------------------------------