@Joe, the sites work 90% of the time. But 90% is a far far cry from
100%. So since traffic gets through most of the time, a firewall seems
like a really unlikely source of trouble (we also don't have direct
control over the firewall). I've looked for and not yet found any good
patterns to the times.
We're still using SQL 2005 (Microsoft SQL Server 2005 - 9.00.5000.00
(X64) Dec 10 2010 10:38:40 Copyright (c) 1988-2005 Microsoft
Corporation Standard Edition (64-bit) on Windows NT 6.1 (Build 7601:
Service Pack 1) ) ...
We use NHibernate (Hibernate for .NET) on some of these sites, so the
connection string is a little different, but looks like
Server=aisdb4.ais.msu.edu; Database=XXX; UID=XXX; PWD=XXX
We specify the "dialect" as MsSql2005
In our legacy (or classic, if you will) ASP site, the string is
Catalog=XXX;User ID=XXX;Password=XXX;OLE DB Services=-1
Carl Bussema III
Michigan State University Outreach & Engagement
Phone: (517) 353-8977 • Fax: (517) 432-9541
[log in to unmask]
On Tue, Jun 14, 2011 at 9:14 AM, Rytlewski, Jamie <[log in to unmask]> wrote:
> We had a similar problem when we moved our DB server to virtualization. What DB version are you using and what are you using for your connection string. We had to make some changes to our connection string to make it work. We were using something similar to:
> Provider=sqloledb;Data Source=xxx;Initial Catalog=xxx;Integrated Security=SSPI;
> Then we changed to:
> Provider=SQLNCLI10;Data Source=xxx;Initial Catalog=xxx;Integrated Security=SSPI;
> Which worked better for us since we were now connecting to a SQL 2008.
> Of course we are also using classic ASP on that site.
> -----Original Message-----
> From: Carl Bussema III [mailto:[log in to unmask]]
> Sent: Tuesday, June 14, 2011 8:51 AM
> To: [log in to unmask]
> Subject: [MSUNAG] Database timeouts
> (Cross-posting to WEBDEV and MSUNAG because not all webdev people are also their systems people, and the systems people may not be aware of this depending on the communication between them and the web teams.
> Apologies to those of you who get this twice.)
> Is anyone else on this list using AISDB3/AISDB4 for their websites (or other data-drive applications) and experiencing frequent timeouts? Our sites are reporting now up to 6-10 times per day errors such as these three below:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Timeout expired
> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
> System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
> All of these errors started after the May 23 AIS maintenance that moved these servers to a virtual context. It used to be we'd get something like this once a day around 9 p.m. (presumably the servers were going offline for backup, which is a completely separate rant), but now that's it's happening in the middle of the day, I'm trying to figure out if this is just us or if something's really messed up over there, so I know which direction to start poking.
> None of our data operations changed -- we're still requesting the connection the same way as always. Some of our sites are completely unchanged except minor content updates, so it's not like we changed something, but now we're seeing all these errors, and we're trying to get to the bottom of them.
> Thanks all for any information,
> Carl Bussema III
> Information Technologist
> Michigan State University Outreach & Engagement
> Phone: (517) 353-8977 . Fax: (517) 432-9541 [log in to unmask]