x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 59 subscribers
  • Views 918 views
  • Users 0 members are here
Browse Forums
Announcements
78
topics
166
replies
General Discussion
5k
topics
16k
replies
Installation and Upgrades
982
topics
2k
replies
Inventory, Projects, and Departments
339
topics
1k
replies
Payables and Receivables
1k
topics
4k
replies
Payroll
1k
topics
3k
replies
Reconciliation and Banking
318
topics
997
replies
Reporting and Analytics
207
topics
401
replies
Soutien Technique - Français
632
topics
1k
replies
Year End Activities
224
topics
596
replies
Paul_R

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

SOLVED
Posted By

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 Richard S. Ridings

    Thank you Richard, yes I have also followed that article completely, as well as removed the antivirus, confirmed option 5 is disabled, re and re'd the software from scratch - no joy. Activation is successful and Quantum then immediate fails to open post activation. Event ID 1026 .NET runtime has an unhandled exception error, followed by an application error ID 1000, both listed below

    Why does it work fine until activated? I find this curious..

    Note that when activated these changes are happening in the "C:\Users\Public\Public Documents\Sage Software" directory per the KB article saying files are missing

    C:\Users\Public\Documents\Sage Software\Simply Accounting\2024\1 has two new or updated files simacct$.dat and simply.cfg

    C:\Users\Public\Documents\Sage Software\Simply Accounting\Logs\2024 has one new file Sage50_N_203-10-17_1.log and this only logs startup and shutdown events.

    that is the extent of the changes post activation per the files date/time stamps.

    ID 1026: Application: Sage50Accounting.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.NullReferenceException
    at Simply.Domain.Utility.RegisterData.ReadSimBusKeyFile(System.String)
    at Simply.Domain.Utility.RegisterData.ReadSimAcctData(Boolean)
    at Simply.Domain.Utility.RegisterData.ReadSimAcctData()
    at Simply.Domain.Factories.SalesCodeVersionFactory..ctor()
    at Simply.Domain.Factories.SalesCodeVersionFactory+NormalVersion..ctor()
    at Simply.Domain.Factories.SalesCodeVersionFactory+Enterprisebuild..ctor()
    at Simply.Domain.Factories.SalesCodeVersionFactory+NormalVersion.CreateNormalVersion()
    at Simply.Domain.Factories.SalesCodeVersionFactory.CreateSalesCodeVersion()
    at Simply.Domain.Factories.SalesCodeVersionFactory.get_Instance()
    at Simply.UI.Start.SplashScreenUI..ctor()
    at Simply.UI.Start.SplashScreenUI.DisplaySplashScreen()
    at <Module>.DisplaySplashScreen()

    ID 1000: Faulting application name: Sage50Accounting.exe, version: 31.0.0.1, time stamp: 0x650544ba
    Faulting module name: KERNELBASE.dll, version: 10.0.20348.2031, time stamp: 0x3af8fc2f
    Exception code: 0xe0434352
    Fault offset: 0x00138d52
    Faulting process id: 0xc48
    Faulting application start time: 0x01da028153cf6192
    Faulting application path: C:\Program Files (x86)\Sage 50 Quantum Accounting Version 2024\Sage50Accounting.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 733e7172-69e4-4add-8a21-3bfa929b6461
    Faulting package full name:
    Faulting package-relative application ID: 

*Community Hub is the new name for Sage City