x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 18 replies
  • Answers 3 answers
  • Subscribers 103 subscribers
  • Views 3196 views
  • Users 0 members are here
Browse Forums
Announcements
150
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
631
topics
887
replies
Reporting and Analytics
573
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
434
topics
671
replies
Year End
83
topics
128
replies
Harold Bailey

2024.0.1 Sage 50 Update Issue

SOLVED
Posted By

This is more an FYI than a question. After the first in-place upgrade I performed, I noticed there was another performance patch waiting (PTXA2024.0.1) immediately after upgrading all the client installs and updating the company file. At the next client, the upgrade was a fresh install on a new server. i installed the performance patch immediately after migrating and updating the company file, and before upgrading the workstations (full uninstall and manual cleanup of 2023 and running the ClientInstall.bat from the new server). The client installs failed with, "Sage 50 cannot connect to your Sage 50 company data location." After a lot of troubleshooting and a full uninstall and reinstall of Sage 50 on the server, the client installs ran fine before I installed the performance patch. Out of curiosity, I tested this at the next in-place upgrade (2023 Quantum to 2024 Quantum). Workstation upgrades could be performed from \\server\\PeachtreeInstaller2024 before I installed the performance upgrade, but not after. The share was still accessible over the network after the performance patch was installed. The fix was to do a repair installation of Peachtree 2024, but not install the perfomance patch until after all workstations had been upgrade/installed, and then apply the performance patch to all machines, starting with the server.

tl;dr:  After you install Sage 50 2024 performance patch PTXA2024.0.1, you will be unable to run the ClientInstall.bat batch file from \\server\\PeachtreeInstaller2024 to upgrade workstations or perform new, clean installs. You will get the error, "Sage 50 cannot connect to your Sage 50 company data location." This happens whether you modify the ClintInstall.bat to point to a data file location that is a mapped drive letter or the UNC path. The registry edit, "EnableLinkedConnections=1" had been applied. The fix is a repair install of Sage 50 without installing the PTXA2024.0.1 performance patch until all workstations have been installed/upgraded.

  • 0
    SUGGESTED

    Hi  ,

    Thank you for taking the time to share this valuable information. Your detailed account of the issues encountered with the Sage 50 2024.0.1 update and the subsequent performance patch is greatly appreciated and will certainly be helpful to others in the community.

    For those coming across this post, here is a paraphrased summary of Harold's findings and the steps to resolve the issue:

    1. When you upgrade to Sage 50 2024 and then apply the PTXA2024.0.1 performance patch, it may prevent the ClientInstall.bat from connecting to your company data location during workstation upgrades.
    2. This problem persists whether using mapped drives or UNC paths, even with "EnableLinkedConnections=1" set in the registry.
    3. To fix this, perform a repair installation of Sage 50 on the server without the performance patch.
    4. Only after all workstations have been successfully upgraded or installed, apply the performance patch to the entire network, starting with the server.

    By following these steps, you should be able to upgrade workstations without encountering the connectivity error. Thanks again, Harold, for sharing your solution.

    Warm Regards, 
    Erzsi

  • 0

    Hi, this happened to me just yesterday, but on 2 out of 6 client installations.  One is Win10 and the other one is win11.  Thanks for the fix!

  • 0

    Okay... But screwing around with the server seems like an annoying step. Does anyone know what the actual root cause is...?

  • 0 in reply to Erzsi_I

    No one is going to be searching for this solution until after they've already installed the patch on their servers and are receiving errors on workstations. To imply that this is a "fix" is a bit misleading in my opinion.

    Assuming we've arrived at this message thread because we've already installed the patch on the server... and for those of us who don't want to go through the horrible hassle of bringing down the server, backing up our data, uninstalling and reinstalling... what is the more reasonable and permanent solution to this issue?

  • 0 in reply to Walt S

    Agreed. Very unprofessional of Sage to recommend a workaround that would be extremely inconvenient and a huge hassle.

  • 0 in reply to Erzsi_I
    SUGGESTED

    Hi everyone,

    The team has confirmed that the 2nd January tax update is tentatively scheduled for release on 2/8/24. Stay tuned for the announcement coming soon. 

    Warm Regards,
    Erzsi

  • 0 in reply to BG4C
    SUGGESTED

    I had this same issue yeterday at a client ugprade, I fixed it without running a repair install.  Instead, go to the company directory, locate the PVSW.LOC file, right click on it and check the Read Only box, then go back to the workstation and run the installer.  Or I just hit the back button in the wizard and then when back through and it completed just fine.  This also happened while 15 users were actively using the system and no one complained of any interruptions or issues.  [email protected]  

  • 0 in reply to bottomline

    Thanks for the post. A Sage tech recently told me the same thing.

  • 0

    I have to admit I read the headline and had flashbacks of last year's upgrade disaster. We just got notice of Sage 2023's obsolescence date of March 6th. I am dreading this upgrade just like nearly every other before it. 

  • 0 in reply to killertunes

    I think they need to focus less on upgrading the software every year and spend more time developing good products before they're released.

*Community Hub is the new name for Sage City