SP2010- Event 3760, SharePoint Foundation
I keep on receiving this error message in the application logs and I dont know how to resolve it. Can someone please help me?? Thanks!
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 8/5/2011 4:00:03 PM
Event ID: 3760
Task Category: Database
Level: Critical
Keywords:
User: SDI\_ps20
Computer: sharepoint.test.org
Description:
SQL Database 'Search_Service_Applicatio
Cannot open database "Search_Service_Applicatio
Login failed for user 'SDI\_ps20'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint
<EventID>3760</EventID>
<Version>14</Version>
<Level>1</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x40000000000000
<TimeCreated SystemTime="2011-08-05T20:
<EventRecordID>335909</Eve
<Correlation ActivityID="{D660E4FF-630A
<Execution ProcessID="3780" ThreadID="1892" />
<Channel>Application</Chan
<Computer>sharepoint.test.
<Security UserID="S-1-5-21-400213411
</System>
<EventData>
<Data Name="string0">Search_Serv
<Data Name="string1">SQLDATA</Da
<Data Name="string2">Cannot open database "Search_Service_Applicatio
Login failed for user 'SDI\_ps20'.</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 8/5/2011 4:00:03 PM
Event ID: 3760
Task Category: Database
Level: Critical
Keywords:
User: SDI\_ps20
Computer: sharepoint.test.org
Description:
SQL Database 'Search_Service_Applicatio
Cannot open database "Search_Service_Applicatio
Login failed for user 'SDI\_ps20'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint
<EventID>3760</EventID>
<Version>14</Version>
<Level>1</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x40000000000000
<TimeCreated SystemTime="2011-08-05T20:
<EventRecordID>335909</Eve
<Correlation ActivityID="{D660E4FF-630A
<Execution ProcessID="3780" ThreadID="1892" />
<Channel>Application</Chan
<Computer>sharepoint.test.
<Security UserID="S-1-5-21-400213411
</System>
<EventData>
<Data Name="string0">Search_Serv
<Data Name="string1">SQLDATA</Da
<Data Name="string2">Cannot open database "Search_Service_Applicatio
Login failed for user 'SDI\_ps20'.</Data>
</EventData>
</Event>
ASKER
Yes I understand that. However this database is not on the SQL server and the database that is currently running for the search crawlDB is a different name. How do I fix this error so it doesn't keep showing up? It looks like it sees two search service applications but there is only one in SharePoint.
detach the Search_Service_Application
ASKER
What if you cant detach the database due to the database could not be found on the database instance in the farm.
ASKER
I re-created the database on the default SQL server but I still cant detach the database. The error stops because the database is live now BUT it is a database that isnt being used by search service. It is like there is a phantom search service application.
I recall having a similar issue with login failures when the SSP was recreated
Go to SQL Server Management Studio -> SQL Server Agent -> Jobs
Disable the jobs that have the DBNAME_JobDeleteExpiredSes
Check if the login errors persist
Go to SQL Server Management Studio -> SQL Server Agent -> Jobs
Disable the jobs that have the DBNAME_JobDeleteExpiredSes
Check if the login errors persist
ASKER
I actually have a MS Tech involved with this. Tried restoring this DB and was still not able to get rid of the DB because the Search Application is not there. It looks like I will need to get into the actual SharePoint Config DB to see if it is possible to delete the reference to the DB.
ASKER
Still working with the MS Tech....
Not sure if this will help, but I had a similar issue this morning. Our SharePoint Foundation site would not come up and I was seeing this same Event ID error in our logs. This worked for me:
1. If the WSS is in a server farm, use the “SharePoint Products and Technologies Configuration Wizard” to disconnect the server from the farm.
2. go to Start >Program > Microsoft SQL Server 2005 > Configuration Tools >SQL Server Configuration Manager
3. Navigate to SQL Server 2005 Network Configuration > Protocol for MSSQLSERVER
4. Right click Named Pipes and select Enable (if not enabled)
5. Restart SQL Server
6. Join back the server to server farm using “SharePoint Products and Technologies Configuration Wizard” and follow the wizards.
Note: If the installation is a stand-alone installation, then you don’t need to worry about steps 1 & 6
Taken from: http://blog.rojakstyle.com/?p=480
1. If the WSS is in a server farm, use the “SharePoint Products and Technologies Configuration Wizard” to disconnect the server from the farm.
2. go to Start >Program > Microsoft SQL Server 2005 > Configuration Tools >SQL Server Configuration Manager
3. Navigate to SQL Server 2005 Network Configuration > Protocol for MSSQLSERVER
4. Right click Named Pipes and select Enable (if not enabled)
5. Restart SQL Server
6. Join back the server to server farm using “SharePoint Products and Technologies Configuration Wizard” and follow the wizards.
Note: If the installation is a stand-alone installation, then you don’t need to worry about steps 1 & 6
Taken from: http://blog.rojakstyle.com/?p=480
ASKER
Well the Search Application 'was' running on one machine but I reconfigured it to be on another machine instead. The SQL server is a different machine. So there is a mix of this machines.
SharePoint Server, Search Application Server, Database Server.
Are you saying to disconnect the SharePoint server from the FARM then run the SQL steps on the SQL Server, then add the SharePoint Server back to the FARM?
SharePoint Server, Search Application Server, Database Server.
Are you saying to disconnect the SharePoint server from the FARM then run the SQL steps on the SQL Server, then add the SharePoint Server back to the FARM?
I only have one SharePoint server and a separate SQL server. It sounds very similar to your setup minus the search server. I did not follow steps 1 and 6. I ...
- Did the work on the SQL server, enabling the Named Pipes
- Restarted the SQL service (and agent service)
- Then on the SharePoint server I did an IISRESET from a command line
After that my SPF site was back up and running. Also, other applications that rely on SQL seemed to get happier too after this. I'm not exactly sure what happened in our environment to cause this. I did some work last night swapping out our SAN device and I had to rejoin the SQL server using the iSCSI Initiator tool. That all went fine and I rebooted the server just to be safe. Still, it was barking at me until I made the change suggested above.
Good luck. Let us know.
- Did the work on the SQL server, enabling the Named Pipes
- Restarted the SQL service (and agent service)
- Then on the SharePoint server I did an IISRESET from a command line
After that my SPF site was back up and running. Also, other applications that rely on SQL seemed to get happier too after this. I'm not exactly sure what happened in our environment to cause this. I did some work last night swapping out our SAN device and I had to rejoin the SQL server using the iSCSI Initiator tool. That all went fine and I rebooted the server just to be safe. Still, it was barking at me until I made the change suggested above.
Good luck. Let us know.
ASKER
Thanks for that information. I may try it out, what do I got to lose.
In my case, the DBs are not there because the Search Application is on a new machine with new DBs. The old DBs have since been deleted HOWEVER SharePoint sitll sees the old DBs and Im having the hardest time trying to get SharePoint to stop seeing them.
In my case, the DBs are not there because the Search Application is on a new machine with new DBs. The old DBs have since been deleted HOWEVER SharePoint sitll sees the old DBs and Im having the hardest time trying to get SharePoint to stop seeing them.
ASKER
Well scratch that idea ... Named Pipes was already enabled and I have done MULTIPLE iisresets since this issue started. Im pretty sure my SQL machine has been restarted since then too but I honestly have forgotten. It is a machine that doesnt really need to be rebooted often.
It was worth a shot. For what it worth, I've found SPF (and past versions of SharePoint) to be a beast to manage. Very complicated with configs, terminology, etc. Good luck.
ASKER
I agree, thanks for the info though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had to consult Microsoft to solve the issue.
Cannot open database "Search_Service_Applicatio
Login failed for user 'SDI\_ps20'.