So disappointing sitting on hold for an hour and a half and getting no answer.
I keep getting the above message anytime I enter invoices. It can be for any client, any stage of the entering purchases and it can be multiple times
Is there a simple way to work out why this is happening and to stop it?
Closing down each time I make an entry is time consuming and frustrating.
If you attach the error report or diagnostic log, someone might be able to narrow it down. Somewhere something is missing in your file. Look under Setup > Linked accounts to ensure there is a linked account for every feature you use. Then look under List > Tax Codes to check that every tax code you use has a linked account for tax collected and tax paid.
Regards
Gavin
Here is a copy of the error report
AccountRight Application Error Report
=====================================
Application Version: 2022.3.24.6313
Application File Version: 2022.3.24.6313
Incident Id: b8218d61-4ee6-43d5-9172-3c862ab81005
Time: Tuesday, 17 May 2022 11:27:04 AM
Code:
System.NullReferenceException
Message:
Object reference not set to an instance of an object.
Stack Trace
----------------------------------------
1 : System.NullReferenceException
----------------------------------------
System.NullReferenceException: Object reference not set to an instance of an object.
at mscorlib!0x0600572c!System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +0x27
at mscorlib!0x06005737!System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +0x1b3
at Huxley.Service.Gateway!0x06001a03!MYOB.Huxley.Service.Gateway.API.IGatewayService.Dispatch(String name, Object[] arguments)
at Huxley.Service.Proxy!0x0600152c!MYOB.Huxley.Service.Proxy.Services.ProxyPurchaseEventService.Validate(Object entity, IEnumerable`1 propertyNames) +0x0
at Huxley.UI.Decorators!0x0600268a!MYOB.Huxley.UI.Decorators.Services.DecoratorServiceMYOBHuxleyAPIServicesAccountingIIntPurchaseEventService.MYOB.Huxley.API.Services.Core.IValidator.Validate(Object entity, IEnumerable`1 propertyNames) +0x52
at Huxley.UI.Model!0x06002944!MYOB.Huxley.UI.Model.Facades.Base.UIObject`1.OnBackgroundWorkerValidate(Object entity, IEnumerable`1 propertyNames) +0x0
at Huxley.UI.Model!0x06002943!MYOB.Huxley.UI.Model.Facades.Base.UIObject`1.validationBackgroundWorker_DoWork(Object sender, DoWorkEventArgs e) +0x22
at System!0x0600314c!System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) +0x19
at System!0x0600315c!System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) +0xe
--- End of stack trace from previous location where exception was thrown ---
at Huxley.UI.Model!0x06002941!MYOB.Huxley.UI.Model.Facades.Base.UIObject`1.validationBackgroundWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) +0x0
at System!0x0600314d!System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e) +0x19
at System!0x06003146!System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg) +0xe
==========
MODULE: Huxley.Service.Gateway => Huxley.Service.Gateway, Version=2022.3.24.6313, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:1d7a7f9678084520808cb0916c7571d4; A:1
MODULE: Huxley.Service.Proxy => Huxley.Service.Proxy, Version=2022.3.24.6313, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:26d40ac656374784a52df4f095e95591; A:1
MODULE: Huxley.UI.Decorators => Huxley.UI.Decorators, Version=2022.3.24.6313, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:3c2aed10339944a99a058a388128b33f; A:1
MODULE: Huxley.UI.Model => Huxley.UI.Model, Version=2022.3.24.6313, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:7a0abd3077dd4a6993c2194d3b2cb21a; A:1
MODULE: mscorlib => mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:e802975d87a14ffa8a6a0836952ea231; A:2
MODULE: System => System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:9356c0a4d80e4e679da8d57f9dae1dd9; A:2
Hi Receptionist1
This has been an issue now for 12+ months (I can't remember what version it was introduced) and MYOB has no interest in addressing the issue. There are a couple of issues they introduced and still waiting to be fixed.
Thank you aaa2
PAINFUL!
Hi Receptionist1 , aaa2
We're sorry to hear that you're impacted by this. Please refer to this help article for fixing this error and let us know if you're still impacted so we can escalate it.
