| View previous topic :: View next topic |
| Author |
Message |
trurl
Joined: 17 Oct 2006
Posts: 5
|
 Posted: Tue Oct 17, 2006 2:42 am Post subject: ODBC test |
 |
|
Time to time on some ODBC test happens strange error:
Unknown Error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation<cr> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv())
Used ODBC driver "SQL Server" version 2000.86.18.30.00 with few SQL Servers 2005. HostMonitor 6.10 on Windows 2003 R2. 1Gb network connection. |
|
| Back to top |
|
 |
trurl
Joined: 17 Oct 2006
Posts: 5
|
| Posted: Tue Oct 17, 2006 4:02 am Post subject: |
|
|
| Same problem with Hostmonitor 6.24 |
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Tue Oct 17, 2006 6:09 am Post subject: Re: ODBC test |
|
|
| trurl wrote: | | [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()) |
Such error means the server forcefully closed the connection. Hm. Could you check the MS SQL log for the errors?
| trurl wrote: | | Used ODBC driver "SQL Server" version 2000.86.18.30.00 with few SQL Servers 2005. |
With SQL Servers 2005 client is supplied SQL Native Client ODBC driver(sqlncli.dll 2005.90.2047.00). Coud you try to setup the datasource using this driver?
There are some special ODBC options, located on Options > Misc > ODBC related options tab. Have you enabled "Connection pooling" or "Do not use SQLFetchAbsolute command" options?
Regards,
Max |
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Tue Oct 17, 2006 6:38 am Post subject: |
|
|
BTW. Do you have any firewall or antivirus software installed on the machine where HostMonitor is running?
Regards,
Max |
|
| Back to top |
|
|
trurl
Joined: 17 Oct 2006
Posts: 5
|
| Posted: Tue Oct 17, 2006 7:48 am Post subject: Re: ODBC test |
|
|
| KS-Soft Europe wrote: | | trurl wrote: | | [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()) |
Such error means the server forcefully closed the connection. Hm. Could you check the MS SQL log for the errors?
| trurl wrote: | | Used ODBC driver "SQL Server" version 2000.86.18.30.00 with few SQL Servers 2005. |
With SQL Servers 2005 client is supplied SQL Native Client ODBC driver(sqlncli.dll 2005.90.2047.00). Coud you try to setup the datasource using this driver?
There are some special ODBC options, located on Options > Misc > ODBC related options tab. Have you enabled "Connection pooling" or "Do not use SQLFetchAbsolute command" options?
Regards,
Max |
No any errors on SQL server side.
With "SQL Native Client" I've time to time getting another error:
| Code: | | Unknown Error: [Microsoft][SQL Native Client]Failed to read prelogin response<cr> [Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english<cr> [Microsoft][SQL Native Client][SQL Server]Changed database context to 'DataStore'<cr> [Microsoft][SQL Native Client]Client unable to establish connectio |
"Connection pooling" turned on
"Do not use SQLFetchAbsolute command" turned off (but with "on" is same result)
Antivirus not used yet (new monitoring server). Firewall used, but open as router (no NAT) on this protocols |
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Tue Oct 17, 2006 8:45 am Post subject: Re: ODBC test |
|
|
| trurl wrote: | | Error: [Microsoft][SQL Native Client]Failed to read prelogin response |
Quite strange error. It seems the server is not ready to process a new local connection, possibly due to overload. How often does HostMonitor perform the ODBC tests? Do you use lightweight query or something complex (stored proc, etc)? What about other software that uses SQL servers? Could you check the server load?
I think, following article might be helpful: http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
Regards,
Max |
|
| Back to top |
|
|
trurl
Joined: 17 Oct 2006
Posts: 5
|
| Posted: Tue Oct 17, 2006 9:25 am Post subject: Re: ODBC test |
|
|
| KS-Soft Europe wrote: | | trurl wrote: | | Error: [Microsoft][SQL Native Client]Failed to read prelogin response |
Quite strange error. It seems the server is not ready to process a new local connection, possibly due to overload. How often does HostMonitor perform the ODBC tests? Do you use lightweight query or something complex (stored proc, etc)? What about other software that uses SQL servers? Could you check the server load?
I think, following article might be helpful: http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
Regards,
Max |
Running 15-20 tests (interval 10 minutes)
Stored procedures, but very light
Fails not related to server load 
With SQL Server driver it's happens 5-10 times per day, with SQL Native Client it's fails every time with 1-5 tests)
Sometimes getting error:
| Code: | | Unknown Error: [Microsoft][SQL Native Client]TCP Provider: The specified network name is no longer available.<cr> <cr> [Microsoft][SQL Native Client]Communication link failur |
when few ODBC test to same server finished without problem in same time. |
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Tue Oct 17, 2006 12:43 pm Post subject: |
|
|
Looks like problem with SQL Server. I have looked through Google and found the following:
| Quote: | 5.1 Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
If TCP/IP networking is turned on, client connections to an instance of the SQL Server Express Database Engine running on Windows Server 2003 Service Pack 1 might fail with the following error: "ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing connection was forcibly closed by the remote host"."
This might occur when you are testing scalability with a large number of client connection attempts. To resolve this issue, use the regedit.exe utility to add a new DWORD value named SynAttackProtect to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ with value data of 00000000.
Security Note:
Setting this registry key might expose the server to a SYN flood denial-of-service attack. Remove this registry value when testing is complete.
Caution:
Incorrectly editing the registry can cause serious problems that might require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from editing the registry incorrectly can be resolved. Before editing the registry, back up any valuable data. For information about how to back up, restore, and edit the registry, Microsoft Knowledge Base article 256986. |
You may find full article here: http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/ReadmeSQLEXP2005.htm
It might help.
Regards,
Max |
|
| Back to top |
|
|
trurl
Joined: 17 Oct 2006
Posts: 5
|
| Posted: Tue Oct 24, 2006 3:16 am Post subject: |
|
|
Still every time happen random errors. For example:
| Code: | | Error: Access violation at address 00000000. Read at address 00000000 |
or
| Code: | | Error: [Microsoft][SQL Native Client] Failed to read prelogin response |
|
|
| Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006
Posts: 2832
|
| Posted: Wed Oct 25, 2006 2:33 am Post subject: |
|
|
Sorry, we could not reproduce such behaviour in our test environment. Probably, you need adjust some network or MS SQL server settings.
Please, read following article:
http://support.microsoft.com/kb/170359/en-us
It might help.
Regards,
Max |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in
