Sage 50 Quantum 2024 - terminal server - works fine with demo company until activated then "bad key file" post activation?

SOLVED

Odd problem, sage install and runs just fine on a new terminal server (windows 2022) build, installed using both change user /install or via control panel add app, same result. Once installed and before activation you can open, update and run a sample company file. Activation while in sage works, with a success message followed immediately by a "bad key file" error. Activation with sage closed same success message but not bad key file error.

Try to open sage post activation it flashes' and that's it, wont' open.

Originally thought it was a bad DOT NET install, and checked/repaired that with no success, once I activated with sage open it popped the bad key file error.

Antivirus shows no sign of interference or blocking 

I'm at a loss as to why  - any help would be appreciated.

Parents Reply Children
  • 0 in reply to Paul_R
    SUGGESTED

    Hi  ,

    Thank you for detailing the issue you're experiencing with Sage on your new Windows 2022 terminal server. I was unable to find your account details with us based on your profile here but feel free to email me the details here to forward onto the team.

    Here's a quick rundown based on this article's content:

    1. Connection Manager: Ensure that the Sage 50 Connection Manager is installed and properly configured to bind to the TCP protocol. Verify IP/Hostname resolution is correct.

    2. Firewall Settings: Make sure the necessary ports and processes are allowed through your firewall for Sage 50 to operate correctly.

    3. User Permissions: Right-click on your Sage data folder and adjust the sharing and security settings. Test accessing the data from various workstations.

    4. Service Log On: Add the local server administrator (not global admin) to the Log On tab for the Connection Manager Service. Restart the service and test.

    5. Local Permissions: Navigate to 'secpol.msc' and add network users to the User Rights Assignments.

    6. Network Cards: If the server has multiple network cards, disable all but one to test the connection.

    7. Re-examine .NET Install: Since you mentioned a suspicion about .NET, it might be beneficial to completely uninstall and reinstall it, even if the repair showed no issues.

    If you've already followed these steps and the problem persists, we would recommend reaching out to our support team. 

    For further assistance, you can consult our support resources at Point right www.Sage.com/Resources or phone 1-866-996-7243 during regular business hours.

    Hope this helps!

    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    We are an IT provider this as a client setup, so you would not have found an account under my profile info. Thanks for reaching out, it was resolved per my post.