Hi, SharePoint farm is as below. 1 SQL, 1 WFE, 1 Application server. SQL 2005 and SharePoint 2007 with SP1. SharePoint portal is working fine from 1 year, suddenly from today morning in the WFE eventvwr we are getting 27745, 3355 and 5586 event id errors. Site also giving error saying "unable to connect the content database". This is repeating for 10 to 15 min. when ever these errors occur in eventvwr sharepoint will not work. Please suggest on this issue. waiting for MS replies.. Regards, v235.

Can you connect to content/config Databases from WFE under SharePoint Web Farm account? Try to do this from SQL Server management Studio. Oleg

It sounds like a service account issue. Either the account was disabled, deleted, locked out, or the password has expired. You can troubleshoot this by manually connecting to SQL as Oleg described by opening SQL Server Management Studio and using the service account credentials. This is usually the same credentials that your web application pool is currently using, also known as the Application Pool Identity.http://donahoo-development.com

Hi all, thanks for reply... account was not disabled.. we are able to connect to SQL server through the account on which application poll is running. we used to take back of SQL database with that account. We are using single account on which sharepoint services are running, using same account SQL also configured in SharePoint configuration wizard. In WFE we are getting these event error, is it because of SQL is over loaded ?? or due to any other issues WFE is unable to reache the SQL databases during that time?? -------------------- v235

Hi V235, Could you tell us if the problem happens always at the same period of the day (each morning around 8 o'clock) ? Could you tell us if the problem happens only under heavy load ? Are you under a virtualize environnement ? You should read this article from Bill Baer http://blogs.technet.com/b/wbaer/archive/2009/10/06/intermittent-database-server-connectivity-and-microsoft-sharepoint-products-and-technologies.aspx, you will find a lot of information about Intermittent connectivity to a database server hosting Microsoft SharePoint Products and Technologies. MarioMon Blog/My Blog (in french) LinkedIn

Are you sure that account is not disabled, deleted, locked out, or the password has expired? I got this kind of error because of the service a/c password was expired. pls check SQL server log size.thanksArup MCTS - SharePoint Play Sudoku Online

did you follow this instruction http://technet.microsoft.com/en-us/library/cc561047(office.12).aspx and key thing is run IIS reset? and also this one http://technet.microsoft.com/en-us/library/cc561042(office.12).aspx. One thing did you check your SQL server data drive have enough space, and also make sure Database is not offline or readonly. are you able to get your central admin site? hope this help thanks -ws SharePoint administrator, MCTS,MCITP

Hi Mario, Arup... thanks for reply... Its occurring for every 20min, the servers are in virtual environment. Load is consistent through out the day. @Arup, account is working fine. Once long back it has been locked out for 5 mins, after that its unlocked then sharapoint is working as of normal. Suddenly from yesterday we are getting these errors in eventvwr. locking the account for certain duration causes any long run problems?? ---------------- regards v235

locking the account for certain duration causes any long run problems?? Answer to your questions: definitely not.. Can you pls paste the error that you get in eventvwr?thanksArup MCTS - SharePoint Play Sudoku Online

Hi Arup, thanks for reply.. This is 3355 event id error. Cannot connect to SQL Server. SERVER_Name not found. Additional error information from SQL Server is included below. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. ----------------------------------------------- The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database WSS_Content_PROD on SERVER. Check the database connection information and make sure that the database server is running.. --------------------------------------------------- Unknown SQL Exception 233 occured. Additional error information from SQL Server is included below. The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) --------------------------------- These are the errors which are occurring repeatedly in the eventvwr. Is there any problem from SQL server side or Network side. No recent updates of sharepoint, SQL and OS (windws 2003 server). -------------------------------------------------- regards v235

it may be bacause of the following: sql aliases you setup for your nonstandard sql port back when you were running SP2003. It appears that MOSS does not like the sql alias. On all of your WFEs, you may ran c:\WINDOWS\system32\cliconfg.exe and removed the Alias entries. Hope this helps someone solve their errors... Make sure all your credentials are up to date. Sometimes the farm account is a domain account who's password has expired or changed. To set curent credentials, see this post: http://blogs.msdn.com/joelo/archive/2006/08/22/712945.aspx Check memory space of your SQl server.. check the link also http://www.thesug.org/mossasaurus/wiki%20pages/event%20id%2027745.aspx thanksArup MCTS - SharePoint Play Sudoku Online

Hi Arup, SQL and WFE restart helped me. during that time few sites of huge content are moving from one location to other location in same site collection. Same is noted in the Eventvwr. May be above suggestion will help in some cases. --------------------------------- Regards V235

We have the same intermittent issue. Everything's been working fine for years, but once every other day or so (for the past couple months), we get the 3355 error, which repeats for about 10 to 15 minutes, then everything starts working fine again without any intervention. During those 10 to 15 minutes, we cannot connect to the SQL Server from the offending WFE, either via "ping", Management Studio, or even a pre-defined ODBC test connection; however we CAN connect to it from any other machine, including other WFE's in the same farm. It appears that all network connections from the offending WFE are being refused, but not any other machines. We thought it might be resolved by changing the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\synattackprotect Registry Key, but we turned that off months ago to no avail. (This turns on/off Sync Flood Attack protection on the local NIC, which would be a "per IP" connection block from other machines with suspicious connectivty to the target Server.) Anyone have any ideas? Mahalo from Hawaii! :^) -Ted

We have the same intermittent issue. Everything's been working fine for years, but once every other day or so (for the past couple months), we get the 3355 error, which repears for about 10 to 15 minutes, then everything starts working fine again without any intervention. During those 10 to 15 minutes, we cannot connect to the SQL Server from the offending WFE, either via "ping", Management Studio, or even a pre-defined ODBC test connection; however we CAN connect to it from any other machine, including other WFE's in the same farm. It appears that all network connections from the offending WFE are being refused, but not any other machines. We thought it might be resolved by changing the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\synattackprotect Registry Key, but we turned that off months ago to no avail. (This turns on/off Sync Flood Attack protection on the local NIC, which would be a "per IP" connection block from other machines with suspicious connectivty to the target Server.) Anyone have any ideas? Mahalo from Hawaii! :^) -Ted