[Microsoft][SQLServer 2000 Driver for JDBC]net dll not initi

We are currently in the middle of piloting a new application using
MSDE, and some of our users are getting the following SQLException
when attempting to query the database. The exception occurs
sporadically, and it only seems to happen after the application is
used for an extended duraton of time. Also, once the exception
occurs, it seems like the only way to obtain a good connection again
is to restart the JVM. Successive calls to get a connection from the
drivermanager fail otherwise.
Our calling application uses JNI to call a java function which is
responsible for creating the database connection and querying the
database.
Any help would be appreciated!
Here's the exception:
[Microsoft][SQLServer 2000 Driver for JDBC]net dll not initialized
(WSAStartup): socket write error
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]net
dll not initialized (WSAStartup): socket write error
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.sub mitRequest(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown
Source)
at com.microsoft.jdbc.base.BasePreparedStatement.exec uteQuery(Unknown
Source)
Hello,
WSAStartup is a Windows API that is called (typically once) during an
application's startup to start using Winsock calls. Since you have been
using sockets up until the failure, it had to be called prior to that. It
looks like somehow the Winsock got uninitialized or unloaded but the JVM is
unaware of that.
Can you try opening a socket directly when this happens to confirm? You
could try something like:
java.net.Socket conn = new java.net.Socket("localhost", 1433);
and if you get the same failure, I would say this is an issue in the JVM.
Thanks,
Kamil
Kamil Sykora
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/securXity.
| NNTP-Posting-Date: Wed, 13 Jul 2005 00:58:48 -0500
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]net dll not initi
| From: akraai@.hotmail-dot-com.no-spam.invalid (akraai)
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Mime-Version: 1.0
| Content-Type: text/plain; charset=ISO-8859-15
| Content-Transfer-Encoding: 8bit
| User-Agent: newsSync (SQL Server) 112669
| Message-ID: <foWdneohifEFMEnfRVn_vg@.giganews.com>
| Date: Wed, 13 Jul 2005 00:58:48 -0500
|
| We are currently in the middle of piloting a new application using
MSDE, and some of our users are getting the following SQLException
when attempting to query the database. The exception occurs
sporadically, and it only seems to happen after the application is
used for an extended duraton of time. Also, once the exception
occurs, it seems like the only way to obtain a good connection again
is to restart the JVM. Successive calls to get a connection from the
drivermanager fail otherwise.
Our calling application uses JNI to call a java function which is
responsible for creating the database connection and querying the
database.
Any help would be appreciated!
Here's the exception:
[Microsoft][SQLServer 2000 Driver for JDBC]net dll not initialized
(WSAStartup): socket write error
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]net
dll not initialized (WSAStartup): socket write error
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.sub mitRequest(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown
Source)
at com.microsoft.jdbc.base.BasePreparedStatement.exec uteQuery(Unknown
Source)
|

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue