• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 21760
  • Last Modified:

Quickbooks EVentID 4 - An unexpected error has occured in "QuickBooks": Returning NULL QBWinInstance Handle

Lots of these under Event Viewer/ Application:

quickbooks
category : error
eventid: 4


An unexpected error has occured in "QuickBooks":
Returning NULL QBWinInstance Handle

This happens every half hour or so

Windows Server 2003 Std. SP2, QB Enterprise 10 (recently upgraded from 7.0)
0
Anti-Mhz
Asked:
Anti-Mhz
  • 18
  • 16
  • 7
  • +2
1 Solution
 
JohnBusiness Consultant (Owner)Commented:
This is a very common error (true in QB Premier as well) particularly on a Windows 7 64-bit machine. It appears to cause a problem with Symantec Endpoint Protection V11 MR5. MR4 was not such a problem on Vista, but only MR5 will run on Windows 7.

I have opened cases with both Intuit and Symantec. Symantec says it is an Intuit problem (I agree) and Intuit is living in complete denial.

There is no fix for this at this point. I suggest you open a case with Intuit and add your voice that the error needs to be fixed. .... Thinkpads_User
0
 
jhalapradeepCommented:
Hi,

Please check this Symantec forum for the latest updates on this issue:

http://www.symantec.com/connect/forums/sep11-ru5-and-quickbooks-problems

-You can try upgrading to the latest version: 11.0.6005 RU6a . This one contains additional fixes after RU6 version.

Regards,
Pradeep Jhala
Symantec Technical Specialist (Endpoint Protection)
0
 
Anti-MhzAuthor Commented:
thanks. il be trying ru6a tonite
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
JohnBusiness Consultant (Owner)Commented:
RU6a does not do anything for the QB error. That belongs to Intuit. Otherwise it doesn't hinder QB either.
... Thinkpads_User
0
 
Anti-MhzAuthor Commented:
@thinkpads_user: any idea if this has been fixed in the latest version/update to quickbooks? Im considering upgrading solely because of this issue.
0
 
JohnBusiness Consultant (Owner)Commented:
@Anti-Mhz - No, the newest version of QB does not stop this error. So far as I can see, Intuit is in denial over both fixing it, and the need to fixt it. .. Thinkpads_User
0
 
kennyhenaoCommented:
What you will need to do is to uninstall all versions of .netframework from your server.
Then reinstall it from the Quickbooks CD first.
Then, repatch .net through windows update
0
 
JohnBusiness Consultant (Owner)Commented:
My guess is that, upon the next (annual) version of QuickBooks, that the error will re-occur. Uninstalling .netframework and then doing it all over probably only works once. ... Thinkpads_User
0
 
Anti-MhzAuthor Commented:
thanks to all. im have the chance to try it tonite. wishme luck
0
 
Anti-MhzAuthor Commented:
heres a question. is there a like an add-on application to quickbooks that requires .NET (web connector maybe) or is it a necessity if i want to run quickbooks at all
0
 
Anti-MhzAuthor Commented:
and another one. if i was to reinstall .net framework from quickbooks cd and "patch it" via windows update. Wouldnt I be presented with an option to install .Net Framework 1.1, 2.0,  3.0, etc
Out of those , what do I need?
0
 
JohnBusiness Consultant (Owner)Commented:
If QuickBooks wants .NET Framework, it will install it as it goes. Then Wiindows will want to update the rest. I have always had .NET Framework installed, so I am not certain how things will go. ... Thinkpads_User
0
 
Anti-MhzAuthor Commented:
i should mentionthats im also getting the following error:


Microsoft .NET framework - Unhandled exception has occured in your application:


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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at QBWebConnector.RegistryManager.anyAppScheduled()
   at QBWebConnector.ScheduleManager.Scheduler_Tick(Object sender, EventArgs e)
   at QBWebConnector.EventManager.OnClockTicked(Object sender)
   at QBWebConnector.QBWebConnector.Clock_Ticked(Object sender, EventArgs args)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3607 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
QBWebConnector
    Assembly Version: 2.0.0.139
    Win32 Version: 2.0.0.139
    CodeBase: file:///C:/Program%20Files/Common%20Files/Intuit/QuickBooks/QBWebConnector/QBWebConnector.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
QBWCUtil
    Assembly Version: 2.0.0.139
    Win32 Version: 2.0.0.139
    CodeBase: file:///C:/Program%20Files/Common%20Files/Intuit/QuickBooks/QBWebConnector/QBWCUtil.DLL
