x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 2 replies
  • Subscribers 96 subscribers
  • Views 1793 views
  • Users 0 members are here
Browse Forums
Announcements
150
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
631
topics
888
replies
Reporting and Analytics
573
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
435
topics
671
replies
Year End
83
topics
128
replies
jgielski

Sage 50 Clients Silently Crashing on Start Up

SOLVED
Posted By

Good Afternoon

We are running Sage 2020.1 on a Windows 2012 server. We rebooted our server last night and started noticing our client machines would attempt to load Sage 50, but then it would fail and close with no error message. We can still boot up sage directly at the server and login to all our companies just fine though.

Every client however crashes with no error message before it even brings up the company log in screen.


We have tried

  • Restarting Pervasive at the server.
  • Repairing Pervasive and Sage 50 at the server.
  • Reinstalling the .NET Framework on clients.
  • Repairing Sage and Pervasive on clients.

Event viewer shows 2 errors, but this one comes first which probably means the second one is caused from this one everytime we attempt startup.

Any ideas?


Application: Peachw.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Sockets.SocketException
at System.Net.Sockets.TcpClient..ctor(System.String, Int32)
at Pervasive.Data.SqlClient.Lna.ac.ce()
at Pervasive.Data.SqlClient.az.d()
at Pervasive.Data.SqlClient.az.a4()
at DDInt.Common.aj.a7()
at DDInt.Common.ak.b(DDInt.Common.j, DDInt.Common.z)
at DDInt.Common.al.j()
at DDInt.Common.al.a(System.Transactions.Transaction, DDInt.Common.ai)
at DDInt.Common.ak.a(System.Object, DDInt.Common.j, Boolean, DDInt.Common.ai)
at Pervasive.Data.SqlClient.PsqlConnection.Open()
at Sage.SBD.ACS.Framework.DataAccess.DbOperationContext.Open()
at Sage.SBD.ACS.Framework.BusinessLogic.Entity.GetSafeDbOperationContext(Sage.SBD.ACS.Framework.DataAccess.DbOperationContext, Sage.SBD.ACS.Framework.DataAccess.DbOperationContext ByRef)
at Sage.SBD.ACS.Framework.BusinessLogic.Entity.TryLoadInternal(Sage.SBD.ACS.Framework.DataTypes.KeyInfoBase, Sage.SBD.ACS.Framework.DataAccess.DbOperationContext)
at Sage.SBD.ACS.Framework.BusinessLogic.Entity.TryLoad(Sage.SBD.ACS.Framework.DataTypes.KeyInfoBase, Sage.SBD.ACS.Framework.DataAccess.DbOperationContext)
at Sage.SBD.ACS.Framework.BusinessLogic.Entity.TryLoad(Sage.SBD.ACS.Framework.DataTypes.KeyInfoBase)
at Sage.Peachtree.BusinessLogic.SerialNumbers.get_IsProductActivated()
at Sage.Peachtree.BusinessLogic.EntitlementService.Lookup(System.String)
at Sage.Peachtree.BusinessLogic.EntitlementService.GetDateValue(System.String)
at Sage.Peachtree.BusinessLogic.EntitlementService.GetSageDriveSubscriptionEndDate()
at Sage.Peachtree.BusinessLogic.SageDriveService.get_EndDate()
at Sage.Peachtree.BusinessLogic.SageDriveService.GetNumberOfDaysExpired()
at Sage.Peachtree.BusinessLogic.SageDriveService.IsExpired(Boolean)
at <Module>.IsSageDriveSubscriptionExpiredInterop()
at <Module>.IsSageDriveSubscriptionExpiredInterop()
at <Module>.PAWLegacy.CPeachwApp.InitInstance(PAWLegacy.CPeachwApp*)
at PAWLegacy.LegacyStartup.StartPAW()
at Peachw.Program.Main(System.String[])

  • +1
    verified answer

    I've been battling this all day. After investigating the logs, I think it was actually a memory / caching issue on our server from a faulty start up. I ran the repair tool on pervasive and then immediately rebooted the server and it fixed the issue. I did both those steps previously, but not in sequence for those facing similar issues.

    Last Note: I'm a .NET developer working this as a side issue from my primary duties. Unhandleds can be caught globally in App.xaml.cs (assuming this is a WPF app) which would eliminate silent crashes from unhandleds in 95% of cases devs. Even if pervasive is the issue, the app shouldn't crash due to an UnhandleException, as it make dissecting with support take way longer.

    As the Event Log will show a .NET failure (as seen above), support will automatically default to (reinstall .NET) which will never fix this problem.


    Unhandleds have only bitten me like 10000 times so I know the pain and I promise I am not judging here lol.

    https://stackoverflow.com/a/1472562/3133249

    Reach out if you want more info on that, I would love to help.

    Still love Sage 50!!!

  • 0 in reply to jgielski

    Whoa thanks for circling back and sharing your detailed findings ! Slight smile

*Community Hub is the new name for Sage City