Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Help understanding SAGE error messages

  • 1.  Help understanding SAGE error messages

    Posted 07-30-2020 10:53
    I have a client that was on SAGE 100 STD v2017 and receiving Unlock Region Failure, Input output SY_Session.pvc and Error 105 messages several times a month. Their IT folks installed a new virtual server and I upgraded SAGE 100 from v2017 to v2019 PU#3.  The Unlock Region Failure errors have gone away with the new server. The main AR and SO user continues to receive "Input Output SY_Session.pvc" errors and "Error 105 Short Key Block" errors in the Cash Receipts posting function and in the Sales Order Journal Update function.  She stated that most of the time "it seems to resolve itself" she just has to "shut down SAGE 100 and get back in". A few times the "cash receipts batch or the SO invoice has to be re-entered"
    Are the two error messages related? Does the Input Output message cause the Error 105s?  When I look in the SAGE System Activity Log I only see Error 105 entries. on the day this occurs. Here are the steps I taken to try to get this to stop:
    1) Reviewed Windows 10 power saving mode - all options set to "Never"
    2) Checked the Network Adapter in Device Management: "Sleep = Never".
    3) Uninstalled/reinstalled SAGE 100 workstation client on user's computer
    4) Had the IT folks create a new Windows User Profile for this user.
    5) Renamed SY_Workstation.M4T and SY_Console.M4T in the MAS_System folder.
    6) Checked the SAGE 100 v2019 icon to make sure that SAGE is being launched using UNC path instead of  a mapped drive.

    Open to any suggestions or more detailed explanation of the above two error messages.  Also could there be anything in the Windows/Network  system logs that I can ask the IT folks to search for?  . 



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


  • 2.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 11:12
    Have you run Rebuild Keys for AR and/or SO?

    ------------------------------
    Michelle Taylor
    ERP Consulting Manager, CS3 Technology
    918-388-9772
    ------------------------------



  • 3.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 11:33
    No I have not because the client said "that most of the time "it seems to resolve itself" she just has to "shut down SAGE 100 and get back in". A few times the "cash receipts batch or the SO invoice has to be re-entered"

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

    Original Message


  • 4.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 11:36
    Edited by Alnoor Cassim 07-30-2020 11:37
    It sounds like you are on the right track. Be sure to adjust the power and network adapter settings for the other workstations too and at the server as well. Whether it's "unlock region failure" or "input output error" it sounds like a network disconnect happens at some point. The Error 105 is a classic data corruption and no doubt it stems from the disconnect. Maybe you need to have IT do some load tests on the switch or try a different port on the switch or temporarily swap it out.

    Do you know if it only occurs when she or others have left their wkstns idle for a while? If so, here is a longshot to check. 

    Without going into the weeds try these steps:
    1. Have her open a CMD prompt
    2. type IPCONFIG / ALL
    3. Look at the Lease Expired and Lease Obtained values. Pretend it is 1 full day / 24 hours.
    4. Divide that by 2. This means if PC is left idle for 12 hrs a DHCP Lease Renewal occurs (ip address is "refreshed") where by design a short ntwk disconnect occurs. Did she have Sage open at the time?

    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------



  • 5.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 12:51
      |   view attached
    @Alnoor Cassim​  It's interesting that you mention idle workstations. This client has 7 to 15 users who make it a practice to open a Customer Maintenance session or an Inventory Maintenance session in SAGE 100 and "park" there all day long. Even when they go home they do not logout of SAGE 100. Attached is a screen shot of SAGE 100 Master Console from a typical Tuesday evening after everyone has gone home. It show 7 active users.  Could all these "idle" workstations in an open SAGE 100 session be causing the Input\Output error that the AR/SO user is experiencing when she posts Cash Receipts and Sales Journals?

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

    Original Message


  • 6.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 13:02
    Edited by Alnoor Cassim 07-30-2020 13:25
    Yes especially If the AR/SO user is one of those that leaves Sage 100 open when going home at night.

    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------

    Original Message


  • 7.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 11:50
    Are they using a wifi connection?  I had something similar a couple of months ago and finally determined the user had a laptop and wasn't using the ethernet port/cable.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Assistant to the Traveling Secretary
    ------------------------------



  • 8.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 12:07
    @Doug Higgs No we (the IT folks) learned that lesson (SAGE 100 does not work on WIFI) ​many years ago. They know that all workstations running SAGE 100 must be hardwired.

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

    Original Message


  • 9.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 12:48
    As Alnoor and others mentioned it could something with the network adapter.  Looks at the Windows Event Viewer for network connection errors.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Assistant to the Traveling Secretary
    ------------------------------

    Original Message


  • 10.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 18:28
    @Alnoor Cassim and @Doug Higgs ​​ Thank you for your responses and assistance. I will try your suggestions.

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

    Original Message


  • 11.  RE: Help understanding SAGE error messages

    Posted 07-30-2020 20:42
      |   view attached
    @Alnoor Cassim Here is a screen shot of the IPCONFIG /ALL from the AR/SO user's workstation. Does the Lease Expire date mean that if she is idle with SAGE files open on her workstation on that date, she could experience data corruption and therefore Error 105s? ​

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

    Original Message


  • 12.  RE: Help understanding SAGE error messages

    Posted 07-31-2020 10:01
    The difference between Expires and Obtained is 12 days (the duration) meaning in 6 days (the 50% mark) a renewal occurs or in this case, attempted. It looks it didn't renew on 7/29 because you would've seen new Expired and Obtained date/times. Something seems off. It will try to renew again on 8/2 (87.5% mark). I would try to work with IT to have them:

    1a. Reboot wkstn PCs every 5 days or less. Thru Windows Task Scheduler or PowerShell they can schedule a reboot.
    OR
    1b. Don't reboot but force them out of Sage at a certain time every evening. A PowerShell script to kill all pvxwin32.exe tasks should work.

    2. Have them update to latest Realtek NIC driver for Windows 7 (looks like Windows 7). They're typically not detected by Windows Updates.

    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------

    Original Message


  • 13.  RE: Help understanding SAGE error messages

    Posted 07-31-2020 10:49
    Edited by Michael McDonald 07-31-2020 11:42
      |   view attached
    Here is a screen shot of the SAGE Master Console from last evening. Does the Acct Date field show the date that listed User "rogd" first accessed Customer Maintenance?  If he does not make any changes and just uses the maintenance screen for 'lookup purposes" does this show that User  = "rogd" has had the Customer Maintenance window open since 7/7/2020? 
    Could having all these users (assuming none are ghost users) in a open Customer Maintenance, Vendor Maintenance, or Item Maintenance (look at User = "kentb") function everyday cause the file corruption issues when the AR/SO person tries to post Cash Receipts in the AR module or a Sales Journal in the SO module?.
    Should I use the built-in SAGE Library Master function to force a user logout each day?

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

    Original Message


  • 14.  RE: Help understanding SAGE error messages

    Posted 07-31-2020 13:33
    The Accounting Date (Module Date) is acquired when a user accesses a task for the module for a given company code. It does not necessarily mean the date they opened Customer Maintenance since they could have opened say Cash Receipts Entry earlier on that date but have since closed that screen.

    If you suspect issues with the Acct Date in Master Console, then make a backup of then reinitialize the Sy_ModuleDate table. I would do that regardless.

    Those users being in the Maintenance screens do NOT inherently cause data corruption for the user updating SJ and CR journals. Usually the person doing the updating / posting has lost their continuous ntwk connection at some point in the Update.

    I understand using Auto-Logoff has some issues that others here could comment on but it sounds promising. But know the Launcher itself would still be open so it might still be advisable to do the PowerShell script anyway. 

    Another way to resolve the "unlock region failure" and "input output" errors is have them go through RDS / Terminal Server. In this case you may not want to have it as a separate server from the Sage server.

    Lastly, you mentioned no WiFi here, which Doug had mentioned, but we ourselves had a customer who's chief Sage 100 user had received a new Win 10 laptop which was setup in a Sage 100 friendly way (no power savers etc) before we were involved. She was hard wire Ethernet connected and working just fine in Sage until she did her Sales Journal Update where it blew up. Apparently at some point earlier in the day, her patch cable that goes from laptop to the wall became loose (at the wall) so her laptop auto switched to WiFi which didn't hold the connection long enough to the server for entirety of SJ update. So make sure this isn't happening either :-) 

    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------

    Original Message


  • 15.  RE: Help understanding SAGE error messages

    Posted 07-31-2020 14:32
    Edited by alan niergarth 07-31-2020 14:33
    You mention this is Sage 100 Standard, have the installation instructions changed from specifying a mapped drive versus UNC path?  

    2 Map a drive letter to a share at least one folder above the MAS90 folder where the Sage 100 Standard server component is installed.

    We've traditionally used mapped drives for standard and UNC for advanced.  is this just habit?  Or outdated instructions?

    ------------------------------
    alan niergarth
    Velosio LLC
    ------------------------------



  • 16.  RE: Help understanding SAGE error messages

    Posted 08-03-2020 11:43
    Edited by Michael McDonald 08-03-2020 11:45
    @alan niergarth We are still mapping a drive letter one folder above the MAS90 folder just like you state. for SAGE 100 Standard installs. Switching to the UNC path on the SAGE icon was recommended in a Sage City post by Alnoor  i​n response to the Input\Output error SY_Session.PVC as something to try on Windows 10 pc's, to help stop this random recurring error.

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

    Original Message


Related Content