Sage 100

Strange printing problem of the week. A customer uses RDP in a hosted Amazon cloud for their Sage 100 solution. Each user has their own RDP credentials and their own Sage 100 credentials. When a particular user is logged into his RDP session his operating system recognizes all printers on the network. However, when he logs into Sage 100 the only printer on the list is ""Deferred Printer."" This totally prevents him from printing from within Sage even though he can print from other apps (i.e. Excel, Word). This situation happens no matter which Sage 100 user credentials are used When a different user's RDP credentials are used, any Sage 100 credentials will recognize all of the network printers from within the Sage product. The IT guy says that he hasn't done anything special to the RDP credentials. Any ideas?

Log out and back in again to RDP. User has lost network authentication

@RobertWhite would that be the case every time the user logs in? This is a consistent error that follows a particular user. It ""may"" be tied to administrator rights. I'm not sure.

I had this issue last week and giving Sage users full rights to the Sage share solved it. Ronald S. Gouveia, CPA CITP Carr, Gouveia, & Associates, CPAs, Inc. T: (808) 837-2507 E-mail: Ron@cga-cpa.com F: (808) 833-0892

In my experience it's always network authentication. Navigate to the path of where sage is installed on the server (as shown in the sota.ini file). If challenged for a user name and password, enter it, then the user should see other printers. Of course user needs full rights to the 'mas90' folder and subfolders

This is why I prefer that IT create a user group ""Sage 100"", granting all necessary network rights to that group, then assign each user to that group. Minimizes the possibility that network rights are inadequate.

It's network authentication or rights.

We ran into an issue like this recently too. We had the IT professional ""push out"" the security profile again for that one user, and that fixed it. So, for some reason, this one user had lost their permissions overnight. We still do not know why. All of this nonsense to simply agree with everyone else that it is a permissions issue. Didn't add much to this, did I? Ha!