My Sharepoint 3.0 services that were bundled with SBS 2008 appear to be working fine. Companyweb, etc, all work w/o issue, so I don't want to take violent action, but these errors seem to be accellerating so I would love to know if there is a known solution.
I typically receive the following (these are in reverse time order, latest at the top, just as they appear in the event log):
Error Event ID: 3760 SQL Database 'ShareWebDb' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below. Cannot open database "ShareWebDb" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
one second earlier:Error Event ID: 2424 The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file on the search server Search'
Information Event ID: 18456 No description, here is the Details:- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System><Provider Name="MSSQL$MICROSOFT##SSEE" /><EventID Qualifiers="49152">18456</EventID><Level>0</Level><Task>4</Task><Keywords>0x90000000000000</Keywords><TimeCreated SystemTime="2010-11-12T18:35:06.000Z" /><EventRecordID>491461</EventRecordID><Channel>Application</Channel><Computer>myserver.mydomain.local</Computer><Security UserID="S-1-5-20" /></System>- <EventData><Data>NT AUTHORITY\NETWORK SERVICE</Data><Data>[CLIENT: <named pipe>]</Data><Binary>184800000E000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary></EventData></Event>
Two seconds earlier
Information Event ID 17137 No description, here is the Details:- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System><Provider Name="MSSQL$MICROSOFT##SSEE" /><EventID Qualifiers="16384">17137</EventID><Level>4</Level><Task>2</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2010-11-12T18:35:04.000Z" /><EventRecordID>491460</EventRecordID><Channel>Application</Channel><Computer>mysever.mydomain.local</Computer><Security UserID="S-1-5-20" /></System>- <EventData><Data>ShareWebDb</Data><Binary>F14200000A000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary></EventData></Event>
I get more 3760 errors than 2424's. However, the 2424's do seem to usually correspond to a 3760 18456 17137 occurance and the 3760 are always preceeded by 18456 17137. I was getting one or two sets a day, lately that has increased to 5 or 10.
I've done a lot of web research on Sharepoint Errors 3760 and 2424 and I see a number of people are experiencing the the same issue. Most of what I've come across for solutions do not apply, since errors are intermittent, not chronic and my public remote URL has already been added to BackConnectionHostNames as per:
I installed the SQL Server Management Studio Express so I could try to track down the permissions on this database. I see the SQL server instance, MYSERVER\Microsoft##ssee, and it shows as running, but when I try to connect to it I get the following error: "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)" I'm assuming that is because I don't have access permission for that internal database.
I don't see any errors in the event log related to failed logins or any errors at all from the SQL server, but there are the time matching informational entries right before the error events and lots of other 17137's and 2803's from MSSQL$Microsoft##ssee
Did you see this post (Issue #1)?
-Kevin Weilbacher (SBS MVP)
"The days pass by so quickly now, the nights are seldom long"
KW Support MVP Blog
MVP's do NOT work for Microsoft. We give our time freely to support the SBS community!
Thank you Kevin, that does seem to match my symptoms and I have made the change suggested. Just incase that page becomes unreachable by others, here is the part of the page that applies to this:
Receive event error 3760 and 6398 on SBS 2008
Issue was caused by incorrect Auto Close option for ShareWebDb database
1. On the SBS 2008 server, click Start -> All Programs -> Microsoft SQL Server 2005, right click SQL Server Management Studio Express and choose run as administrator.
NOTE: You must run it as administrator to perform steps below.
2. In the Server Name box, type \\.\pipe\MSSQL$Microsoft##SSEE\sql\query, click connect.
3. Expand Database node and right click the ShareWebDb then choose properties.
4. Click Options in the left pane, in the right pane, please check whether the Auto Close option is set to True, if so, please change it to False.
I get this error thus:
Event Source Event ID Last Occurence Total Occurences
Windows SharePoint Services 3 3760 16/12/2010 19:10:37 10
Event Details: SQL Database ''SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6'' on SQL Server instance ''AUDORSERVER\Microsoft##SSEE'' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6" requested by the login. The login failed.
The setting suggested above was set to False. In Central Admin under Content DBs the ShareWebDb is there. Further suggestions as to resolution welcome.
Many thanks for your time.
I really wish /other people/ would not mark my questions as answered... It's my question, I did not report that it was solved. This problem is ongoing.
I get one of each error once a day without fail. It seems to coincide with the backup. Machine now has 16GB RAM 1333MHz bus speed, and isn't really doing much work at all... just serving a few files to customers and Exchange accounts for 4 users.
Everything else I can find on the net is about these errors occurring every 5 to 10 minutes, not once a day. There is a /separate/ problem related to backup on SBS systems which is being masked in the error reporting by these other issues which cause more frequent logging of these errors. This less frequent error which I am experiencing is still important and should be KNOWN and hopefully solved.
- Edited by James Newton Monday, October 24, 2011 4:01 PM
Don't understand your first comment. Did I do that?!
My Backup has gone completely AWOL. It ignors my data partitions now and as I cannot get answers to my relevant posts (I guess posting to often makes one a PITA). so I must consider a third party solution!
Many thanks for your time.
No, it still happens along with the backup, but not every day. Sometimes it happens, sometimes it doesn't. Makes me very nervous that perhaps the backup, on the days when the error occurs, is not really a full backup.