connectivity issues after SP2

Recently I upgraded a prod db server and since then users are experiencing
connectivity issues. The application errors out with :
Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
Check your network documentation.
They try to ingore the error and sometimes work but not always.
No changes on the application side. The server is 64b Windows Server 2003 EE
with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their SP2
..
I do have a test env. and there everithing went smoothly and no problems
have been reported.
No errors in the logs (both windows and sql server). A warning that network
card driver is outdated (Broadcom 1G). No network issues
The server is usually heavy loaded 8-5 and these issues start early
afternoon and once started happening they dont go away until users are done
for the day.
I am afraid of db corruption and all I can think about is to roll off the
service packs (both windows and sql)
Please help
Ellie
Can you show us connection string?
"Ellie" <Ellie@.discussions.microsoft.com> wrote in message
news:6C9C0F3B-C118-4B71-9F40-119D874EE783@.microsoft.com...
> Recently I upgraded a prod db server and since then users are experiencing
> connectivity issues. The application errors out with :
> Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
> Check your network documentation.
> They try to ingore the error and sometimes work but not always.
> No changes on the application side. The server is 64b Windows Server 2003
> EE
> with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their
> SP2
> .
> I do have a test env. and there everithing went smoothly and no problems
> have been reported.
> No errors in the logs (both windows and sql server). A warning that
> network
> card driver is outdated (Broadcom 1G). No network issues
> The server is usually heavy loaded 8-5 and these issues start early
> afternoon and once started happening they dont go away until users are
> done
> for the day.
> I am afraid of db corruption and all I can think about is to roll off the
> service packs (both windows and sql)
> Please help
|||> I am afraid of db corruption
No, I doubt it. You would be seeing different symptoms than connectivity
issues.
Have you considered paying attention to the network card driver issue? And
are you sure this isn't a network issue that happens to have started at or
around the same time you installed the service packs? Maybe there is some
process that is now running in the early afternoon that is hogging bandwidth
and making the network unreliable?

connectivity issues after SP2

Recently I upgraded a prod db server and since then users are experiencing
connectivity issues. The application errors out with :
Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
Check your network documentation.
They try to ingore the error and sometimes work but not always.
No changes on the application side. The server is 64b Windows Server 2003 EE
with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their SP2
.
I do have a test env. and there everithing went smoothly and no problems
have been reported.
No errors in the logs (both windows and sql server). A warning that network
card driver is outdated (Broadcom 1G). No network issues
The server is usually heavy loaded 8-5 and these issues start early
afternoon and once started happening they dont go away until users are done
for the day.
I am afraid of db corruption and all I can think about is to roll off the
service packs (both windows and sql)
Please helpEllie
Can you show us connection string?
"Ellie" <Ellie@.discussions.microsoft.com> wrote in message
news:6C9C0F3B-C118-4B71-9F40-119D874EE783@.microsoft.com...
> Recently I upgraded a prod db server and since then users are experiencing
> connectivity issues. The application errors out with :
> Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
> Check your network documentation.
> They try to ingore the error and sometimes work but not always.
> No changes on the application side. The server is 64b Windows Server 2003
> EE
> with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their
> SP2
> .
> I do have a test env. and there everithing went smoothly and no problems
> have been reported.
> No errors in the logs (both windows and sql server). A warning that
> network
> card driver is outdated (Broadcom 1G). No network issues
> The server is usually heavy loaded 8-5 and these issues start early
> afternoon and once started happening they dont go away until users are
> done
> for the day.
> I am afraid of db corruption and all I can think about is to roll off the
> service packs (both windows and sql)
> Please help|||> I am afraid of db corruption
No, I doubt it. You would be seeing different symptoms than connectivity
issues.
Have you considered paying attention to the network card driver issue? And
are you sure this isn't a network issue that happens to have started at or
around the same time you installed the service packs? Maybe there is some
process that is now running in the early afternoon that is hogging bandwidth
and making the network unreliable?

Connection without MDAC2.6

Hello Faculties
If a client is not upgraded with MDAC 2.6, is it still possible to
connect to SQL Server 2000 from that client?

Thanks in advance
Debashishdebashish (debashish_majumdar@.rediffmail.com) writes:
> Hello Faculties
> If a client is not upgraded with MDAC 2.6, is it still possible to
> connect to SQL Server 2000 from that client?

Yes, but you may experience limitations in functionality. For instance,
MDAC 2.5 and earlier does not support named instances. You may not be able
to use the bigint data type, or XML data.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp