SharePoint Errors 3760, 18456 and 2436
Hello, In the appliction event log, I see errors 3760, 18456 and 2436 that happen at the same time. For the error 3760, I see this message: Cannot open database "WSS_Content_81" requested by the login. The login failed. Login failed for user 'PBTF\SvcMOSS'. So, I checked a few things: The SharePoint site is using a content database named STS_Chinook_1. This is from the Manage Content Databases page in Sharepoint 3.0 Central Admin. In SQL Server Management Studio, the STS_Chinook_1 database is filled with tables and data. In SQL Server Management Studio, I also see WSS_Content_81 as a database, but can't open the properties (an error is shown) and no objects are shwon underneath the database name. This is WSS 3.0 on a Windows Server 2003 server. The site is up and running, but SharePoint is trying to connect and use to this WSS_Content_81 (bad) database. What can I do disable/remove this bad database? Event Type: Failure Audit Event Source: MSSQL$MICROSOFT##SSEE Event Category: (4) Event ID: 18456 Date: 5/13/2011 Time: 2:35:53 PM User: PBTF\SvcMOSS Computer: CHINOOK Description: The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE ) 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: PBTF\SvcMOSS, [CLIENT: <named pipe>]. Event Type: Warning Event Source: Windows SharePoint Services 3 Search Event Category: Gatherer Event ID: 2436 Date: 5/13/2011 Time: 2:30:20 PM User: N/A Computer: CHINOOK Description: The start address <sts3://chinook:81/contentdbid={104a483a-6a73-4d6b-8a74-702fbc92a825}> cannot be crawled. Context: Application 'Search index file on the search server', Catalog 'Search' Details: Error in the Site Data Web Service. (0x80042616) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Can you help? thanks
May 13th, 2011 6:07pm

First, Can you make sure by navigation to central administration and determine whether the database is being used by any of the web applications? If you cannot find the web application that is accessing this particular content database, the only reason the content database might exist is because the web application was deleted without actually deleting the content database. You can delete the content database using Sql Server management studio. As another alternative, which I prefer, would be to a- Create New web application from central administartion. b- delete content database of your new web application. c- use stsadm command to add your old content database to your web application as the following:- stsadm -o addcontentdb -url http://portal -databasename youroldDB -databaseserver yourDBserver. This way, you would atleast know the data associated with the content database. Regarding the error, "Cannot open database "WSS_Content_81" requested by the login. The login failed. Login failed for user 'PBTF\SvcMOSS", you might want to assign 'PBTF\SvcMOSS' the necessary permissions to that particular user to access the database. The search might be trying to crawl the database which is resulting in this error. Hope this helps. V
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2011 10:54am

First, Can you make sure by navigation to central administration and determine whether the database is being used by any of the web applications? If you cannot find the web application that is accessing this particular content database, the only reason the content database might exist is because the web application was deleted without actually deleting the content database. You can delete the content database using Sql Server management studio. As another alternative, which I prefer, would be to a- Create New web application from central administartion. b- delete content database of your new web application. c- use stsadm command to add your old content database to your web application as the following:- stsadm -o addcontentdb -url http://portal -databasename youroldDB -databaseserver yourDBserver. This way, you would atleast know the data associated with the content database. Regarding the error, "Cannot open database "WSS_Content_81" requested by the login. The login failed. Login failed for user 'PBTF\SvcMOSS", you might want to assign 'PBTF\SvcMOSS' the necessary permissions to that particular user to access the database. The search might be trying to crawl the database which is resulting in this error. Hope this helps. V
May 15th, 2011 10:54am

Hi Doug Fir, From the description of this issue, it seems that it is related with your SQL server. For Event 3760, please make sure you are using the correct account. For detailed information about this, you can go through this article: http://technet.microsoft.com/zh-cn/library/cc561036(office.12).aspx, and this thread: http://social.msdn.microsoft.com/Forums/en/sharepoint2010general/thread/307ca64c-8944-4756-9dbe-8ae65efb1925. Event 18456 is the most unanimous when it comes to SQL server user rights. And moreover this error 18456 is a generic message and the state described with this error in sp_readerrorlog is important as that can be handy to track down the exact reason. You can go through these two articles, you will get a complete description and solution of the problems: http://www.eraofdata.com/blog/sql-18456-login-failures/; http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456/. Event 2436 occurs if text (.txt) files are blocked on the Blocked File Types page in SharePoint Server 2007. The gatherer is unable to access the Robots.txt file when it starts to crawl the specified URL. Please look into this KB article to get detailed information and solution of this problem: http://support.microsoft.com/kb/952172. Thanks & Regards, Peng Lei
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2011 11:35pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics