When logging in on a MOSS 2007 WFE-server to investigate a smaller issue, I noticed a wall of red errors in the event viewer. Most of them came down to something like:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 1111
Date: dd/mm/yyyy
Time: 1:00:00
User: N/A
Computer: SERVERNAME
Description:
SQL database login failed. Additional error information from SQL Server is included below.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
It was pretty clear that some SQL credentials weren’t correct, I just had to find out which ones. These are (part of) the errors I found in the SharePoint ULS logs:
DocAveAPVCService.exe (0x052C) 0x0D20 Windows SharePoint Services Database 880i High
System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
DocAveAPVCService.exe (0x052C) 0x0D20 Windows SharePoint Services Database 880j High
SqlError: 'Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.'
DocAveAPVCService.exe (0x052C) 0x0D20 Windows SharePoint Services Database 6y64 Critical
SQL database login failed. Additional error information from SQL Server is included below.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
A quick visit to the services control panel taught me that “AvePoint Communication Service” was running under the Local System credentials. This explains the failed login with ‘NT AUTHORITY\ANONYMOUS LOGON’ credentials in SQL Server on a different machine.
Solution
The solution is simple: run “AvePoint Communication Service” under (domain) credentials that have access to the SQL Server instance.
Edit: AvePoint seems to have a private patch available for this issue which you can receive after contacting them.