Sage 50 2016 crashes

[Galdorf]

I have scanned windows 10 for viruses and malware, cleaned registry for some reason sage 50 2016 crashes when you try to run it.
Tried revo uninstaller- then re-install still crashes sfc show no problems even tried running it on a clean startup any ideas?.

 

[Kitten Kong]

What anti virus is running?

 

[Kitten Kong]

I had issues with this with a client a few months ago. Is it an error similar to sbddesktop.exe?

If so, it 'could' be the av which is installed. In my case it was Bit Defender (MAV). I had to add a lot of exclusions.

 

[Galdorf]

What anti virus is running?

AVAST

 

[Kitten Kong]

Firstly try adding all the sage directories to the exclusions (if it exists in avast). If not, remove avast completely, and try again.

 

[TurricanII]

And also try right clicking the Sage icon and setting compatibility to Windows 7.

Sage 2016 needs the Sage services to be installed and running. Are they installed and running on the machine holding the company data? If on a mapped drive, this means that the services need to be on the server.

 

[Galdorf]

Firstly try adding all the sage directories to the exclusions (if it exists in avast). If not, remove avast completely, and try again.

Seems there were leftovers of Mcafee antivirus i removed them no more crashes , used ad remove programs and uninstalled it but it left services running!.

 

[Galdorf]

Ok it worked a few times but keeps crashing after looking at logs there seems to be issues with .net framework and mysql trying to find a reason for it?.

Faulting application name: Sage50Accounting.exe, version: 23.20.0.1, time stamp: 0x575b6f32
Faulting module name: System.Runtime.Serialization.ni.dll, version: 4.6.1038.0, time stamp: 0x5615cb25
Exception code: 0xc0000005
Fault offset: 0x00050270
Faulting process id: 0xb58
Faulting application start time: 0x01d1fd7d7c723d4f
Faulting application path: C:\Program Files\Sage 50 Pro Accounting Version 2016\Sage50Accounting.exe
Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\2f18aee9e26301da57394e94416a20ba\System.Runtime.Serialization.ni.dll
Report Id: 53439364-9c90-4da0-ae6a-198b246d745c
Faulting package full name:
Faulting package-relative application ID:


------------------------------------------------------------------------------------------------------------------------------------------
Application: Sage50Accounting.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Simply.Domain.CollectData.IS50CollectDataService.IsCollectDataFeatureEnabled()
at Simply.Domain.CollectData.S50CollectDataServiceClient.IsCollectDataFeatureEnabled()
at Simply.Domain.CollectData.CollectDataFeatureSwitchWebService.DoWebRequest()
at Simply.Domain.CollectData.CollectDataWebService.SubmitRequest()
at Simply.Domain.CollectData.UploadCollectDataBaseThread.UploadingDataOnce(System.Object, System.ComponentModel.DoWorkEventArgs)
at Simply.Domain.CollectData.UploadCollectDataBaseThread.DoUploadingWork(System.Object, System.ComponentModel.DoWorkEventArgs)
at Simply.Domain.CollectData.UploadCollectDataBaseThread.Worker_DoWork(System.Object, System.ComponentModel.DoWorkEventArgs)
at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

 

[Galdorf]

Ok it only crashes when hooked up to a network or the internet. runs fine if i disconnect the lan cable?.

 

[Kitten Kong]

Possible.

Have you spoke to sage support?.

They are generally really helpful.

 

[Galdorf]

Possible.

Have you spoke to sage support?.

They are generally really helpful.

Yes they spent hours trying to fix it i think im going to just backup and format reload as trying to guess what might be happening may take too long, all they said was there is something blocking it, removed all AV, security programs ,and other running processes ect. did not help, disabled firewalls, check hosts and sfc errors.

 

[YeOldeStonecat]

Just had to chime into this thread...not Sage 50 related, but had a Sage Timeslips experience this afternoon for 2 and a half hours upgrading a clients database to the new 2017 format. Ugh.