error 1603 installing microsoft sql native client

Hi
You will need to remove all references to the SQL Server 2005 before you
start the instalation. Did you have any prior to RTM vesrions on your
computer?
"Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>I am sql server 2005 installed, and I do not think I have sql server
>express. I tried to install express but I keep getting.
> Error 1603 installing Microsoft SQL Native Client.
> This worked before when reinstalling SQL Server 2005 but uninstalling it,
> but will this hurt SQL server 2005 if I do it again for SQL Express?
>I am sql server 2005 installed, and I do not think I have sql server
express. I tried to install express but I keep getting.
Error 1603 installing Microsoft SQL Native Client.
This worked before when reinstalling SQL Server 2005 but uninstalling it,
but will this hurt SQL server 2005 if I do it again for SQL Express?|||Hi
You will need to remove all references to the SQL Server 2005 before you
start the instalation. Did you have any prior to RTM vesrions on your
computer?
"Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>I am sql server 2005 installed, and I do not think I have sql server
>express. I tried to install express but I keep getting.
> Error 1603 installing Microsoft SQL Native Client.
> This worked before when reinstalling SQL Server 2005 but uninstalling it,
> but will this hurt SQL server 2005 if I do it again for SQL Express?
>|||When you mean references, do you mean all of SQL Server 2005? I would like
both on the computer, is that not possible. What is RTM versions? If I
uninstall Native Client from Add/Remove Programs, and install Express, will
that mess up SQL server 2005 in anyway, because I have no idea what the
native client is.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:evuRYJPlGHA.1340@.TK2MSFTNGP02.phx.gbl...
> Hi
> You will need to remove all references to the SQL Server 2005 before you
> start the instalation. Did you have any prior to RTM vesrions on your
> computer?
>
>
>
> "Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
> news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>|||When you mean references, do you mean all of SQL Server 2005? I would like
both on the computer, is that not possible. What is RTM versions? If I
uninstall Native Client from Add/Remove Programs, and install Express, will
that mess up SQL server 2005 in anyway, because I have no idea what the
native client is.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:evuRYJPlGHA.1340@.TK2MSFTNGP02.phx.gbl...
> Hi
> You will need to remove all references to the SQL Server 2005 before you
> start the instalation. Did you have any prior to RTM vesrions on your
> computer?
>
>
>
> "Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
> news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>

Error : Timeout expired. The timeout period elapsed...

Hi,

Iget this error from our web application every once in a while. " Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding". I emailmyself when an error occurs, and once every 2-3 days I get this timeouterror emails, like 5-10 emails in a span of few minutes. Then it goesaway. I have set the command timeout for 60 secs.

Itdoesn't happen from the same stored procedure, actually I have seen ittimeout from really simple 1 or 2 line stored procedures, which shouldn't normally take 1 sec. Its likesql server just shuts down for few minutes. We have somebackups and maintenance jobs scheduled, but they run only aftermidnight. I have checked theapplication event viewer, there are no warnings orerror messages forMSSQLSERVER.

Canany one tell me how to check whats going on during that short timespanwhen timeout error occurs, and what causes it? I don't want to run sqlprofiler continuously for 2-3 days, I am afraid it will slow down theserver more.

Thanks.

It could be locking|||Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records|||

websolutions:

Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records

I agree read the performance tuning tips in the link below and run SQL Server profiler to find out what is causing your error. Hope this helps.

http://msdn.microsoft.com/msdnmag/issues/06/07/WebAppFollies/default.aspx