Sage 100

Sage 100 v 2015 Advanced - Windows 10 Workstation When the user is under her network login, and logs into Sage, the user name and pwd are accepted, then the screen flashes, then nothing displays. When I remote in using her network login with my Sage 100 login, Sage opens and can be used. Click File change User in Library master to switch from my login to her Sage 100 login and it holds it, for about 10 seconds, then Sage closes, no error, just closes. This is a new Win 10 workstation wrksetup installed under my network login first, and when she couldn't see the Sage install at all, reinstalled under her (local domain admin, I'm led to believe). Set the workstation shortcut Run as Admin, added Modify permission on all the Sage, Common Components, etc. folders, set the PDF printer to non-null port, turned off UAC. I even created a new Sage user code for her and it still doesn't work. I'm not sure where to look next any ideas? tia.

Standard or Classic UI? If Standard, delete the Sage folder from the user's documents folder and launch Sage again.

Sage v 2015 classic, I don't think themes had been introduced yet. When I look at the users\documents I don't see a Sage folder.

You asked for ideas. These are all iffy but ... Does her Sage User ID contain spaces or dots or other potentially problematic symbols (like . ! $ % ^ ' ( ) { } ` ~ ) It does allow those them some of which are o/s problematic. There is a Rename button in User Maintenance if you were inclined to try it out then revert it back. Related to the symbols, one thing that happens on Sage login is it identifies all User-Company folders under Mas90\MM\Custom folders. Not sure if done based on the library paths in Customizer log file or scan of o/s under \mas90 folder. Also, on a Change User or initial User login using Classic launcher it will load the buttons on custom toolbar, Public Tasks, and Private Tasks for the user. Back in 4.5, troubleshot a long load time when users logged in. It didn't close the Launcher but maybe similar still. One user had created a Public Task (but could have been Private Task) that was pointed to an EXE that was only valid for her. During login process, system was actually validating the path each Public and Private Tasks that pointed to external programs (like this EXE). By design it tried to validate EXE path in a 30 second loop before timing out. To see if in play, from where Wkstn Setup is installed, go to her \mas90\Launcher and rename folder showing her Sage user name. It contains custom buttons (MNUCBTN.txt) and Private Tasks (MNUTASKS.ini). Then login as her.

based off of your 6:04 post: If they are using redirected 'My Documents' it can be an issue. The Sage 100 folder needs to be local. Sage ID 83202 (may be what you're looking for) Be sure there is no redirect. Not sure on 2015, but I've had this on 2018/2018 100c. Create \ Rename Sage 100 in the Documents (local) directory maybe.

To eliminate workstation issues or Sage account issues, I'd try MAS90 mode.

Status - tried it all and we still have issues. Called in IT to review permissions - we'll keep you posted, thanks everyone.