SQL Access to Database Denied every hour when "SharePoint Services Search Refresh" Timer Job runs

Question

Issue: Every hour when the "SharePoint Services Search Refresh" Timer job runs it gives this error on all four servers in the farm. Can anyone tell me
what access i need to grant to the Domain\Server$ account in SQL and to which databases it is trying to access.
It has access to the two Config databases and since i thought it was MOSS Search related i granted access to the two SSP databases. That didn't seem to stop the issue.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3351
Date:  11/3/2009
Time:  11:34:15 AM
User:  N/A
Computer: ServerName
Description:
SQL database login failed. Additional error information from SQL Server is included below.

Login failed for user 'DOMIAN\SERVER$'.


Environment: 5 server farm (two front-end webs [querying running on both], two application servers [one is running both wss search and indexing], and on SQL Server)
The four SharePoint servers all have this problem.

Answer 1

Maybe you can find some database named like "_Search_DB", check the users in these dbs.

Answer 2

Hi,

Please check if this article from MSDN helps:
http://technet.microsoft.com/en-us/library/cc561068.aspx

---

Xue-Mei Chang

Answer 3

Gave user account 'DOMIAN\SERVER$ db_owner rights  to all databases and it didn't fix it. Also followed the above article and ensured that all service accounts are able to access the database, which they are and still i get this error every couple of minutes on the two front-end web servers and the two application servers.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3351
Date:  11/3/2009
Time:  11:34:15 AM
User:  N/A
Computer: ServerName
Description:
SQL database login failed. Additional error information from SQL Server is included below.

Login failed for user 'DOMIAN\SERVER$'.

Any other ideas?

Answer 4

Ok now this is wierd, I have two front-end web servers and two application servers. One of the Front-end web stopped throwing these error on 11/5/2009. We haven't changed anything on the system. The other three still record the above error every few minutes. Checked SQL permissions and they are exactly the same for all four server accounts (DOMAIN\SERVER$). Any ideas?

These are highly managed production servers that do not have internat access so Microsoft updates are scheduled and applied throughout the enviroment buy our support team.