x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 134 subscribers
  • Views 853 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
758
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
Llew

Intermittent Issues following ERP2022 Upgrade

Posted By

Following an upgrade from ERP2018 to Sage ERP2022 (PU2), we have started experiencing intermittent issues in our environment when opening Sage - I have been scouring the forums and 'google' to no avail.

The upgrade was done on the same servers etc as the previous release, so nothing in terms of the environment changed - just the programs were upgraded. Sage programs are installed on multiple terminal servers with load balancing, SQL DB's are on a different server, and Shared Data is on the third server. The environment is hosted in a private Azure cloud.

The following issues have been experienced since the upgrade:

1. It takes way longer to open a company with the 'Connecting to Database' message showing for significantly longer than before. Previously you barely noticed it.

2. Intermittent error - cannot access lanpak.bin in site folder: Checked all the usual things and no issues, as mentioned the upgrade was done over the top of the old version, so all PATH variables, reg settings etc have been checked, and permissions have not changed since the upgrade. I am an administrator also. When this happens, I can close the message, then open a different company, then switch back and it's fine.

3. Opening Sage screens is taking way longer than the previous version. Does this mean ERP2022 is just 'slower' than 2018, or has something in fact changed?

The issues are experienced on new datasets too, so db size etc are not complicit here. In the Sage setup, SQL server name is used. I believe the environment is hosted by 

If there is anything I left out that might be pertinent to help me understand what might be happening, I apologise. Any assistance to troubleshoot would be appreciated. 

  • 0

    If you have troubles with Lanpak.bin, you have a lousy network.  You can't run Sage over a WAN, make sure the Ping between all servers and clients is <1 Ms,  And check the PATH for servers that are turned off.

  • 0

    Hi Llew, we're in a very similar boat after upgrading from 2020 to 2023 and have a near identical server infrastructure.  Were you ever able to resolve your issues?

    We have been troubleshooting this and banging our collective heads against the wall for a couple of weeks now with no substantial progress.

    Thank you!

  • 0

    I found the other day that if I had the user screen open that the lanpak.bin error message came up for others, once I closed that, everyone could get in but it's been happening a lot lately, especially the last couple of months at a client that upgraded to 2022 last year.
    We can't all have lousy servers so it must be something since the upgrade.
    I have turned off the advisor which slows things down so it's not that on my site but it could be an issue elsewhere for others.  See KB110298

  • 0

    Hi Llew,

    it appears that Sage found this as a bug with interface with some 3rd party applications.  The fix is suppose to be in UPD4 for V2023.  Have you loaded it yet?  where the results positives.   

  • 0

    Hi LLew,

    I work with Mark (above) and we have since loaded PU5 for 2022.  Unfortunately our LANPAK.BIN error persists.  Did you ever make any progress on resolving your issues?  We have tried every troubleshooting step we can find to no avail.

    Thank you,

    TD

  • 0 in reply to Thomas Duermeier

    These are all the things I would check:

    Low hanging fruit:

    • Make sure you're using ODBC Driver 18 for SQL Server and make sure you're using a version of Microsoft SQL Server that fully supports it - what version of SQL are you running?  Make sure you're not still trying to connect with the SQL Native Client 11 used with version 2018.  Make sure your ODBC Driver 18 has the Trust Server Certificate or Optional Encryption set so its not sitting there trying to negotiate a secure connection.
    • If you moved from Perpetual to Subscription Licensing, make sure all Terminal Servers in the farm have outbound access to the firewall to the Entitlement server - it could be a delay for the client trying to get through to the licensing server to validate the entitlements.
    • How much memory and vCPU's are allocated to the SQL server, and how large are your databases combined?
    • Ensure you have a SQL Maintenance plan in place that does a periodic offline rebuild of the indexes - use Ola Hallengren's classic plan, or do a weekly reorganise and a rebuild monthly after hours with the first rebuild done ASAP.
    • Make sure you have your Sage 300 share - applications and shared data fully excluded from any antivirus applications.  I know this shouldn't have changed but I've seen many crazy things.
    • Check the Event Viewer on your Sage 300 Application Server to see if there are any events recurring over and over.
    • If you have a Startup folder in Sage 300 make sure there aren't old screen references left in there.
    • If you have changed any of your folder structure during the new install, ensure the path under Customization Directories isn't out of date.
    • Check Task Manager processes on the Application Server and SQL Server, adding the column CPU Time and sorting by it.  This will tell you if a service or executable is going haywire.

    Get out the ladder:

    • Re-dump and load your company databases using Sage 300 DB Dump and DB Load.  This is especially critical if you performed any SQL BAK and restore processes during the upgrade because something went wrong.  Dumping and Loading will clean up broken indexes and many other issues.
    • If you don't use the Web Screens and you installed them, try stopping your Sage.CNA.WindowServices service and disable it.
    • On your RDS server or workstations, uninstall Sage 300 workstation setup then in Programs and Features type C++ into the search bar and uninstall all references and versions of C++ Redistributable then re-install Workstation Setup.
    • Did you implement any new backup or monitoring of the VM's that could have added overhead?

    See how you go with these first and let us know.  Good Luck...Tim

*Community Hub is the new name for Sage City