MS SQL Server - SQL 2000 SP4 Possible Problems

Author

SQL 2000 SP4 Possible Problems

Chris

2005-07-18, 11:23 am

We have a VB6 application failing to connect to our SQL2000 SP4 (SP4 just
installed). ADO over provider OLE/DB... any known issues?

Some users can connect successfully, many cannot.

David Gugick

2005-07-18, 1:23 pm

Chris wrote:
> We have a VB6 application failing to connect to our SQL2000 SP4 (SP4
> just installed). ADO over provider OLE/DB... any known issues?
>
> Some users can connect successfully, many cannot.

What's the error?

--
David Gugick
Quest Software
www.imceda.com
www.quest.com

Chris

2005-07-18, 1:23 pm

We also implemented Win2003 SP1 along w/ SQL 2000 SP4.

We applied registry key described below & problem fixed... HOly S! We are
lucky we stumbled across this...

This is newsgroup content that eggheadcafe.com's archiver has collected for
informational purposes. You can see the original thread and / or reply to a
post by visiting Google Groups, or using your newsreader

6/8/2005 1:16:03 PM General Network Error - Windows 2003 SP1, SQL Server
2000 SP4

FYI: If you are experiencing seemingly random errors such as

"DBNETLIB ConnectionWrite (send()). General network error. Check your

network documentation"

Refer to

http://support.microsoft.com/defaul...kb;en-us;899599

The problem arises on a busy SQL system and some requests will randomly seem

to be dropped with a General Network Error.

To fix:

HKEY_LOCAL_MACHINE\S
YSTEM\CurrentControl
Set\Services\Tcpip\P
arameters

Add a new DWORD key SynAttackProtect with value of 0. Restart server.

This referenced security change made in SP1 is implemented very, very poorly

and whoever wrote it, tested it, or reviewed it should simply be fired. NO

WHERE are the dropped packets documented....Shouldn't there be an entry in

the event log stating the the server was under suspected DOS attack and that

preventative action was automatically being taken?? IF there is a suspected

DOS attack going on, what is the point of dropping just some of the traffic

from the DOS source? It appears to randomly drop packets - it would be MUCH

better to block ALL the traffic from the source with a log entry stating
that

this source's traffic is now being blocked, and if you want to unblock the

source do x.

Arrgghh...I would think ANYONE with a busy SQL Server running on Win2003 SP1

would run into this problem!

"Chris" wrote:

>
> We have a VB6 application failing to connect to our SQL2000 SP4 (SP4 just
> installed). ADO over provider OLE/DB... any known issues?
>
> Some users can connect successfully, many cannot.
>

Chris

2005-07-18, 8:23 pm

spoke too soon. problem continues. receiving [TCP/IP Sockets]General network
error... calling MS

"Chris" wrote:
[color=darkred]
> We also implemented Win2003 SP1 along w/ SQL 2000 SP4.
>
> We applied registry key described below & problem fixed... HOly S! We are
> lucky we stumbled across this...
>
> This is newsgroup content that eggheadcafe.com's archiver has collected for
> informational purposes. You can see the original thread and / or reply to a
> post by visiting Google Groups, or using your newsreader
>
>
> 6/8/2005 1:16:03 PM General Network Error - Windows 2003 SP1, SQL Server
> 2000 SP4
>
> FYI: If you are experiencing seemingly random errors such as
>
> "DBNETLIB ConnectionWrite (send()). General network error. Check your
>
> network documentation"
>
> Refer to
>
> http://support.microsoft.com/defaul...kb;en-us;899599
>
> The problem arises on a busy SQL system and some requests will randomly seem
>
> to be dropped with a General Network Error.
>
> To fix:
>
> HKEY_LOCAL_MACHINE\S
YSTEM\CurrentControl
Set\Services\Tcpip\P
arameters
>
> Add a new DWORD key SynAttackProtect with value of 0. Restart server.
>
> This referenced security change made in SP1 is implemented very, very poorly
>
> and whoever wrote it, tested it, or reviewed it should simply be fired. NO
>
> WHERE are the dropped packets documented....Shouldn't there be an entry in
>
> the event log stating the the server was under suspected DOS attack and that
>
> preventative action was automatically being taken?? IF there is a suspected
>
> DOS attack going on, what is the point of dropping just some of the traffic
>
> from the DOS source? It appears to randomly drop packets - it would be MUCH
>
> better to block ALL the traffic from the source with a log entry stating
> that
>
> this source's traffic is now being blocked, and if you want to unblock the
>
> source do x.
>
> Arrgghh...I would think ANYONE with a busy SQL Server running on Win2003 SP1
>
> would run into this problem!
>
>
>
> "Chris" wrote:
>

Sponsored Links