After installing Sage 50 in a client/server configuration, Sage 50 failed to start on the client workstations. The Sage 50 application window briefly opened and then closed without displaying an error message. The following error was recorded in the Windows Applications event log:

Application: Peachw.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
    at Sage.Peachtree.BusinessLogic.ApplicationLogic.PervasiveKeyState.GetKeyStateForDBServer()
    at Sage.Peachtree.UI.Activation.ActivationController.CheckActivation()
    at .CheckActivation()
    at .CheckActivation()
    at .PAWLegacy.CPeachwApp.InitInstance(PAWLegacy.CPeachwApp*)
    at PAWLegacy.LegacyStartup.StartPAW()
    at Peachw.Program.Main(System.String[])

A Sage technical support representative instructed me to disable IPv6, stating that Sage 50 does not support IPv6. The Sage technical support representative also provided me with a link to the Error: "Sage 50 cannot be started..." and Internet Protocol version 6 (IPv6) is enabled Sage knowledgebase article.

Sage 50 works after IPv6 is disabled. However, disabling IPv6 on every computer does not seem like a good long-term solution. Is it possible to force Sage 50 and Pervasive PSQL (which is the database used by Sage 50) to use IPv4 without disabling IPv6?

The LAN in question uses and the Sage 50 server computer has an address of

  • That's not even a good short term solution! Especially when you already have IPv6 in production and can't possibly "disable" it. The error makes it clear this is an obvious bug, and it's one that the vendor should fix. You might be able to get by with just disabling IPv6 transition technologies (which actually should be disabled if not in use) without disabling IPv6. – Michael Hampton Jul 11 at 16:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.