RE: Random IIS SQL Timeout

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Baldo and thanks for the response.

I have learned a little more. The error comes when I try to open recordsets,
not when I open connections. There are about 15 - 35 connections on the SQL
server (Performance monitor).

I really have no idea what to do. I knew of the link you posted, but it
hasn't helped me.

Let me know if you find an answer.

Could this be solved by a MS support case? Which category of support case
should that be? Development, IIS or SQL 2005?

"Baldo" wrote:

Check out this post by Microsoft.

http://support.microsoft.com/?id=328306

I am having the same problem with one server with Windows 2003 R2. The other
server is a Windows 2003 and has no problems with the exact same install of
software. I am now trying to determine if it is an operating system (MDAC)
problem or not.

Bob

"Limbo" wrote:

I am having problems with our CMS system (self-developed in ASP) that is
running on two servers. We have about 20 web applications running the same
CMS system on these servers.

Both servers have Windows 2003 Server R2 installed with all updates and the
SQL server is running MS SQL 2005 with SP1 + additional updates.

We have had the system running on one server running Windows 2003 with SQL
server 2000 (running both from same server) without this problem. Now that we
have upgraded to running IIS on one server and SQL on another, we are
experiencing random timeout problems.

The problem happens a few times each day. Within a minute or so, I get
several of these error messages:

Category: Microsoft OLE DB Provider for SQL Server
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.

and

Category: Microsoft OLE DB Provider for SQL Server
Description: Timeout expired

The errors appear ar random in the ASP files. Not a single call that gives
the error.

I have tried installing all updates and looking through configs but I can't
see a reason for this.

I have tried pinging both servers from a 3rd server, and there is never a
connection problem. Have had the network admin check all network
configurations, but he found no problems.

Any suggestions on what is causing this? Which steps should I try?

.

Relevant Pages

  • Re: Publishing Error FP2003 to Remote site
    ... I have 2 machines running Windows XP Pro SP2, with automatic updates. ... Ron Symonds (Microsoft MVP - FrontPage) ... Created a new vurtual server ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: Error 10061, 0x800ccc0e, bug?
    ... It's definitely the April Windows update!!!! ... Checked program files after restore and the updates are gone and OE is ... receive mail after changing account in windows. ... Mike, the error indicates that you are failing to connect to the server, ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Sql Server 2005 Dev. Ed. on Windows Server 2003
    ... Check out this KB which is about transferring Logins: http://support.microsoft.com/kb/246133 ... Also, since this is running on a newly installed Windows Server 2003, is ... them from your older SQL Server instance to the newer one. ...
    (microsoft.public.sqlserver.setup)
  • Re: Multiple issues (Server & Desktop) since last Windows Updates
    ... and I am still fighting problems since the reboot after the updates. ... since SP1 on our main Domain controller, which is also DNS server for itself ... I have another two Windows Server 2003 Standard servers that I ... Lexmark printers printer, ...
    (microsoft.public.windows.file_system)
  • Re: New Windows Infrastructure
    ... vendor's application runs on windows with an SQL database and I will also need a web server for a separate module which will allow our customers to access account data online. ... I would think that if the app runs on windows, I do not need the citrix server. ... It makes sense to have separate DCs though, because let's say you want to upgrade your Active Directory in two weeks time, with separate DCs it's easy, but if you've got a bunch of apps installed it could be a nightmare. ...
    (microsoft.public.win2000.setup_deployment)