Sage 100

 View Only

  • 1.  Error #43 in Sage 2020

    Posted 01-27-2021 14:01

    I'm hoping you guys might be able to help on this. We have a customer going onto Sage 2020.0 Premium (from Sage 2018) that is experiencing error #43. According to Sage, the fix is to try rebooting the server (which we did) and also to rename the SY_Workstation and SY_Console files (which I'm planning on doing tonight).

     

    I was wondering if anyone else had run into. The users who get it might run into it as soon as they log into Sage, some get on a specific data entry screen, others might get it during posting. Note – when it happens, the user gets booted out of Sage completely. If they log right back in, sometimes it will start working for them, sometimes it won't.

     

    Important to note – customer in question has users logging into a Terminal Server farm so we're thinking part of why logging out/logging back in works is because they aren't getting back in on the same server. However, this also doesn't work for everyone.

     

    The problem is becoming increasingly worse which is why I thought I would post here. We had 1 user have it last week. This week we have had probably 5 to 6 getting it. We're going to be taking them live in 3 weeks so I just want to be sure this isn't a major 911.

     

    Thanks in advance for your help!

     

     

     

    Tara Schinkel

    CFO
    Stewart Technologies



  • 2.  RE: Error #43 in Sage 2020

    Posted 02-04-2021 10:30
    Did renaming  sy_console  and Sy_workstation resolve this issue?

    ------------------------------
    Jim Woodhead
    DSD Business Systems
    619-990-3946
    ------------------------------



  • 3.  RE: Error #43 in Sage 2020

    Posted 02-04-2021 10:31
    First thing we tried, it came back the next day. 

    Tara Morgan Schinkel, CPA

    Sage 100 Consultant

    Act! and Sage CRM Consultant

    Phone: 410-309-9550 x1104

    www.stewarttechnologies.com







    Original Message


  • 4.  RE: Error #43 in Sage 2020

    Posted 02-05-2021 09:11
    Not sure if this is the same exact issue or not, but I fought this same message for a very long time.  I have actually come across this now twice.
    The first time it was on a network that was wired terribly, new switches were ordered, and new cables had to be run.
    The second time was when a client was on a terrible WIFI router.

    From what I can tell with 2020 it takes longer to "log in".  You actually get the launcher fully up before everything behind the scenes is done logging you in and giving you a valid session.  On slow networks or networks that occasionally hiccup and cause things to temporarily pause its possible to click on screens before you are fully logged in.
    The temp work around was to ask users that get the issue to wait 30 sec to a min after they log in before the start trying to use the system.

    ------------------------------
    Brett Pensinger
    Martin And Associates
    Cincinnati OH
    513-782-6119
    ------------------------------



  • 5.  RE: Error #43 in Sage 2020

    Posted 02-05-2021 09:55
    Thanks for the feedback.  In my case the customer  getting  this is on has a network that is very slow.  This is making a lot of sense .

    Thanks 

    Get Outlook for iOSo



    Original Message


  • 6.  RE: Error #43 in Sage 2020

    Posted 02-05-2021 11:13

    Thanks. Unfortunately, for mine, the network is actually pretty quick.

     

    Tara Schinkel

    Sage 100 Consultant

    Act! Certified Consultant

    Stewart Technologies

    410 – 309 -9550 x 1104

     




    Original Message


Related Content