Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP General > SQL errors after IIS5 to IIS 6 move

Thread Tools

SQL errors after IIS5 to IIS 6 move

M. M. Rafferty
Posts: n/a
Yesterday we moved a site from a shared Win2K box to a customer dedicated
Win2k3 server. The application is ASP, a huge busy site with MS SQL server
backend. Since the move, the website log is showing many entries with the
following error:


The connection string used in the client's web application is in the format:

Conn.Open " Provider=SQLOLEDB.1;Password=xxxx;Persist Security
Info=True;User ID=yyyy;Initial Catalog=zzzz;Data

From what I can tell from the SQL server, the timing on many of these errors
is at a point where the SQL server is at high CPU loads. However, this is
the same SQL server that has been used all along and the logs were not
showing SQL server connectivity issues prior to the move even when the SQL
server was under a load.

Are there any known out of the box differences between Win2K/IIS5 and
Win2k3/IIS6 that would be effecting the SQL server connectivity? Or what
settings might I have missed on the Win2K3 box that could be causing this
difference in behavior?


Mary Rafferty

Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
WebPart database iis 6.0, iis5.0 and personal web server yfa ASP .Net 1 12-11-2006 12:39 AM
having an issue with iis5 when I move code from iis6 =?Utf-8?B?Q2hyaXM=?= ASP .Net 0 10-11-2004 06:57 PM
Win2k, IIS5, IIS Lockdown Tool, URL Scan 13 Fallen ASP .Net Security 2 06-01-2004 07:24 PM
Difference in IIS5 and IIS6, GetObject errors David Lozzi ASP General 0 02-25-2004 06:40 PM
Dotnet, IIS5.0 and IIS lockdown/hardening tool/security Dave ASP .Net Security 0 07-11-2003 10:36 AM