We have sharepoint services 3.0 installed on a single server, and are using a backend sql 2005 database. this is a test environment with low use.

we occasionally encounter issues loading pages where the page load will time out. I see several of the errors listed below which seem to indicate that the connection to the back end sql server was forcibly closed, or there may have been an authentication issue .... but i do not understand why this issue is intermittent.

Has anyone seen this issue, or have troubleshooting suggestions?

Event ID: 27745#50071: Unable to connect to the database WSS_Content on jfsqlserver. Check the database connection information and make sure that the database server is running..

thanks for your tip.I've the same problem with this many eventlog entries, but mine isn't a test environment!And my WFE Server crashed the last three days at night. After a restart it is all ok. No errors in the eventlog. After 6-9h the errors come back.

I've tried what you say, but it is all ok! TCP/IP and Named pipes are activated and the connection test is successful.

I'm having the same exact issues and have a firewall between my wfe and database server. We have opened ports 1433 and 1434 (the sql ports). Is there anything else that you can think that we might be missing?

Are you sure these connections are required? I have the same issues and have a firewall between WFE and SQL servers. It looks like when the server is bounced the errors go away for a while. Eventually the errors start to come back. That being the case, I don't know why opening up firewall ports will help the situation.

We have been experiencing the same issue. Out of curiosity is anyone seeing errors in your WSS diagnostic logs? I am and they are mainly "unexpected query execution failure" errors from SQL Server. I don't know if they're related issues yet but it seems likely.

The strange thing is this happening in production and we are not receiving complaints from users. I have a ticket in with Premier Support but that's usually a shot in the dark these days...

I am also getting the same issues, the erros get logged once in a while and after we have restrated the machine for almost half a day we dont get to see any error, but later again we see the same issues 3355 and 5586.

I'm having this issue as well! A lot of event id 3355 more or less constantly, but so far no users have complained! Then suddenly it loses database connectivity completely, and we get a lot of 3358 ("Specified SQL Server not found") and 5586 ("Unknown SQL Exception -1 occured").

Hi,We have the same problems and they started suddenly a few weeks ago. We have "Windows server 2003 R2 64-bit sp2, MOSS 2007 sp1" and "Windows Server 2003 R2 64-bit sp2, SQL 2005 sp2" and we can not relate the problems to start in connection to the service packs.It only seems that the MOSS sites with common shared services is affected by the errors, the SQL still works for other applications.We do not have a firewall between them.Both servers are Virtuel Machines.

So it sounds like no one has been able to correct this issue? We started experiencing this issue after our service accounts were disabled and we had to run stsadm updatefarmcredentials.

One thing I have noticed is that SharePoint runs ok overnight when usage is down. It is just when volume picks up on the server that we start getting the errors and sites start going down with "database configuration issue".

We run in to this as well. It turned out to be a connection pooling issue. or the lack of connection pooling. That is why it works fine when the load is low and the errors pops up once the load gets up. Read this KB: http://support.microsoft.com/kb/328476 Sp2 for sharepoint fixes this.

We are also experiencing this issue, we are on SQL 2005 SP3 + CU7 and MOSS 2007 sp2 + CU Oct 2009. The issue has started recently, but I'm not sure what triggered it, both servicepacks and CUs were recently applied for both platforms, but I'm not sure it
is related. Anyone out here with more info on this issue, as we're clearly not the only one.

Hello, we are seeing the same exact issues with a farm that has been running for almost 3 years. Scouring the web for solutions but it's hard to correlate all these errors.

Below is a list of our servers (by role) and the event errors we are seeing in clusters at the same time frame, these are sporadic and we have not received user complaints at all,
but the nature of these alerts is troubling, i.e. DB connectivity issues.I did get a couple of can’t connect to db errors when loading pages in Central Admin, but they clear up with a refresh.

We are still investigating, but the issue might be caused, in our environment, by an issue in the networkdriver of our Hyper-V 2.0 implementation. For more information on this, please refer to
KB981836 . As said before, we are not 100% sure yet, but have some indication that we are experiencing this issue.

Has everyone checked what time their sql Backups and Maintenance Plans kick off and correlated the time with the event log errors. How about Full Crawls do they over lap the Full backups or transaction log backups? What is your IO Wait Stats, Whats
report are yoiu using to monitor SQL Health, what is the primary cause for the wait? What third party apps are installed?

Theres more read Bill on intermittent Connectivity...... After you install Windows server 2003 Service Pack 2 (SP2) or Windows Server 2003 Scalable Networking Pack (SNP) on a computer that has a TCP/IP Offload-enabled network adapter, you may experience
many network-related problems. Review the Knowledge Base article here (http://support.microsoft.com/kb/948496/en-us) for options and instructions on how to disable SNP features in Windows Server
2003 (see also below for additional information).