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

.Net Runtime 2.0 error in Application Event Log, possibly related to Quickbooks performance issues

I've got a customer who has come to me with problems in Quickbooks (slow performance, problems with multi-user access).  I have found the following error in the Event Log:

"Source:  .NET Runtime 2.0 Error
Event ID:  5000

EventType clr20r3, P1 qbwebconnector.exe, P2 2.0.0.111, P3 4720f278, P4 mscorlib, P5 2.0.0.0, P6 471ebc5b, P7 3404, P8 15a, P9 system.unauthorizedaccess, P10 NIL"

A Google search including all these parameters turned up zilch.  I did find some results on this type of .NET Runtime Error, but most were geared toward programmers and code troubleshooting.  (I'm not about to try to troubleshoot Intuit's code directly; I wouldn't attempt that even if I were a code-monkey type, no offense intended to you code-monkeys out there. ;) )

The worst part is that I don't even know for certain that this is related to the original problem I'm working on (the QB performance/multi-user issues)!

Just for clarity:  in this question, I am only asking for information about the above quoted error message; if this leads to a solution to the QB performance/multi-user issue then that's wonderful, but it's a bonus only.  Mainly I just want to know what this Event means, and what (if anything) can be done to fix it.
I am hoping that the solution will be along the lines of "apply such-and-such update" or "re-register the following .dll files"; as mentioned before I am allergic to source code.  ;)

Thanks in advance!
:)

P. S.  I am putting this in the QB zone; the PTB's are welcome to move it or add zones if they feel it will fit better elsewhere.  :)
0
TekServer
Asked:
TekServer
3 Solutions
 
top_rungCommented:
So not much information on the error can be found.  Definitely seems like a code debug issue.  What version of QB - is it updated and current?  That would be the first step IMO.   What is the OS, patching level, etc.?

Are the QB data files shared across the network?  Are there any other noticeable networking issues?




0
 
TekServerAuthor Commented:
QuickBooks Enterprise Solutions - Professional Services Edition 8.0

When opening the program, it does say that there is a downloaded update it wants to install.  I will check with the client tomorrow about installing the update, so I can make sure all instances of QB are updated together.

The machine that's hosting the data is running Windows Server 2003 R2 on fairly new hardware (less than a year old).  It was short by three Windows updates, two SQL updates, and one Office update, all of which I am installing now.  The updates seem to be proceeding smoothly, and I should be able to do a reboot tonight if needed.

A further bit of info (probably irrelevant):  there are two servers in this network; the "primary" DC is an older SBS 2003 server.  AFAIK, it has nothing whatsoever to do with QuickBooks (other than domain authentication to reach the share on which the data resides, of course).

Okay, the updates and the reboot are finished; the OS is up to date.  I'll touch base tomorrow after I (hopefully) get QB updated.

Thanks!
:)

p.s. Seems like it would have been a lot simpler to craft an error message that said: "You need to update QuickBooks".  ;)
0
 
top_rungCommented:
Just to clarify, I don't think that the error is saying in "update" in cryptic words, it is just that I can almost guarantee that when you don't find answers googling or by asking here, your next bet would be to contact QB support.  There first response will be "update".  At least you will be there already ;)

Good Luck!

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
grandebobCommented:
I would make sure your client has all the appropriate .net 2.0 framework patches.

Your performance issues might be due to regular maintenance not being performed on the file. QB uses a database that easily gets bloated and fragmented.
0
 
TekServerAuthor Commented:
top_rung:  Understood, and a good point.  I was being facetious.  ;)

The QB updates should be applied today; we'll see what happens from there.

grandebob:  I'm pretty sure the .Net framework patches are up to date; they usually are included with the MS Updates, at least in the "Optional" section, and I always go through the Optional updates and pick & choose the ones I feel are needed/useful (like .Net updates, and Root Certificate Updates, and such).

You have a very good point on the database maintenance, which I will pass along.  My boss is an old Unix guy, and one of his favorite "war stories" is about a support tech for one of the old database programs he used to support that would always answer the same way when you called:  "reindex the database".  At that time (almost 20 years ago), reindexing the database could take hours or even days, which would usually guarantee that when he called back, he'd get a different tech support person (which he figured was probably the point).  Still, it is always a good place to start with a database.

:)
0
 
hesCommented:
The P9 system.unauthorizedaccess points to the app is trying to write to a folder that requires Admin privlidges
0
 
TekServerAuthor Commented:
hes:  That's a very interesting point.

I checked the NTFS permissions on the folder where the QB data is stored, and on the Intuit folder under the Program files.  On the former, Everyone has Full Control (Everyone also has Full Control in the Share permissions).  On the program folder, Everyone has Read Only access.

I checked specifically for the user account that is used by the QB DB service (QBDataServiceUser18, a local account on this member server rather than a domain account); that user account had special permissions (Read, Write, and Execute, but no Delete, Change Permissions, or Take Ownership) on the data folder and Read Only access to the program folder.  I went ahead and granted that account Full Control to both locations, just to be on the safe side.

I believe the QB updates were done this afternoon; I'll check tomorrow morning and see what the status is.

Looking in the event logs just now, I see evidence that the updates were done this evening, and that the database maintenance was done as well.  I do not see any instances of the .Net error after about 6:30 PM (CST).  The errors were not very frequent (1-3 per day, roughly), so I figure on giving this a day or three to see what develops.

Thanks!
:)
0
 
ajames9000Commented:


I am not sure if it was the sever or the client PC that had the error from your post; however, if it was on the PC then here is an old thread that referred to the  C:\Document and settings\<user>.  folder not allowing access when the individual was not logged on as an administrator.

http://www.eggheadcafe.com/forumarchives/NETFramework/Feb2006/post25801454.asp
0
 
TekServerAuthor Commented:
Just over 24 hours now without an error in the logs, and customer reported QB running like a scalded dog today, after DB maintenance last night.
Thanks!
:)
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now