Sage 100

Client switched servers. Client has some buttons which run scripts. Scripts now work for some folks and not for others and appears to be MAS, not network. (i.e. end user logged into network, can't run it - then IT guy logs into MAS only and it runs for him - same network user, though). Any thoughts? He's checked roles, network rights, etc, and he can access the files via Explorer as the end user, but via MAS gets ""Cannot access script"".

If this is MAS 200, what Windows account is the MAS 200 service running as? System account often has restrictions that can effect scripts.

Oh, I got all excited until I remembered they are on MAs90. Bummer.

Is it an issue with a UNC versus mapped drive?

Client thought that, too, but didn't help. Keep those cards and letters coming...

Probably asked, here goes Is there any pathing specified within the script ro specified? What about the pathing that idicates where the script is located. I usually use UNC paths which will error out if the server name changes.

He tried it both ways.

Are the panels customized uniquely for each user? If so, the link settings could also be different.

Asked about that and apparently no. Dang it.

Well, there is always the ""give them full role rights in MAS"" to see if this allows the user access. Since the IT guy logs into MAS as the same network user, this would seem to indicate and issue with the MAS role maintenance.

Just emailed him to try this. We shall see...

Regarding roles, if one was copied from another, I know there were issues where the roles could look exactly the same but they did not function the same, something about the copying. (Did Sage ever resolve that??)

Interesting. I think I've run into this ""bug"" before. Completely befuddled me. FWIW, I usually set up a dummy user that I can try different roles with. This allows me to ""see"" the issue that a user reports (assign user role to dummy user) without having to do a session with the user.