Sage 100

 View Only

  • 1.  Slow Performance SAGE 100 Standard UNC path in SAGE shortcut.

    Posted 11-16-2022 10:58
    Edited by Michael McDonald 11-16-2022 17:23
      |   view attached
    I have a client running SAGE 100 Standard v2020 w/PU #1. They RDP into a virtual windows server and then launch SAGE 100 from an icon on the desktop. SAGE 100 STD v2020 is installed on a different application virtual server.  The SAGE 100 STD v2020 icon shows "Start In' as a UNC path to the application server. The remote server has the drive letter "S" mapped to a folder above \SAGE 100 v2020\MAS90.

    Here is a SAGE Technical Bulletin ID 62660 (see attached) that states "Slow performance" when "the 'Start In' path on the Sage 100 STD shortcut is changed to a UNC path".

    What is causing the "Start In" configuration to switch to the UNC path if you perform the normal Sage 100 Workstation Client install using the mapped drive letter "S"? Can you manually change the UNC path back to the mapped drive letter in icon properties?

    TIA for any assistance.   ​

    ------------------------------
    Michael McDonald - Consultant
    Michael T McDonald CPA
    (616) 813-8887 - mike@mcdcpa.com
    ------------------------------


  • 2.  RE: Slow Performance SAGE 100 Standard UNC path in SAGE shortcut.

    Posted 11-17-2022 10:44
    You can change the path and start in on the icon, But there may be registry entries or .dll files somewhere - My advice would be to do a complete uninstall and reinstall workstation setup.

    ------------------------------
    David Overholt
    DWD Technology Group
    ------------------------------



  • 3.  RE: Slow Performance SAGE 100 Standard UNC path in SAGE shortcut.

    Posted 11-17-2022 11:27
    @David Overholt...Thanks for your reply. I have the in-house IT guy scheduled to do the following: 

    1) Adjust the User Account Control (UAC) on the Windows 2016 remote server as mentioned in the SAGE Technical Bulletin
    2) Uninstall the SAGE 100 v2020 Workstation Client on the remote server.
    3) Re-boot the Windows 2016 remote server.
    4) Re-install the SAGE 100 v2020 Workstation Client on the remote server, making sure it is launched "run as administrator" from the "S" drive and NOT from a UNC path.
    5) Examine the properties of the created Sage 100 icon. Hopefully the "Start In" will show the mapped drive and NOT the UNC path.  

    Thanks again
    ​

    ------------------------------
    Michael McDonald - Consultant
    Michael T McDonald CPA
    (616) 813-8887 - mike@mcdcpa.com
    ------------------------------

    Original Message


Related Content