----------------------------------------
QBWCCommon
    Assembly Version: 2.0.0.139
    Win32 Version: 2.0.0.139
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/QBWCCommon/2.0.0.139__82cc56431f1a971d/QBWCCommon.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
QBWCInterfaces
    Assembly Version: 2.0.0.139
    Win32 Version: 2.0.0.139
    CodeBase: file:///C:/WINDOWS/assembly/GAC/QBWCInterfaces/2.0.0.139__82cc56431f1a971d/QBWCInterfaces.dll
----------------------------------------
Interop.QBXMLRP2
    Assembly Version: 8.0.0.249
    Win32 Version: 8.0.0.249
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Interop.QBXMLRP2/8.0.0.249__31d8aec643e18259/Interop.QBXMLRP2.dll
----------------------------------------
Syncfusion.Grid.Windows
    Assembly Version: 6.402.0.15
    Win32 Version: 6.402.0.15
    CodeBase: file:///C:/Program%20Files/Common%20Files/Intuit/QuickBooks/QBWebConnector/Syncfusion.Grid.Windows.DLL
----------------------------------------
Syncfusion.Shared.Base
    Assembly Version: 6.402.0.15
    Win32 Version: 6.402.0.15
    CodeBase: file:///C:/Program%20Files/Common%20Files/Intuit/QuickBooks/QBWebConnector/Syncfusion.Shared.Base.DLL
----------------------------------------
Syncfusion.Core
    Assembly Version: 6.402.0.15
    Win32 Version: 6.402.0.15
    CodeBase: file:///C:/Program%20Files/Common%20Files/Intuit/QuickBooks/QBWebConnector/Syncfusion.Core.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


This probably has the roots same as EventID 4?
0
 
JohnBusiness Consultant (Owner)Commented:
I don't see any .NET Framework errors on my machine. Where do you see these errors, as perhaps I am not looking in the correct place. I am using Event Viewer. .... Thinkpads_User
0
 
Anti-MhzAuthor Commented:
First I used the Add\Remove Programs and removed all the .NET applications installed. Second I used the .NET removal tool that can be found at one of msdn's blogs and remove any possible leftover files. Having done that I installed dotnetfx20.exe

The error would still appear about every 2nd time I launch quickbooks. Once that was established I proceeded to Windows Update where I installed .NET Framework 3.0 service pack 2 and .NET Framework 3.5 service pack 1

Having done that I receive the following error about every second time when accessing Quickbooks:

szAppName : QBW32.EXE     szAppVer : 20.0.4006.807     szModName : msvcr90.dll
szModVer : 9.0.30729.1     offset : 00030701  

See quickbooks-error-1.JPG image for more details

The following errors are logged in Event Viewer, Application at the same time:

Category: Error, Source: Quickbooks, Event: 4. When double clicked Description says:

 "An unexpected error has occured in "QuickBooks":
Returning NULL QBWinInstance Handle"

See screenshot quickbooks-error-2.JPG for more details:

Having clicked Don't Send on the Error Report, I'm able to open Quickbooks with no problems

I'm able to open it again a few times without the crash...yet maybe on 3rd-4th quickbook launch, error would present itself again.




quickbooks-error-1.JPG
quickbooks-error-2.JPG
0
 
JohnBusiness Consultant (Owner)Commented:
@Anti-Mhz - Thank for the update.

I am not getting the first error and I do not get (and have not gotten) the Microsoft "Send Error Report" errors.

I get thousands of the "Returning NULL QBWinInstance Handle" errors. I cannot get Intuit to listen.

The critical error I get is an APPCRASH in qbw32.exe in StackHash_5595. When this happens, QuickBooks has Stopped Working, it closes, and then I see the above in the Reliability Monitor. I have several dozens of these.

What the above error relates to is Symantec Endpoint Protection V11 MR5. This crash did not occur with MR4. However, only MR5 works in Windows 7 Pro 64-bit.

If I disable SEP first, I can open QuickBooks with no issue. I can re-enable SEP immediately after while QB is running with no problem. So it is a problem on opening a file and that is all. It is a 64-bit problem, and I keep after Intuit but they refuse to acknoweldge that their product is any less than 100.0% perfect. Clods.

... Thinkpads_User
 
0
 
Anti-MhzAuthor Commented:
that  sounds a lot  like Intuit.
that being said, the server where I have Quickbooks installed is running Windows Server 2003 32-bit(im ot even sure if 64 bit exists for 2003 server).

I'm currently browsing through Symantec Forums for SEP for cross reference regarding this issue.
If this an issue Symantec is having with Intuit products, maybe theres a way to make a list of exceptions for Intuit Software. For example including the Inventory file that is being opened. I will be trying adding c:\Program Files\Intuit to SEP console as Security Risk Folder, Action: Ignore and the directory where my company file resides.
0
 
