Network Error Ado
Contents |
List Welcome Guide More BleepingComputer.com → Internet & Networking → Networking Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. BLEEPINGCOMPUTER NEEDS YOUR HELP! BleepingComputer is being sued by Enigma Software because of a negative review
Dbnetlib Connectionread (recv()). General Network Error. Check Your Network Documentation
of SpyHunter. A case like this could easily cost hundreds of thousands of dollars. If we dbnetlib connectionwrite (send()). general network error. check your network documentation have ever helped you in the past, please consider helping us. To learn more and to read the lawsuit, click here. CONTRIBUTE TO OUR adodb connection error LEGAL DEFENSE All unused funds will be donated to the Electronic Frontier Foundation (EFF). If you accept cookies from this site, you will only be shown this dialog once!You can press escape or click on the X to close this box. https://support.microsoft.com/en-us/kb/942861 Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics http://www.bleepingcomputer.com/forums/t/473736/networking-error-ado-connection-timeout/ and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. Networking Error ADO connection Timeout Started by roberth5 , Nov 01 2012 10:54 AM Please log in to reply 5 replies to this topic #1 roberth5 roberth5 Members 31 posts OFFLINE Gender:Male Location:Michigan Local time:04:42 AM Posted 01 November 2012 - 10:54 AM I have a small network of about 30 workstation, running on SBS2011 server (w/DHCP). We run an accounting system using a separate server running SQL Express data base for the accounting system (about 10 to 12 users logged in at any one time). Recently I began getting (ADO ConnecttoCompanyTable Time Out Error) screens and the accounting system would shut down. At 1st we thought the database needed to be truncated, we did this a few times, and looked at the log file size, it was very small, not needing truncation at all. The company that build the Accounting system said I have a network issue. The servers are identical brand new Dells, 32GB Ram, taskmanager shows 16 processors, no real load on memory or processors. I can see the workstations loose their connection to the database server (ping 192.168.1.5 -t) freezes only on the workstation that gets an ADO error message and it can be ANY workstation, IT IS NOT WORKSTATION SPECIFIC.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/18616967/vb6accessado-jet-randomly-getting-disk-or-network-error-or-cannot-find-the Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs https://www.sitepoint.com/community/t/the-famous-general-network-error-check-your-network-documentation-error-message/1723 Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up VB6+Access(ADO/JET) Randomly getting “Disk or Network Error” or “Cannot find the input table or query X on Database Y” up vote 0 down network error vote favorite We have a Practice Management system that is about 15 years old. I've been working on it for about 12, and I've never encountered this problem until just recently, and we can't figure it out. It is written in VB6 which uses ADO/JET to access an Access .mdb file on the network. The application opens the connection when it starts, keeps it open while it's open, and closes it when it exits. general network error. It does a LOT of stuff with the DB - the system deals with Patient Accounts, Charges, Payments, Scheduling Appointments, and about a million other things. We have dozens of clients that use this program, each with their own DB and most of them 'offsite', where they have their own server, some number of workstations, between 1 and 20 users, pounding away at the system 24 hours a day, 7 days a week, and except for the occasional DB field bug or having to compact/repair DBs, it's pretty stable. About 3 weeks ago, we started seeing a problem that we hadn't seen before. We have an 'in-house' system setup for us to use: the DB is on our Server which houses maybe 10 other DBs, and only a couple of people connect in to this system. We started noticing that if someone logged into the system, went straight to our Scheduler screen, and then sat idle for about 5-10 minutes, they might get "Disk or Network Error", or "Cannot find the input table or query X on database Y". What's strange is that it SEEMS to happen only when 2 or more people are logged into that DB from different computers, and then one of them will get the error (Randomly?) but the other 2 users will be fine. There is
however, all suggested fixes have failed to work for me. I've tried setting POOLING=FALSE. I've also tried setting CONNECTION RESET=FALSE. Although both of these have allowed me to keep a connection open for slightly longer, after a while I would get the familiar "General network error. Check your network documentation." error message. It seems that, in general, SQL 7.0 / ADO .NET does not like it when you keep connections open for more than a half hour, even if you are constantly using that connection. The only way that I've been able to deal with the situation is to occasionally close the connection and open it again. Kind of kludgey, but it's the only fix that has worked. Does anybody else have a suggestion? rbutler 2004-09-15 16:26:40 UTC #2 Afro_Blanca said: It seems that, in general, SQL 7.0 / ADO .NET does not like it when you keep connections open for more than a half hour, even if you are constantly using that connection. The only way that I've been able to deal with the situation is to occasionally close the connection and open it again. Kind of kludgey, but it's the only fix that has worked. Does anybody else have a suggestion? I probably won't be too much help, but I was confused by your statement of leaving the connection open for more than half an hour. In your code you should do clean up, i.e., if you opening a connection to a db with a dataReader object, then you should follow this pretty much to the "T". Dim objConn as New OleDbConnection("Some connection string here") Dim objCmd as OleDbCommand Dim objDR as OleDbDataReader objCmd=New OleDbCommand("SELECT * FROM Table_Name", objConn) objConn.Open() objDR=objCmd.ExecuteReader() dgDataGrid.DataSource=objDR dgDataGrid.DataBind() objDR.Close() 'close the datareader object objConn.Close() 'close the connection This way, as soon as the page queries the db for the required data, it closes the DataReader object and Connection, therefore, elminiating the worry about having the connection open for any amount of time which leads to db server strain. This probably has led to more confusion, hopefully not. miseldine 2004-09-15 21:17:01 UTC #3 Should the SqlConnection class disconnect on disposal when garbage collected? You're right of course, you should formally disconnect,