Sage 100

 View Only
  • 1.  Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 12:20
    Client on Sage 100 Std 2013, running through RDS as a Remote App is reporting the following: ""He (end user) launches the RDP, he sees the login screen and logs in, then SAGE (remote) shows in the task bar but it's not displaying on the screen, it's like it's there but invisible.. if I click on the screen(which shows his background) it takes me to a SAGE website in IE.."" He is the only user that is having this problem, Sage works fine if he logs in from another user's PC. Anyone run across anything like that? Any idea how to fix it? Can I clear his ""terminal"" records on the RDS server? TIA.


  • 2.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 12:24
    Greg. We usually see this in RemoteApp if the user is working on 2 monitors, and they launch sage on a single monitor where the last launch was on a now non-existent monitor. (So basically Sage is off-screen). Try clearing their Sage 100 folder in documents, or at least their JSON files, and have them try again. This sill likely resolve the issue.


  • 3.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 13:15
    What George said. Here is how I've handled it before using the keyboard. Note this is hard to describe to a customer and if you're not keyboard oriented yourself it could get weird. From the Windows taskbar click on Sage (and you can't see it still obviously) do the following: * Hold down the Alt key + spacebar. This is same as clicking on the top left stub menu where you see Restore, Move, Size, Minimize, Maximize, and Close options. * Press M on the keyboard for Move * Hold down your keyboard arrow key (either left or right) to move the Launcher into the main screen. It's just like dragging with your mouse. I like trying the left arrow key first since most secondary screens are on the right. If it doesn't become visible soon, then hold down right arrow key. Worst case is if they are using the Classic Launcher, then renaming a specific registry key under HKCU and restarting Sage will force the Launcher to reload in its default screen, position, and size. I think it's this one: HKEY_CURRENT_USER\Software\Sage Software\MAS 90 Business Desktop I think @BethBowers remembers this better:


  • 4.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 13:17
    @BethBowers doesn't remember **** any more.


  • 5.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 13:19
    Noted :-)


  • 6.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 13:20
    LOL


  • 7.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-07-2019 13:22
    Thanks @GeorgeKhairallah & @AlnoorCassim info passed along to IT. @BethBowers me either :\


  • 8.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-08-2019 13:12
    So this was caused by docking the laptop at home where the user has multiple monitors, then bringing to the office where there is only one monitor - good call @GeorgeKhairallah. IT was able to fix using @AlnoorCassim keyboard method to move the launcher window back into view. Thanks guys.


  • 9.  RE: Client on Sage 100 Std 2013, running through RDS a

    Posted 01-08-2019 14:38
    This sometimes happens to me when I undock my LT (two external monitors) and go on a road trip. I find the older software (Act! and Sage) remembers the last monitor used and has to be manually moved back. Browsers and Microsoft Office seems to know when there is only one monitor......