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?

connections to MSDE with .net installed

Hi,
Does the .net framework take up a connection to MSDE when starting up? We
are experiencing the following scenario:
Start up computer
Start our program that uses MSDE and the .net framework
Runs very slow
Shut down program on all computers
Stop MSDE service and Start again and it runs fine.
The reason I ask about the .net framework is that our program ran fine
before we migrated it to .net.
It seems like the govenor kicks in as soon as the machine is started - maybe
..net checks liscences or something?
..Net does not automatically take up connections or check licenses to MSDE or
any other DBMS. Run SQL Profiler (you have the Developers Edition of SQL
Server, don't you?) and see if any unexpected connections are being made to
the MSDE instance.
Jim
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:BF7838CC-CC14-4953-82A4-280A7B8213F7@.microsoft.com...
> Hi,
> Does the .net framework take up a connection to MSDE when starting up? We
> are experiencing the following scenario:
> Start up computer
> Start our program that uses MSDE and the .net framework
> Runs very slow
> Shut down program on all computers
> Stop MSDE service and Start again and it runs fine.
> The reason I ask about the .net framework is that our program ran fine
> before we migrated it to .net.
> It seems like the govenor kicks in as soon as the machine is started -
maybe
> .net checks liscences or something?

connection string problem...

I am experiencing a strange problem at the moment:

Basically, I have a webconfig file with the connection string to a sql server database.

I have 2 pages...both reference the connection string in the web config file...

the first page is a logon page - this accesses the database and executes properly, however, the second page raises an exception when opening the connection with the following

"The connectionString property has not been initialized".

As an additional note, I have pulled source code from 2 different machines and done a rebuild on the project - not sure why this would have a bearing on it but maybe I am missing something.

Anyone shed any light on it?

Thanks in advance!Can you post your web.config string and the one used in code
There may be a possibility that name in web.config and the one used in code are not in same case...or there is typo...|||The definition in the program is:

Dim cnRobDb As New SqlConnection(ConfigurationSettings.AppSettings("connectionString"))

and within the web config file:

<appSettings>
<add key="connectionString" value="data source=RobSQL;initial catalog=Robdb;user id=sa;pwd=??" />
</appSettings>|||Does it give error when you use

Dim cnRobDb As New SqlConnection("data source=RobSQL;initial catalog=Robdb;user id=sa;pwd=??" )

|||Tried coding as suggested and no it doesn't work - still get the same error. Like I say the wierd thing is that it the other program that runs first, the connection is made and data accessed correctly...mmm very strange.|||Can you post your code
Where are you writing the code for SqlConnection??|||Sushila,

thanks for taking the time to read and respond to this query, your help and time is very much appreciated!

I have solved the problem and interesting it was too. Basically, I had 2 versions of the .netframework installled: 1.0.3705 and 1.1 (installed simultaneosly).

This has not proved a problem until I imported code from another developer. It was importing the code that seems to have brought the problem out into the open. I removed version 1.1 and the problem has now disappeared! The database connection string in all code was identical and was stored in the web.config file but as shown in previous posts was manifesting a "connection not initialized" in certain programs but not others.

Thanks :)
Rob.