Home » SharepointRSS

Intermittent connectivity loss to sql backend with sharepoint services 3.0

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..

Event ID: 3355
Cannot connect to SQL Server. jfsqlserver not found. Additional error information from SQL Server is included below.

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Event ID: 5586
Unknown SQL Exception 10054 occured. Additional error information from SQL Server is included below.

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.)

Event ID: 6398
The Execute method of job definition Microsoft.SharePoint.Administration.SPConfigurationRefreshJobDefinition (ID 68375afb-bafa-49b4-b1e5-7add4f677755) threw an exception. More information is included below.

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.)


Event ID: 3355
Cannot connect to SQL Server. jfsqlserver not found. Additional error information from SQL Server is included below.

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Thanks for any suggestions or insight anyone can offer!

-pmeyerson

 

29 Answers Found

 

Answer 1

This kind of issue mostly related Network Card or Routing Issue.

1. Check the routing

use the command tracert <DBServer>

check the number of hopes it taking and check with your network guys about the routing.

2. Netwwork Card Issue 

Network card could be a potential culprit in most of the case check the follwoing article

http://technet.microsoft.com/en-us/library/cc263061(office.12).aspx

 

Some issue are related Windows 2008 

Go to the Network Adapter Properties

 Configure button for the Network Card

Advanced Tab and Disable

1. IPv4 Checksum Offload

2. IPv4 Large Send Offload

3. TCP Connection Offload

 

Answer 2

I also have this error on test server.

Event ID: 3355
Cannot connect to SQL Server. jfsqlserver not found. Additional error information from SQL Server is included below.

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

 

I resolved this by starting SQL Server Browser service on Database Server

 

Answer 3

Hello,

On your database server, try to activate both TCP/IP and Named pipes through your surface area configuration tool.

Don't forget to restart your sql  server service, once done.

On the server  hosting wss 3.0, open notepad and save this Blank file as connection.udl, on the desktop.

Once done you have a tool that permit to test your connection to the database.

So open this file (run it with the credential used by wss to connect to your database).

On the provider tab choose "Microsoft OLE DB provider for sql server" then click next.

On the connection tab, enter the server name hosting your databases, and then choose you connection method (windows authentication, sql server authentication)

So Try to choose a database listed in the "select a database on the server" drop down list box and try to the connection by clicking on the "test the connection" button.

Regards,

Noureddine

 

Answer 4

Hello Noureddine,

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.

Have anyone a solution?

Thanks!


Regards,
Tobe
 

Answer 5

Hello,

Do you have a firewall between your web front end and your database server?

Regards,

Noureddine 

 

Answer 6

No firewall...
 

Answer 7

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?

Thanks,
-aps
 

Answer 8

Thank you for your suggestion! We'll give that a try and post back the results.

 

Answer 9

Hello,

You have to open TCP/UDP ports 137, 138, 139 and 445.

Regards,

Noureddine

 

Answer 10

Noureddine,


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.

Pirooz

 

Answer 11

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...

 

Answer 12

Hello again,

what for Service Packs do you have installed?
After I installed  Sharepoint SP1 i've become those errors. My SQL 2005 Server was RTM.
Yesterday I installed SP2 on my SQL Server and i've no more errors!

regards
 

Answer 13

Our environment is mixed right now because we're in the process of upgrading SQL and moving to new hardware.

Production is WSS 3.0 (no SP) with SQL Server 2000 SP4, 32 bit.  Development and test environments are also getting errors but those are WSS 3.0 (no SP) and SQL Server 2005 SP2, 64 bit.

We do plan to apply WSS SP1 soon.

 

Answer 14

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.
 

Answer 15

We have installed  WSS 3.0 with SP1, but still the same issue. Can anyone please help
 

Answer 16

We were able to resolve our issue. What about you?
There was some problem with our Network card setting.
 

Answer 17

hello magu1329,

what was the fix you applied on your NIC?
 

Answer 18

please please tell us what you changed on the nic card. these errors are driving us crazy and every other web page gives a cannot connect to database error.

thank you.
=^..^=
 

Answer 19

magu1329 said:

We were able to resolve our issue. What about you?
There was some problem with our Network card setting.



Glad you got your problem resolved.  Please don't leave the rest of us hanging - share your solution, please!
 

Answer 20

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").

Any ideas appreciated...
 

Answer 21

Could the 3355 ("Cannot connect to SQL Server") messages start coming if you're using an SQL named instance and port 1434/udp to the SQL-server is blocked?
 

Answer 22

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.

The problem is fixed for a couple of days if the SQL is restarted.

Any clue?

Thanks.
Michael
 

Answer 23

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".
 

Answer 24

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.
 

Answer 25

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.

 

Answer 26

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.

App Server -  3355, 5554, 7888, 7082, 10034, 10036

WFE1 - 3355, 27745, 10036, 5586, 5555, 7888

WFE2 - 3355, 27745, 10036, 6772, 7082

SSRS server  2005 (SP Integrated Mode) -  3355, 27745, 7888, 5586, 6772

 

SharePoint 2007 Enterprise, WSS 3.0 64 Bit

 

We have the infrastructure updates applied, December 2009 Updates applied, and WSS/MOSS SP2.

 

Everything is 64 bit, Win 2K3 SP2

 SQL Server 2005 Ent backend  is also 64 bit.

Anybody come accross anything that helped them?

Many thanks.

 

 

Answer 27

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.

Maybe this information will be useful to someone out there.

Rick

 

Answer 28

Hi All,

I'm getting 27745, 3355 and 6772. Its a new install of WSS3 SP2 with a sql  2008 R2 backend. The WSS3 servers are virtual running server  2003 and the SQL backend  is physical running 2008 R2.

This system currently has no load.

Has anyone found a solution?

Please help.....

 

 

Answer 29

Hi All,

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?

Ya gotta read Bill Baers Database Maintenance for Microsoft sharepoint  Products and Technologies (better yet read everything Bill writes) and Russ Houbergs Scaling SharePoint 2007 Storage Architecture (R2) ... Anyone using NAS for SQL Storage, (Just say NO)?

Reference

http://blogs.technet.com/b/wbaer/archive/2009/10/06/intermittent-database-server-connectivity-and-microsoft-sharepoint-products-and-technologies.aspx

http://go.microsoft.com/fwlink/?LinkId=111531&clcid=0x409

http://www.houberg.net/blogcontent/Scaling%20SharePoint%202007%20-%20Storage%20Architecture.pdf

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).

 

-Ivan


Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter