Any idea what might be causing thie following error that happens upon closing QB 2009? Started noticing it after the last p/r update and a MS .net update (I think! - don't see it in my add/remove programs list) These two updates were done on the same day. TIA for any help/suggestions!!
Our systems run WindowsXP SP3 with all Critcal Updates except IE8. We run QuickBooks Pro 2009 I was not seeing this issue until last night when I checked for updates to QuickBooks and went from R10P to R11P.
A QuickBooks Support Search found an article at:
formatting link
had the 0x568b29f9 instruction address in the keyword list, but the address in the article was different. The article does say that "This errror does not harm your QuickBooks company file or cause problems with any features or functions of QuickBooks. Your data inside QuickBooks is safe.", but I would feel better about trusting the informaton if the instruction address in the post had been the one we see. An Intuit Community search found an article at:
formatting link
pointed to an thread at:
formatting link
was a post by Rich LaDuca (edited Friday, June 25, 2010 12:35 PM) reporting himself to be a QuickBooks ProAdvisor Support Engineer which addressed the issue. The post was "Marked As Answer byJason H. - Support EngineerMicrosoft Support, ModeratorMonday, June 28, 2010 2:52 PM". It said that "We have a fix (temporary) for the "reference memory could not be read" issue." The LaDuca post indicated that "so far this is only been confirmed to work on XP". It suggested using Add/Remove Programs to remove the KB976576 update. If that did not get rid of the problem, it suggested also removing the KB977354 update.I did remove the KB976576 update, and the error message is gone on our machines. I also have hidden the .NET Framework update that installed that update until I find an indication that a permanent resolution has been found. I am not crazy about this type of work around, but at least my wife (It is her business and she is the actual QuickBooks user. I just help with tech stuff.) won't have to see that error message, and get nervous.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.