Sage 100

 View Only
Expand all | Collapse all

From a customer who I recently upgraded from Sage

  • 1.  From a customer who I recently upgraded from Sage

    Posted 07-26-2017 12:17
    From a customer who I recently upgraded from Sage 100 Advanced to Sage 100 2017.2 Premium Below is a list of issues that we have been having with users in Sage, specifically when in Citrix vs. Remote Desktop. All of these issues are intermittent. At any point either during login or opening a new task that will create a new window, **the window box is solid black and Sage freezes up at that point**. When posting/processing (i.e. Cash Receipts / Journal Entries), **Sage stops working and freezes in the session**. At that point, we need to 'kill' the locked sessions in Master Console. Problematic with Adobe Reader at times, when printing to PDF. These are the main issues that seem to keep happening. The users are not having issues on Citrix with other applications, such as Accellos, Outlook or Excel. I'd be curious if this other client on Citrix had any of these issues.


  • 2.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 12:26
    Are they using the new interface? With Citrix, are they running as a Published app?


  • 3.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 12:28
    Yes to the new interface and I believe they are running as published apps. They have the Citrix Receiver which seems like it essentially publishes the app.


  • 4.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 12:34
    I have 2 clients having similar issues, but nothing that I can recreate. Both are using the new interface, both are Published apps. If I put them back to the old interface, everything is good. I have not called Sage to report it, since I can't pinpoint the issue. My problems were not exactly the same as yours, and were very intermittent.


  • 5.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 12:38
    This one is a little more consistent. I've seen the black screen come up while I was there doing the upgrade. It isn't instantly repeatable but if I wait for a few hours it's pretty much guaranteed that someone on Citrix will get the big black screen. The RDP access works fine.


  • 6.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 13:18
    We had serious issues with one Citrix client we traced to Sage Exchange (and how that installer / program works). Their IT dealt with it.


  • 7.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:11
    @KevinMoyes Do you remember what type of issues? Was it related only to Citrix? Would it also appear if they were in on Terminal Services/RDP? In my case, I'm only seeing issues with Citrix.


  • 8.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:16
      |   view attached
    It was specifically related to Cirtix and how the local profiles were handled. I think this was the knowledge base article which we gave to their IT about it.


  • 9.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:19
    Two more ideas I sent at the time: 1) The Citrix administrator can set up a folder redirection for the local setting folder of the user's profile. This is the folder where ClickOnce applications install by default. 2) Another method is using the Roaming Profiles, which carries the user profile anywhere the user logs on, including Terminal Sessions.


  • 10.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:20
    (That, plus full access to the workstation program folder).


  • 11.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:23
    Doesn't SED 2.0 fix this issue by requiring that the SED 2.0 be separately installed?


  • 12.  RE: From a customer who I recently upgraded from Sage

    Posted 07-26-2017 14:42
    It's where SE gets installed that was the problem. When the user logged off, the files were destroyed. Citrix permissions were also locked down, so I'm not sure the installer worked for users at all originally. (I'm going based on memory... not a Citrix expert at all).