Exception from HRESULT: 0x80040302


I have Ayanova 3.6 with QBI. The database is an SQL server database. Ayanova works fine.I upgraded to Quickbooks 2010 and was able to load QBI fine and even linked some customers fine. This morning I attempted to load QBI and get this error when it gets to Reading from Quickbooks Invoice Templates:

Microsoft .NET Framework

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Exception from HRESULT: 0x80040302


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040302): Exception from HRESULT: 0x80040302
at Interop.QBFC5.IQBENTemplateTypeType.GetValue()
at AyaNovaQBI.Util.()
at AyaNovaQBI.Util.PopulateQBListCache()
at AyaNovaQBI.Util.PreFlightCheck()
at AyaNovaQBI.MainForm.0()
at AyaNovaQBI.MainForm.0()
at AyaNovaQBI.MainForm.0()
at AyaNovaQBI.MainForm.(Object , EventArgs )
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativewindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)
at System.Windows.Forms.Nativewindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
Assembly Version:
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: [file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll](file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll)

Assembly Version:
Win32 Version:
CodeBase: [file:///C:/Program%20Files/Ground%20Zero%20Tech-Works%20Inc/AyaNova%203/AyaNovaQBI.exe](file:///C:/Program%20Files/Ground%20Zero%20Tech-Works%20Inc/AyaNova%203/AyaNovaQBI.exe)

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: [file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/](file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: [file:///C:/WINDOWS/assembly/GAC_MSIL/System/](file:///C:/WINDOWS/assembly/GAC_MSIL/System/




From what you are saying, QBI 3.6 loaded successfully with no issues with your QuickBooks 2010 previously. Whereas today, when loading QBI (which is when the QBFCC Intuit component reads data from the QuickBooks database), you get this error at the point it is checking invoice templates.

We have not seen such an issue before to provide a specific solution. It would require that you troubleshoot your QuickBooks to resolve. I would suggest checking your QuickBooks invoice templates, especially the one that you have selected as a default invoice template in QBI Preferences.
It may require that you create an invoice using each of the different invoice templates to see if any error occurs in QuickBooks itself that may help identify the specific invoice template if that is what the issue is actually related to.

It may also be an issue with the older version of Intuit’s QBFC5 that is used with the older QBI 3.6
A way to confirm this is, to set up a test station with QuickBooks 2010, a copy of your QuickBooks database file, and temporarily licensed AyaNova 5.1 with QBI 5.1 (which uses QBFC7) and load QBI 5.1 and see if the error occurs. If the error also occurs with QBI 5.1 that uses QBFC7, that would point to it possibly being a specific corrupted or damaged.

I would also suggest running a verify / rebuild on your QuickBooks company data file (make sure to back up your QB data file before doing, etc)

  • Joyce