Error Message when sending payslips, purchase orders, statements

[Tamarahhh]

Hi 

I am getting an error message everytime I try and send payslips, statements, purchase orders

the error message i get is below. Also when I try to close the 'review payslips before delivery window' it says its still working and I have to wait until they are sent but its not doing anything.

Thank-you

AccountRight Application Error Report
=====================================
Application Version: 2019.2.22.2609
Application File Version: 2019.2.22.5066
Incident Id: 83e0c361-9691-4ad2-92e9-147527207e64
Time: Friday, 30 August 2019 9:17:47 AM

Code:
System.InvalidCastException

Message:
Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063001-0000-0000-C000-000000000046}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).

Stack Trace
----------------------------------------
1 : System.InvalidCastException
----------------------------------------
System.InvalidCastException: Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063001-0000-0000-C000-000000000046}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
at mscorlib!0x0600420a!System.StubHelpers.StubHelpers.GetCOMIPFromRCW(Object objSrc, IntPtr pCPCMD, IntPtr& ppTarget, Boolean& pfNeedsRelease)
at Microsoft.Office.Interop.Outlook!0x06002365!Microsoft.Office.Interop.Outlook.ApplicationClass.CreateItem(OlItemType ItemType)
at Huxley.MsOffice.Integration!0x06000078!MYOB.Huxley.MsOffice.Integration.OutlookEmail.OutlookEmailProvider.SendMessage(String emailAddresses, String subject, String body, EmailResourceType resourceType, String documentNumber, IEnumerable`1 attachments) +0xf7
at Huxley.UI.Controllers!0x060011d4!MYOB.Huxley.UI.Controllers.Helpers.EmailHelper.SendEmail(String to, String subject, String body, String pdfFileName, EmailResourceType resourceType, FormTemplateDefinition formTemplateDefinition, FormPrintingParams formPrintingParams, IEnumerable`1 attachements, Nullable`1 entityUid, LayoutType layoutType, String documentNumber) +0xd0
at Huxley.UI.Controllers!0x060021d2!MYOB.Huxley.UI.Controllers.Payroll.EmailPaySlipsController.<SendEmailsOneByOne>b__35_0(EmailHelper helper) +0xa5
at Huxley.UI.Controllers!0x060011d8!MYOB.Huxley.UI.Controllers.Helpers.EmailHelper.SendEmail(Func`2 doSend) +0x0
at Huxley.UI.Controllers!0x060021ce!MYOB.Huxley.UI.Controllers.Payroll.EmailPaySlipsController.SendEmailsOneByOne() +0x17
at Huxley.UI.Controllers!0x06003025!MYOB.Huxley.UI.Controllers.Payroll.EmailPaySlipsController.<>c__DisplayClass33_0.<SendEmails>b__1() +0x0
at Huxley.UI.Controllers!0x060021d1!MYOB.Huxley.UI.Controllers.Payroll.EmailPaySlipsController.PerformActionWithWaitAnimationSpinner(Action action, Boolean disableForm) +0x15
at Huxley.UI.Controllers!0x060021cc!MYOB.Huxley.UI.Controllers.Payroll.EmailPaySlipsController.SendEmails() +0x59
at Huxley.UI.Forms!0x0600268d!MYOB.Huxley.UI.Forms.Payroll.EmailPaySlips.<OnOkClicked>b__16_1() +0x0
at Huxley.UI.Forms!0x060031b5!MYOB.Huxley.UI.Forms.BaseForms.BaseViewContainer.PerformAction(Action methodToPerform) +0x16
at Huxley.UI.Forms!0x0600267c!MYOB.Huxley.UI.Forms.Payroll.EmailPaySlips.OnOkClicked(ButtonClickedArgs args) +0x89
at Huxley.UI.Forms!0x0600270a!MYOB.Huxley.UI.Forms.Payroll.ReviewPaySlipsBeforeDelivery.OnOkClicked(ButtonClickedArgs args) +0x6f
at Huxley.UI.Forms!0x06002e9e!MYOB.Huxley.UI.Forms.BaseForms.BaseViewForm.CallButtonClicked(Action`1 execute, ButtonClickedArgs args, String buttonText) +0x12
at Huxley.UI.Forms!0x06002e19!MYOB.Huxley.UI.Forms.BaseForms.BaseViewForm.btnOk_Click(Object sender, EventArgs e) +0x30
at System.Windows.Forms!0x06000d74!System.Windows.Forms.Control.OnClick(EventArgs e) +0x19
at DevExpress.XtraEditors.v17.1!0x06000d4f!DevExpress.XtraEditors.BaseButton.OnClick(EventArgs e) +0x2e
at DevExpress.XtraEditors.v17.1!0x06000d48!DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e) +0x1d
at System.Windows.Forms!0x06000e58!System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) +0x184
at System.Windows.Forms!0x06000e68!System.Windows.Forms.Control.WndProc(Message& m) +0x66f
at DevExpress.Utils.v17.1!0x06002708!DevExpress.Utils.Controls.ControlBase.WndProc(Message& m) +0x2e
at DevExpress.XtraEditors.v17.1!0x06000256!DevExpress.XtraEditors.BaseControl.WndProc(Message& msg) +0x0
at System.Windows.Forms!0x06005503!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) +0x0
at System.Windows.Forms!0x06005506!System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) +0x8e
at System.Windows.Forms!0x06002cd8!System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) +0x25
==========
MODULE: DevExpress.Utils.v17.1 => DevExpress.Utils.v17.1, Version=17.1.7.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a; G:b8c34c059b804930811d5f6d50999b6c; A:1
MODULE: DevExpress.XtraEditors.v17.1 => DevExpress.XtraEditors.v17.1, Version=17.1.7.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a; G:6df94e55f5bd4444b910d4b2a37076a4; A:1
MODULE: Huxley.MsOffice.Integration => Huxley.MsOffice.Integration, Version=2019.2.22.2609, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:212b94041b1a4cddae382b8457a785b5; A:1
MODULE: Huxley.UI.Controllers => Huxley.UI.Controllers, Version=2019.2.22.2609, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:57bb5c09645147beb154a96202bdf542; A:1
MODULE: Huxley.UI.Forms => Huxley.UI.Forms, Version=2019.2.22.2609, Culture=neutral, PublicKeyToken=947f70fecdd4159f; G:bd59ce3997e64164ac8e1bdba5b900e6; A:1
MODULE: Microsoft.Office.Interop.Outlook => Microsoft.Office.Interop.Outlook, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c;
MODULE: mscorlib => mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:770de44134264924b92f0c55201b01bb; A:2
MODULE: System.Windows.Forms => System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089; G:199b31db99b1448abbbf936be78a06de; A:1

----------------------------------------

[Gayathri · Accepted solution]

Hi @Tamarahhh,

Thank you for the post!

Thank you for providing the detailed error message.Going by your error details this is definitely caused by the colloquially known "interop" errors. This is due to leftover Registry Keys causing errors when applications try and use Outlook via this method.

I am linking you to one of our forum posts answered by one of our moderators on this topic. To view our response to their post and this includes a link on System.InvalidCastException error message when sending remittance advices or pay slips that you can view with an IT Professional to investigate.

Thank you.

[Naomi_Roskell]

Hi @Tamarahhh 

I'm experiencing this problem too. You'd think that MYOB would help us to fix the problem instead of brushing us to our IT guy, too bad if you don't have an IT guy...

Naomi - the disgruntled MYOB Partner who is trying to move all her Clients away from MYOB because the product is so painful to use...

[Steven_M]

Hi @Naomi_Roskell 

As the error message relates to the setup of Outlook i.e. the Interop components of Outlook - which is typically installed with Outlook, this is not something that we offer technical assistance on and recommend that clients do seek IT assistance with respect to that.

The external link does have information on that issue and could be attempted by the standard user after research into the Registry Editor, however, EXTREME CAUTION should be taken if you are going to attempt that yourself as updating the Windows Registry can have dire consequences. 

If you are confident an uninstall of AccountRight, reinstall of Outlook and reinstall of AccountRight has worked for some clients and thus may be something worth trying before consulting an IT professional and changing the registry is required.

[Naomi_Roskell]

Hi @Steven_M 

1. So if it's an issue within Outlook, how do you explain this issue being limited to only one datafile? As a Bookkeeper, obviously I use quite a few datafiles, but this issue only occurs in one of them...

2. Why does MYOB need to use Outlook when other Accounting Softwares do not? Surely, it would be beneficial for MYOB to operate as a standalone software (derr...)

Naomi

[Steven_M]

Hi @Naomi_Roskell 

Typically, this particular situation occurs environmentally and not related to one particular file. If you are encountering the error with only one particular file, I would recommend testing to see if the same situation occurs on multiple computers with different environments. If the same thing is still occurring across multiple environments, using a different customised form like the default form would be my further recommendation for testing.

When the company file is stored locally, AccountRight will rely on a desktop-based email program to send those emails such as Outlook. Other emails may work but these are not tested or supported. A while ago, we introduced the option to remove the dependency on those desktop-based email products for online files with being able to send emails directly from AccountRight (without an email product being installed). This is an option available to all clients that are using the company file in the cloud through the Setup>>Preferences>>Emailing functionality. If you are using the file locally then desktop-based email products, such as Outlook, must be installed.