Anti-MhzAuthor Commented:
I spent a good hour on the phone with Intuit yesterday regarding this issue. The only advice they were able to give me about it is that some people were able to lose this error via reinstallation of quickbooks. however it's far from being a sure shot.


I've have downloaded the latest Symantec Endpoint Manager and have installed it today. As soon as I get symantec endpoint protection to propagate, I will post whether upgrade does any good.
0
 
Anti-MhzAuthor Commented:
I'm still getting the same problem with Quickbooks 10.0 R7 and Symantec Endpoint Protection 11.0.6 (latest)
Did I mention I include all possible and impossible Quickbook directories to Global Exceptions
0
 
JohnBusiness Consultant (Owner)Commented:
I have done the same thing with Exceptions, except that on 64-bit machines, centralized (global) exceptions do not work in 11.0.6 (bug acknowledged by Symantec) so I am still at 11.0.5
.. Thinkpads_User
0
 
Anti-MhzAuthor Commented:
according to some blog eventid 4 and quickbooks....is quickbooks searching for any add-ons and not finding any. Should be a warning at most...

but then again. I'm getting startup errors about every other time when Quickbooks launches. I dunno if its related to anything what has been discussed in this thread so far....
Do you get those nasty system crashes at startup with a Don't Send Report/ Send Report option?
0
 
Anti-MhzAuthor Commented:
last question was addressed to thinkpads_user
0
 
JohnBusiness Consultant (Owner)Commented:
>>> Do you get those nasty system crashes at startup with a Don't Send Report/ Send Report option?

Yes. Here again, Intuit is not adhering to Microsoft Programming practices. When Lenovo started putting out Windows 7 drivers, some would stop working and require reinstallation. Later, a new driver would come out with "WER xxxx" addressed. That means Lenovo is putting the crashes to Microsoft and then using the followup to fix. Intuit is not doing this and nothing is getting fixed.

Worst of all, I don't think Intuit has heard of Experts-Exchange and don't understand how widespread their problems are.
.. Thinkpads_User
0
 
Anti-MhzAuthor Commented:
wow, u hit the nail on the head. Intuit's scope seems to be , well limited to Intuit. Another things that gets me that no such problem existed with Quickbooks 6.0 or 7.0 for that matter. They really pulling a Microsoft on this one with releasing half assed software and patching it up later. I regret ever switching for earlier versions. Illusion of moving forward with versions set us back a few months wasted on patching, updating, repariing and disabling. Actually as I'm typing this a fellow employee came to saying her Quickbooks won't email the last invoice of the day. Should I be surprised she mentioned it was much better when we had previous versions of Quickbooks installed.  ERRRRRRGHH
0
 
Anti-MhzAuthor Commented:
ok so we still getting crashes about every other time on launch. we have upgraded to latest R as well.  we even got the new quickbooks in the mail but im skeptical about it.  u know why
0
 
JohnBusiness Consultant (Owner)Commented:
This was a July 2010 thread. I got a new Lenovo Windows 7 Pro desktop at about that time, and built it very cleanly. QuickBooks 2010 does not crash on this machine at all. I still get event log errors, but it is reliable. I am in the (slow) process of rebuilding my Thinkpad by getting a new hard drive. I have QB 2011 as well, so I will probably speed up the Thinkpad rebuild and get it going with just QB 2011. I shall see how this works.
... Thinkpads_User
0
 
Anti-MhzAuthor Commented:
are u running latest R of qb 10, did u do any windows update? any .net framework updates? did u have any errors that were needing fix  or was it a clean install ? u say u still get error logs, is it event id 4 ?
0
 
JohnBusiness Consultant (Owner)Commented:
I am running the latest QB10 updates (latest R version), and all Windows 7 updates, including .NET Framework including V4 (newest .NET Framework). The QuickBooks errors are all Event ID 4.

So on the new machine, lots of Event ID 4 errors , but no QuickBooks overt errors (QuickBooks has stopped working) and zero Windows crashes.  On the Thinkpad (needs rebuiliding), lots ot Event ID 4 errors, and a few Quicks has stopped working. But even on the Thinkpad, no Windows crashes. ... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We have an up to date Windows Vista x86 machine that we just installed QB 2011 onto. It too is crashing on the MSVCR90.dll.

The kicker is that we installed for our client remotely and QB 2011 started up just fine for us. When we initiated a Remote Assistance session with the user (SBS 2008 backend) QB 2011 would fire up just fine.

It was when the user was logged into their desktop alone that QB 2011 refused to start.

We are no further ahead in our troubleshooting. This network does have SEP 11 installed and is up to date.

Philip
0
 
JohnBusiness Consultant (Owner)Commented:
I do find your situation strange.

