Approved: Fortect
Here are some simple methods that can help you solve the common dbmssocn network error problem. Check the documentation for your network.
I choose vb.net connect sql follow server, connection string:
sqlcon.open
dim myadp as new sqlclient.sqldataadapter (“select * off table1”, sqlcon)
myadp.selectcommand.commandtype = text
myadp.selectcommand.commandtimeout = 180
dim mytable as datatable
myadp.fill (mytable) – Literally an error occured
1> After this error occurred, you logged into the SQL server multiple times (maybe ten minutes later)
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
2> If the first record of a person’s fill-in action is very large, this error will occur when the first record of the fill-in action is very small, without fail, and therefore when it is filled again, even if the extreme number is greater than a thousand. no fault either.
3> If this error occurs, I cannot fully use SQL Enterprise Manager and SQL Difficulty Analyzer Connect Server SQL.
A few days ago I didn’t have this error, I remember that a week ago I reinstalled iis, is that the reason?
I have an application or network hosted on a web server (Win 2k) that only communicates with a SQL 7.0 DB server on a separate DB server (NT 4.0). I also have a package 9 to 5 (Vb-App) as a task on a web server which isIt interacts with the Db server, which performs various functions. I am now using a sqloledb connection with this business stack to communicate with the database. 95% of the time the batch job works fine, but an accidental error occurs in one of the functions with the following data: “[DBMSSOCN] General network error. Check the documentation for your cell tower network. And this causes the function to collapse before completion. I know this because it has to update the maximum number of records, but when a problem occurs, it does not update the full 36 records. There is no rhyme or reason for refusing it because sometimes with heavy and even minimal use it is enough and the number of entries updated before it hits the plant can also be random.
This bug also shows up in one of 4 possible internal functions of the vb application that operate completely separately, suggesting that the problem is not in the code.
any tips and tricks or ideas that are likely to address the issue would be appreciated ..
Speed up your computer's performance now with this simple download.
