Quickbooks NetShareGetInfo Error
I have been seeing this error in the event logs for years in Quickbooks 2003, 2004, 2005, 2006, 2007, 2008 and 2009. I see it in the Pro, Premium and Enterprise versions. This happens to all the computers in the networks I see. No Viruses or other Spywares (100% sure). Fully updated with all Service Packs and Quickbooks updates. When I call Intuit about it they say to ignore it. I have tested all kinds of "Theories in Google": replaced and updated .net, MS Visual C++ Redistributable, etc.... has anyone been able to solve it?
Event Type: Error
Event Source: QuickBooks
Event Category: Error
Event ID: 4
Date: 11/4/2009
Time: 8:31:28 AM
User: N/A
Computer: Server
Description:
An unexpected error has occurred in "QuickBooks":
Got unexpected error 5 in call to NetShareGetInfo for path \\server\Quickbooks\MyQuic
It doesn't give any problems but it fills up the event logs with the annoying "Red" error ...... it seems everyone is complaining about this in the QB forums.... I've searched everywhere for years for a solution to this and nothing...
Event Type: Error
Event Source: QuickBooks
Event Category: Error
Event ID: 4
Date: 11/4/2009
Time: 8:31:28 AM
User: N/A
Computer: Server
Description:
An unexpected error has occurred in "QuickBooks":
Got unexpected error 5 in call to NetShareGetInfo for path \\server\Quickbooks\MyQuic
It doesn't give any problems but it fills up the event logs with the annoying "Red" error ...... it seems everyone is complaining about this in the QB forums.... I've searched everywhere for years for a solution to this and nothing...
jaynir
check this kb http://support.quickbooks.intuit.com/support/pages/knowledgebasearticle/128165
ASKER
jaynir, thank you for your response....apparently you did not completely read the question .
BitsBytes my apology.
I never had and error logs on QB. One time, unexpected error occurred message popped up while running QB. That happened basically when the data was corrupted, we had to buy one 3rd party tool that repaired the data and the problem resolved.
Maybe you can call QB support and tell them about the errors.
I never had and error logs on QB. One time, unexpected error occurred message popped up while running QB. That happened basically when the data was corrupted, we had to buy one 3rd party tool that repaired the data and the problem resolved.
Maybe you can call QB support and tell them about the errors.
ASKER
Jaynir..... you seem confused today....lol.... read the question:
"...When I call Intuit about it they say to ignore it...."
This problem has been going on for years. I see it all the time when I walk into customers offices to fix other unrelated problems and since I'm a perfectionist (a bad thing to be in the computerworld), I have tried to figure it out unsuccessfully..... As I said.... just look it up in Google..... people are very irritated about this with Intuit and the problem has been lingering for years (since 2003) in most if not all Quickbooks versions.
It does not create any problems..... Quickbooks works fine..... it just creates a RED EVENT in the event viewer.....
"...When I call Intuit about it they say to ignore it...."
This problem has been going on for years. I see it all the time when I walk into customers offices to fix other unrelated problems and since I'm a perfectionist (a bad thing to be in the computerworld), I have tried to figure it out unsuccessfully..... As I said.... just look it up in Google..... people are very irritated about this with Intuit and the problem has been lingering for years (since 2003) in most if not all Quickbooks versions.
It does not create any problems..... Quickbooks works fine..... it just creates a RED EVENT in the event viewer.....
hmm... Intuit said not to worry and ignore that RED marked logs? you should probably call them one more time. One time I called HP and told them that i wanted to upgrade memory on my laptop and he was like you can't add more than 1gb in your laptop, if you do your laptop malfunctions.
Try calling them one more time and ask them why the logs are marked as "RED".
Try calling them one more time and ask them why the logs are marked as "RED".
hi
i had the same problem with a customer. the cause was ms net framework.
solution was:
1) uninstalled all net framwork versions (with microsoft uninstaller cleanup utility)
2) then re-install ThirdPartyDotNET20dotnetfx
3) install the lastest NET framework version (this includes all versions)
http://support.quickbooks.intuit.com/support/pages/knowledgebasearticle/1009275
i had the same problem with a customer. the cause was ms net framework.
solution was:
1) uninstalled all net framwork versions (with microsoft uninstaller cleanup utility)
2) then re-install ThirdPartyDotNET20dotnetfx
3) install the lastest NET framework version (this includes all versions)
http://support.quickbooks.intuit.com/support/pages/knowledgebasearticle/1009275
ASKER
Thank you hopeleonie,
I did try this before. Actually, just yesterday I just recommended the same solution to another asker in this thread:
http://www.experts-exchang
I have solved many Quickbooks issues with the .net in the same way you are advising.... but it hasn't worked on this one.....
Jaynir:
Just do a Google search for this phrase: "Quickbooks unexpected error 5 in call to NetShareGetInfo for path \\".
These are just a few links where you can see where the users are getting the "just ignore it answer from Intuit". On each link just CTRL-F the word: NetShareGetInfo
http://community.intuit.co
http://community.intuit.co
http://www.eventid.net/display.asp?eventid=4&eventno=9613&source=Quickbooks&phase=1
http://forums.quickbooksus
http://www.experts-exchang
http://paste-it.net/public
http://qaix.com/software-c
I did try this before. Actually, just yesterday I just recommended the same solution to another asker in this thread:
http://www.experts-exchang
I have solved many Quickbooks issues with the .net in the same way you are advising.... but it hasn't worked on this one.....
Jaynir:
Just do a Google search for this phrase: "Quickbooks unexpected error 5 in call to NetShareGetInfo for path \\".
These are just a few links where you can see where the users are getting the "just ignore it answer from Intuit". On each link just CTRL-F the word: NetShareGetInfo
http://community.intuit.co
http://community.intuit.co
http://www.eventid.net/display.asp?eventid=4&eventno=9613&source=Quickbooks&phase=1
http://forums.quickbooksus
http://www.experts-exchang
http://paste-it.net/public
http://qaix.com/software-c
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I figured that the problem is there, what is really annoying is that people have been complaining to Intuit about this for years..... since 2003 that I remember of.... and they still have not addressed it..... first they started blaming the Microsoft .net, then they said it was the .net sp2, later they said it was a problem with systems that did not have the Microsoft Visual C++ Redistributable installed ......always trying to shift the blame to Microsoft....
One day I got really p...d off and I told them: " you are making a product supposedly designed to work with Microsoft...., if it is not working, it's because of your poor design....don't go blame Microsoft because you don't know how to deal with the existing API....."
One of my customers is technical enough to be dangerous and is very finicky and when she sees the red events..... you can imagine the rest of the story...
One day I got really p...d off and I told them: " you are making a product supposedly designed to work with Microsoft...., if it is not working, it's because of your poor design....don't go blame Microsoft because you don't know how to deal with the existing API....."
One of my customers is technical enough to be dangerous and is very finicky and when she sees the red events..... you can imagine the rest of the story...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you thinkpads_user for taking a look at this.
Yes.... this error you mention above is one of the "infamous group" of related errors that Quickbooks (Intuit) support says to ignore. It is documented in the first link I posted in CommentId: 25850737. I'm sure if we are able to find a solution to this one or any of the errors of this group from the links above, they will all probably have the same source/solution...
It not only happens in Vista, it is also present in XP Pro SP3 and Windows 7......
As I mentioned before, It is not creating any "real problem" for most users (at least not to the users in the networks I support or I would be pulling my hair out) although I have seen many other users complain about it hanging their machines....
Yes.... this error you mention above is one of the "infamous group" of related errors that Quickbooks (Intuit) support says to ignore. It is documented in the first link I posted in CommentId: 25850737. I'm sure if we are able to find a solution to this one or any of the errors of this group from the links above, they will all probably have the same source/solution...
It not only happens in Vista, it is also present in XP Pro SP3 and Windows 7......
As I mentioned before, It is not creating any "real problem" for most users (at least not to the users in the networks I support or I would be pulling my hair out) although I have seen many other users complain about it hanging their machines....
ASKER
Hello experts.... I'm still around.... I do want to solve this Quickbooks issue. I would appreciate some ideas..... :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I agree..... this thread is important in the sense that I can use it to prove that everyone is getting these red errors in the event manager.
Quickbooks does not want to openly admint or post on their website that this is normal.
At least if I get more replies from other experts we set the precedent that the error is there and nevertheless, Quickbooks is working normally......
I will wait for a few other experts to comment on this or at least to ratify that they get the same error events on their systems.
Quickbooks does not want to openly admint or post on their website that this is normal.
At least if I get more replies from other experts we set the precedent that the error is there and nevertheless, Quickbooks is working normally......
I will wait for a few other experts to comment on this or at least to ratify that they get the same error events on their systems.
ASKER
Well ..... we know it is just a false alarm and not a real problem so hopefully if anyone in the near future (although this has been going on since 2001) tries to find out why he is getting this RED Alert in the Events Log he will know he does not need to worry about it.
Thank you BitsBytesand& I am sure we will be crossing paths here again. ... Thinkpads_User
This is ridiculous. And now when trying to create a support ticket with Intuit we get the message "Your case ID cannot be found."
We have replaced the entire infrastructure due to slowness in QuickBooks, upgrading to a 1 gigabit network with a brand new server.
It's absolutely ridiculous how awful QuickBooks support is. An answer to this issue would be very appreciated.
We have replaced the entire infrastructure due to slowness in QuickBooks, upgrading to a 1 gigabit network with a brand new server.
It's absolutely ridiculous how awful QuickBooks support is. An answer to this issue would be very appreciated.
ASKER
Welcome to the Quickbooks world ....... lol.
I run QuickBooks Enterprise Edition 9.0 with all the latest patch on a Windows 2003 Terminal Server and am licensed for 20 users. I get quite a few of these red "got unexpected error 5 in call to NetShareGetInfoPath for..." everyday. I see Intuit's answer is "just ignore it." True, my users have yet to complain about it.
I think you'll find interested that if you use a DFS, e.g., map drive Q: to \\mycompany.local\root\qui
QB is not exactly compatible with Windows, obviously.
Regards,
John Babbitt
Systems Administrator
Ashland Support Group
I think you'll find interested that if you use a DFS, e.g., map drive Q: to \\mycompany.local\root\qui
QB is not exactly compatible with Windows, obviously.
Regards,
John Babbitt
Systems Administrator
Ashland Support Group
Since this thread started, I put a new drive in my Thinkpad and installed Windows 7 Pro 64-bit. I also installed Symantec Endpoint Protection 11 MR5 (known to conflict with QB). Now I get that WinInstance error as before and now I must disable SEP before starting a ledger or QB will crash.
I have opened a case with Intuit but they are not being helpful at this point. They said to make a new Windows Profile. I did that but it did not help. ... Thinkpads_User
I have opened a case with Intuit but they are not being helpful at this point. They said to make a new Windows Profile. I did that but it did not help. ... Thinkpads_User
ASKER
You have no idea how devastating SEP with Quickbooks Enterprise 9 can become. The whole network was crawling like molasses....
It got to a point (I was about to loose my customer who has been on a yearly service plan agreement for the last 5 years) where I told Symantec: "..Ok ... you guys offer as part of the sale of SEP to install it at an extra fee.... well .... go ahead... if it works, I will be glad to pay....". Needless to say they were never able to make it work right and they gave us a full refund....
Bits ...
(Thinkpads: thank you for assisting the other guy with the WiFi)....
It got to a point (I was about to loose my customer who has been on a yearly service plan agreement for the last 5 years) where I told Symantec: "..Ok ... you guys offer as part of the sale of SEP to install it at an extra fee.... well .... go ahead... if it works, I will be glad to pay....". Needless to say they were never able to make it work right and they gave us a full refund....
Bits ...
(Thinkpads: thank you for assisting the other guy with the WiFi)....
I'm glad I don't use SEP. I've always had problem with Symantec's Anti-Virus software (disabling UPS is one of them; too many odd quirks). For years, I've used McAfee Total Virus Defense. Now, I'm a believer of Sunbelt Software's VIPRE product. Low memory overhead, fast and continously updated. I replaced McAfee's with VIPRE on one user's laptop and she said her laptop is now 10x faster than prior. That sold me and now I have not experienced any issues with AV.
Now, if only Sunbelt Software can fix QB's problem. ;-)
Now, if only Sunbelt Software can fix QB's problem. ;-)
My customer is running QB2010 Pro, 5 user edition and until yesterday everything was fine. We've replaced two machines with HP Desktops/Windows 7 and begin to get the infamous:
Got unexpected error 5 in call to NetShareGetInfo for path \\Server1\2010qbcw\CW Pro.QBW
Have you guys experienced the problem with Windows 7? Any clues on how to solve it? The error is closing QB from screen and can't be ignored.... it hapens in groups from time to time with no aparent reason... by the way, another computer, same model e configuration, created from a ghost file is running fine... go figure!
Any help will be greatly appreciated
Thanks
Speed
Got unexpected error 5 in call to NetShareGetInfo for path \\Server1\2010qbcw\CW Pro.QBW
Have you guys experienced the problem with Windows 7? Any clues on how to solve it? The error is closing QB from screen and can't be ignored.... it hapens in groups from time to time with no aparent reason... by the way, another computer, same model e configuration, created from a ghost file is running fine... go figure!
Any help will be greatly appreciated
Thanks
Speed
ASKER
Hello speed2001,
Click right above the comment field and select "Ask a related question" ... this way, the question will be posted so more people can see it and help you find the answer/solution to it.
Bits...
Click right above the comment field and select "Ask a related question" ... this way, the question will be posted so more people can see it and help you find the answer/solution to it.
Bits...
Did anyone ever find a solution to this? I have a Windows 7 user using QB Pro and she has this error. It appears to be causing her QB to close every once in a while as well.
ASKER
adj1984 ... This is not really an error. Quickbooks reports some activity and since Windows doesn't know what Quickbooks is reporting it gets logged as an error. The only problem is that Quickbooks' activities do not report correctly but it will not make your computer crash.
Your friends computer may be crashing for some other issue. Ask a related question (just click on the link right above where you type the comments) and we may be able to address and hopefully fix the issue.
Bits ...
Your friends computer may be crashing for some other issue. Ask a related question (just click on the link right above where you type the comments) and we may be able to address and hopefully fix the issue.
Bits ...
I have this problem:
If any user opens a qbw file I get this error. An unexpected error has occurred in "QuickBooks Pro 2014":Got unexpected error 5 in call to NetShareGetInfo for path \\xxxxx\Quickbooks 2014\xxxxx.qbw.
I've done a lot of research on the internet to fix this problem and keep getting stuff like its suppose to happen or its a .NET problem. I however believe its a permissions problem.
I have solved this issue by making sure in **ACTIVE DIRCTORY COMPUTERS AND USERS** that the user in question, is a **member of** the administrator built in group and domain admin. After you make these changes you should no longer receive that error code.
If any user opens a qbw file I get this error. An unexpected error has occurred in "QuickBooks Pro 2014":Got unexpected error 5 in call to NetShareGetInfo for path \\xxxxx\Quickbooks 2014\xxxxx.qbw.
I've done a lot of research on the internet to fix this problem and keep getting stuff like its suppose to happen or its a .NET problem. I however believe its a permissions problem.
I have solved this issue by making sure in **ACTIVE DIRCTORY COMPUTERS AND USERS** that the user in question, is a **member of** the administrator built in group and domain admin. After you make these changes you should no longer receive that error code.
The problem with putting users as Domain Admins or any admin role is it totally violates PCI compliance standards for one and is an EXTREME security risk. Intuit needs to get better developers - their current staff is clueless!
You are responding to issues that occurred in 2009. This is 2016 - 8 years later. Intuit does not require any QB 2014 or newer user to be Admin. Not necessary.
I actually just solved this error a couple days ago. which means it still occurs? I understand the risk of makin someone a domain admin, but its not a schema admin or something like that which would be dangerous.
and since the error doesn't do much, you can leave and let it plague your system. like all the post suggest.
"You are responding to issues that occurred in 2009" - This issue is STILL a problem (that's how I discovered this forum post - yet again).
A problem that has yet to be resolved for Quickbooks Enterprise 2017. And yes, it does plague the system when you look at the network traffic (timeouts & retries) - it makes it slower, for sure (with all firewalls and antivirus disabled). It compounds the problem the more users accessing it simultaneously. One thing that helped (speedwise) was to upgrade to gigabit ethernet from 100Mbps ethernet.
A problem that has yet to be resolved for Quickbooks Enterprise 2017. And yes, it does plague the system when you look at the network traffic (timeouts & retries) - it makes it slower, for sure (with all firewalls and antivirus disabled). It compounds the problem the more users accessing it simultaneously. One thing that helped (speedwise) was to upgrade to gigabit ethernet from 100Mbps ethernet.
One thing that helped (speedwise) was to upgrade to gigabit ethernet from 100Mbps ethernet. <-- We have our networks set up this way and QuickBooks Premier V2017 is working fine. QB has a very chatty database so it needs the fastest possible network.