0

The following error will occur in the event log after starting my Windows Server 2012 server with SharePoint 2013 (Farm installation, not stand-alone):

SQL Database 'SharePoint_Config' on SQL Server instance 'sp13dev' not found. Additional error information from SQL Server is included below.

Cannot open database "SharePoint_Config" requested by the login. The login failed. Login failed for user 'SP\sp_farm'.

Note: The server is intended for development purposes, so loosening security settings is ok.

'sp_farm' is a dedicated user account that is member of the following AD groups (local DC):

  • Administrators
  • Domain Admins
  • Domain Users
  • IIS_IUSRS
  • Performance monitors
  • WSS_ADMIN_WPG
  • WSS_RESTRICTED_WPG_V4
  • WSS_WPG groups

The user also has got public, dbcreator, securityadmin, serveradmin and sysadmin roles for the SQL server instance. The 'sp_farm' account was specified during the SharePoint configuration wizard, configuration was reported as successful by the wizard.

I know that are already more permissions than usually required, this was however done while trying to resolve the issue - without success.

An except from the diagnose log states the following:

12/09/2013 09:45:41.77  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        880j    High        SqlError: 'Cannot open database "SharePoint_Config" requested by the login. The login failed.'    Source: '.Net SqlClient Data Provider' Number: 4060 State: 1 Class: 11 Procedure: '' LineNumber: 65536 Server: 'sp13dev'   
12/09/2013 09:45:41.77  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        880j    High        SqlError: 'Login failed for user 'SP\sp_farm'.'    Source: '.Net SqlClient Data Provider' Number: 18456 State: 1 Class: 14 Procedure: '' LineNumber: 65536 Server: 'sp13dev'     
12/09/2013 09:45:41.78  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        3760    Critical    SQL Database 'SharePoint_Config' on SQL Server instance 'sp13dev' not found. Additional error information from SQL Server is included below.  Cannot open database "SharePoint_Config" requested by the login. The login failed.  Login failed for user 'SP\sp_farm'.    
12/09/2013 09:45:41.78  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        tzku    High        ConnectionString: 'Data Source=sp13dev;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15'    Partition: NULL ConnectionState: Closed ConnectionTimeout: 15   
12/09/2013 09:45:41.79  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        tzku    High        ConnectionString: 'Data Source=sp13dev;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15'    Partition: NULL ConnectionState: Closed ConnectionTimeout: 15   
12/09/2013 09:45:41.81  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        tzkv    High        SqlCommand: '              BEGIN TRY                  EXEC sp_executesql N'SELECT VersionId, Version FROM [dbo].[Versions] WITH (NOLOCK) ORDER BY VersionId, Id'              END TRY              BEGIN CATCH                  SELECT NULL, NULL              END CATCH              '     CommandType: Text CommandTimeout: 0     Parameter: '@Version' Type: NVarChar Size: 64 Direction: Output Value: ''    
12/09/2013 09:45:41.81  OWSTIMER.EXE (0x0974)                       0x0984  SharePoint Foundation           Database                        aek90   High        SecurityOnOperationCheck = False     

I logged on with the sp_farm user on the server and started the SQL Management Studio. Could connect to the SQL server without problems. Executed the query stated in the logs without problems.

I have then created a PowerShell script which connected to the SQL server using exactly the same ConnectionString as specified in the logs and using the SQL query from the logs. Without any problems.

Not sure what else I can do to solve this problem now - beside from resetting the VM and installing the whole thing again. :-(

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.