>>> On the Thinkpad (needs rebuiliding   <--- The ThinkPad is now rebuilt and up and running. QB V2010 runs just fine (no stop errors and nothing but Event 4 errors which seem to be of no consequence).

So just now (reading your post) I installed QBV2011 and it too installed properly and runs properly. I have SEP 11.05 (MR5) running as well.

I do local installs and that may make a difference.

Can you try a local install?

... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Did that. Had the user uninstall (not clean though) then reinstall QB 2011. It worked fine while connected via RA or RDP but crashed on the same module if only the user was on the desktop.

We will be running a clean out as per Intuit's KB and having the user reinstall on their own to see if it works.

Almost everything is documented here:
http://blog.mpecsinc.ca/2010/12/us-quickbooks-2011-r1-third-party.html

Philip
0
 
JohnBusiness Consultant (Owner)Commented:
From that article:  >>> Note that this user is operating as a Standard User

QB will not run as a standard user (at least up to XP it will not). I have QB2010 working on a client Windows 7 machine just fine. What I did was make them a member of the legacy power users group.

QB does need adequate permissions for it to run.  ... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
That use to be the case. Newer versions of QuickBooks operate fine when the user is running on a Windows 2008+ domain as a Standard User.

We have many clients both in the US and Canada running QB as a Standard User with no issues.

We have already elevated this particular user to Local Admin and that did not work anyway.

Philip
0
 
JohnBusiness Consultant (Owner)Commented:
There must be something wrong with the user machine. I cannot put my finger on what, because I have QB running in variety of circumstances for clients without issue (and you say the same). So there must be something wrong with the Vista machine.  .... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
QB has always had its share of challenges running at single seat clients all the way up to larger accounting firms that we support.

We have a few more things to do before we have exhausted everything plus perhaps a contact at Intuit that may help us out yet too.

Philip
0
 
JohnBusiness Consultant (Owner)Commented:
I understand QB has its challenges. Check out the machine carefully.

Also try a different user id on the Vista machine (because profile errors and corruption affects QB).

And by all means call Intuit. I use Intuit support and generally get decent results from them. ... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The catch with trying another ID is that it would be done remotely thus for whatever reason QB works.

We could try another use ID that has not logged in before just to clear up whether the user's local profile may be the culprit.

No word back from Intuit support yet.

Philip
0
 
Anti-MhzAuthor Commented:
having just upgraded to latest quickbooks (11 me thinks) and latest R il post results soon. At least we no longer have the .NET framework crash on startup, but then i cant even vouch for that, been a lot of changes lately in our company infrastructure, I might be not catching it, yet my coworkers are.

will post soon..
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The fix for us ended up being the video card drivers.

QB 2010 and QB 2011 now require some video acceleration for the way QB renders things according to support.

Our problem was on a two year old Dell with an ATI Radeon HD 2400 that had not had the drivers updated. Once we updated the video drivers on all of the Dell computers the problem went away.

MSVCR90.DLL error:
http://blog.mpecsinc.ca/2010/12/us-quickbooks-2011-r1-third-party.html
MSVCR90.DLL error resolved:
http://blog.mpecsinc.ca/2011/01/quickbooks-2010-and-2011-msvcr90dll.html

We were told by support to ignore the Event ID 4 errors.

We have Enterprise deployments on Terminal Services and Remote Desktop Services where QB is being served by TS/RDS RemoteApps and those errors flood the event logs. As long as QB does not outright crash we are ignoring it. Hopefully the errors don't mean data corruption. BTDT.

Philip
0
 
Anti-MhzAuthor Commented:
how is video acceleration working for you? is there a notice in perfomance?, i also have a 2-3 year old dell , a dell that never got video card drivers treatment (im using whatever windows drivers were available out of the box)
0
 
JohnBusiness Consultant (Owner)Commented:
I don't see any video acceleration involved in my QuickBooks installation.

Yes, you can ignore the event 4 errors. I have no idea why Intuit won't fix this because it has been reported to them thousands upon thousands of times. Someone there is clueless, for certain. ... Thinkpads_User
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The troubleshooting we went through was facilitated by the Pro Advisor's support folks (not off-shore). We were working with front line folks.

Once we figured out where the problem was, we were told by the QB support folks that since QB 2010 certain aspects of QB's code tied into the video subsystem for rendering.

The catch in that case was a bad driver set from ATI.

If your video subsystem is on board/chipset based then make sure the BIOS is up to date and that the video drivers for that model of Dell are also up to date.

Philip
0
 
Anti-MhzAuthor Commented:
i need to ask another question. best solution for now
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 18
  • 16
  • 7
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now