ODBC SQL Server 驱动程序错误
我有一个 VB6 应用程序，可以通过 ODBC 连接访问数据库。它将正常运行几个小时，然后出现以下错误。有什么想法吗？
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite(WrapperWrite())
I have a VB6 app that access's a database thru a ODBC Connection. It will run fine for a few hours then I get the following Error. Any Ideas?
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite(WrapperWrite())
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
通过 Google 搜索该错误，听起来这只是 ADO 表示无法连接的方式 - 服务器无法访问。该服务器上或使用该数据库的其他服务是否在出现此错误的同时变得不可用？听起来客户端刚刚失去了连接，所以我会寻找周围的任何东西 - 网络连接丢失，或者服务器宕机/不堪重负，仅举几个例子。
From Googling the error, it sounds like that's just ADO's way of saying it can't connect - that the server is unreachable. Are there are any other services on that server or that use the database that become unavailable at the same time as this error? It sounds like the client is just losing its connection, so I'd look for anything around that - dropped network connectivity, or a downed/overwhelmed server, to name a few examples.
您的程序是否必须通过网络才能访问 Access 文件？
如果是这样，我会调查任何间歇性网络连接问题，特别是如果您的程序始终连接到数据源。
检查所有日志，了解发生错误时网络上发生的情况。
如果可能的话，将您的应用程序更改为仅在需要访问数据源时连接到数据源，然后在完成后断开连接。
是否有多个程序实例在同一和/或不同的机器上运行？如果是这样，他们会同时收到错误吗？
如果可能的话，尝试在同一台机器上运行多个程序实例，看看它们是否同时出现错误。
另外：
初始连接后大约相同的时间内会发生错误吗？
您的应用程序中相同程度的不活动是否会发生该错误？
Does your program have to reach across a network to get to the Access file?
If so I'd look into any intermittent network connectivity issues, especially if your program is always connected to the data source.
Check any logs you can to see what's happening on your network at the time of the error.
If possible change your app to connect to the data source only when you need to access it and then disconnect when done.
Is there more than one instance of the program running on the same and/or different machines? If so, do they all get the error at the same time?
If possible try to have more than one instance of you program running on the same machine and see if they all get the error at the same time.
Also:
Does the error happen about the same amount of time after initial connection?
Does the error happen about the same amount of inactivity in your application?