Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
I recently upgraded to AR 2018 and was pleased that for the first week, things went smoothly. However today three times so far I am getting an error message that something's gone wrong and AccountRight needs to close.
The first time it happened was when I was looking for open bills and changed the time frame to 1/7/17 to today.
I am using Win7 - I notice on the board a number of similar threads, so I guess this is not an isolated case, though the solutions suggested vary a bit.
I would appreciate some advice on how to continue.
The error report generated is:
AccountRight Application Error Report
Application Version: 2018.2.20.8598
Application File Version: 2018.2.21.806
Incident Id: 053fede6-3045-4356-a171-672cc2bda796
Time: Tuesday, 21 August 2018 2:40:57 PM
The null value cannot be assigned to a member with type System.Decimal which is a non-nullable value type.
1 : System.InvalidOperationException
System.InvalidOperationException: The null value cannot be assigned to a member with type System.Decimal which is a non-nullable value type.
at mscorlib!0x060056de!System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +0x27
at mscorlib!0x060056e9!System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +0x1b3
at Huxley.Service.Gateway!0x06000001!MYOB.Huxley.Service.Gateway.API.IGatewayService.Dispatch(String name, Object arguments)
at Huxley.Service.Proxy!0x06001418!MYOB.Huxley.Service.Proxy.Services.ProxyPurchaseRegisterContainerService.GetAllPurchaseRegisterSummary(IEnumerable`1 objectSetVersions, Nullable`1 cardId, Nullable`1 from, Nullable`1 to) +0x0
at Huxley.UI.Decorators!0x060005af!MYOB.Huxley.UI.Decorators.Services.DecoratorServiceMYOBHuxleyApplicationServicesContainerAPIIPurchaseRegisterContainerService.MYOB.Huxley.ApplicationServices.Container.API.IPurchaseRegisterContainerService.GetAllPurchaseRegisterSummary(IEnumerable`1 objectSetVersions, Nullable`1 cardId, Nullable`1 from, Nullable`1 to) +0x58
at Huxley.UI.Model!0x06003b6f!MYOB.Huxley.UI.Model.Context.PurchaseRegisterContext.<>c__DisplayClass1.<GetAllPurchaseRegisterSummary>b__0() +0x0
at Huxley.UI.Model!0x060000b3!MYOB.Huxley.UI.Model.Context.Base.UIContextContainer`2.InvokeContainerGet(Func`1 getFunction, Boolean force) +0x5f
at Huxley.UI.Model!0x060001a0!MYOB.Huxley.UI.Model.Context.PurchaseRegisterContext.GetAllPurchaseRegisterSummary(Nullable`1 cardId, Nullable`1 from, Nullable`1 to) +0x2f
at Huxley.UI.Controllers!0x06002339!MYOB.Huxley.UI.Controllers.Purchases.PurchaseBillControllerView.DoWork(DoWorkEventArgs e) +0x45
at Huxley.UI.Controllers!0x06000250!MYOB.Huxley.UI.Controllers.Base.BasePresentationController`1._worker_DoWork(Object sender, DoWorkEventArgs e) +0x0
at System!0x0600311b!System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) +0x19
at System!0x0600312b!System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) +0xe
MODULE: Huxley.Service.Gateway => Huxley.Service.Gateway, Version=2018.2.20.8598, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:ab04cd8294a04273b81ae660652f4d4d; A:1
MODULE: Huxley.Service.Proxy => Huxley.Service.Proxy, Version=2018.2.20.8598, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:7d10411c1bac4e17bc9453afb465e5cc; A:1
MODULE: Huxley.UI.Controllers => Huxley.UI.Controllers, Version=2018.2.20.8598, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:78bcd4898b8248e6997dee412557d9e0; A:1
MODULE: Huxley.UI.Decorators => Huxley.UI.Decorators, Version=2018.2.20.8598, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:2c1a001a76d24dc294ccdc2fe9424642; A:1
MODULE: Huxley.UI.Model => Huxley.UI.Model, Version=2018.2.20.8598, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:dd8ecb68a2ea401c8560da7b71b1d309; A:1
MODULE: mscorlib => mscorlib, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:b55f9c79e6884b24916565039d43ab58; A:2
MODULE: System => System, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:7a9276a0eddb40a9bd470cbaa198edd8; A:2
Solved! Go to Solution.
I have seen his error occur when we are attempting to open the Purchases Register, or a Purchase in general. This is caused by an error in the database as there is a Null Value where one should not exist.
We do have a Script that can be run for this, depending on if the file is online or offline depends on who can run the script:
If your company file is online:
We can run an Online Script that any MYOB Moderator can run, just grab:
Once you have this, just click Reply on this Post and post this information.
If your datafile is local:
You can download a Hotfix tool that applies the script offline. Here are the details involved:
Task 1 - Back up your Company File:
You should always create a backup of your company file before completing any maintenance tasks. For instructions, see: Back up your company file
Task 2 - Use the repair tool:
Before using this tool, make sure you have backed up your company file as described in the previous task.
Complete these steps on the computer where the company file is stored, or has been checked out to:
Click Browse and locate your company file in the My AccountRight Files folder here:
C:\Users\<user.name>\My Documents\MYOB\My AccountRight Files (where is the name of the person currently logged into Windows)
C:\Users\Public\Public Documents\MYOB\My AccountRight files
This should then correct the issue, please note you may need to close and re-open the software in order to see the changes.
Please let us know how you go.
August - last edited August
thank you for your assistance. The file is online.
The info is:
AR Plus 2018.2.1 with Build 2018.2.21.806
Thank you for the details there, I have now run the script over your online file. This should now have corrected the error.
You may need to close and re-open the file to see the changes.
Please let me know if this has now solved the troubles.
thanks for your help. I had a quick look and so far it seemed stable. I don't have much time now nor
transactions to enter but will report back at the end of the week once the program has run again for a while
with a number of varied transaction being entered.
once again - thank you for your help. I have worked on the file again for some time and the issue has not come up again, so it seems the script you used did the job.