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:3355Cannot 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:5586Unknown 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:6398The 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:3355Cannot 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
February 13th, 2008 5:02am
Hello, On your database server, try to activate both TCP/IP and Named pipesthrough 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 providerfor 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
February 13th, 2008 8:23am
Hello, Do you have a firewall between yourweb frontend and your database server? Regards, Noureddine
February 13th, 2008 4:57pm
February 13th, 2008 5:15pm
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
February 13th, 2008 11:53pm
Thank you for your suggestion! We'll give that a try and post back the results.
February 16th, 2008 5:14am
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
February 19th, 2008 6:56pm
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
March 18th, 2008 7:11pm
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.
August 6th, 2008 9:29pm
We have installed WSS 3.0 with SP1, but still the same issue. Can anyone please help
August 7th, 2008 6:32pm
We were able to resolve our issue. What about you?There was some problem with our Network card setting.
August 19th, 2008 11:15pm
hello magu1329,what was the fix you applied on your NIC?
October 4th, 2008 12:04am
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!
November 26th, 2008 5:04pm
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?
March 11th, 2009 6:59pm
Hi,We have the same problems and they started suddenly a few weeks ago. We have "Windows Server 2003 R264-bit sp2,MOSS 2007 sp1" and "Windows Server 2003 R264-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
April 23rd, 2009 4:51pm
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/328476Sp2 for sharepoint fixes this.
September 7th, 2009 2:03pm
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.
May 20th, 2010 11:10am
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
June 11th, 2010 2:24pm
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
December 12th, 2010 1:09pm
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
January 27th, 2011 7:23am