Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

Answered Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

  • Thursday, September 15, 2011 5:56 AM
     
     

    Hi All,

    I am using lync 2010 with sql express 2008. When i open my lync control panel i am getting a message saying unauthorized access. Previously everything was working fine, suddenly it started given this message and in the sql logs i found out the below eeor message

     

    Logon       Error: 18456, Severity: 14, State: 38.
    2011-09-14 17:08:39.34 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

     

    can anyone help me resolving this issue.

All Replies

  • Thursday, September 15, 2011 6:14 AM
     
     

    Hi, In event logs i see Event 2032, LS Master Replicator Agent Service and Event 1035, LS File Transfer Agent service.

     

    Under LS Master Replicator Agent Service details is as below

     

     -EventData Data Source = xxxx.xxxx.net\rtc; Database = xds; Max Pool Size = 5; Connection Timeout = 60; Connection Reset = false; Enlist = false; Integrated Security = true; Pooling = true;

     

     [-1] Could not connect to SQL server : [Exception=System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.Rtc.Common.Data.DBCore.PerformSprocContextExecution(SprocContext sprocContext)]

    • Edited by soudami Thursday, September 15, 2011 6:14 AM
    •  
  • Thursday, September 15, 2011 6:29 AM
    Moderator
     
     

    Seems that either the database xds is not there or the NETWORK SERVICE account does not have access to this database. Is there such a database and if yes are the permissions set accordingly ? Is the network service account configured in SQL Server Security and if yes, does it maybe have a default database that has been removed from his access or isn´t present at all anymore ? (Though that yield another state than 38)

    -Jens


    Jens K. Suessmeyer http://blogs.msdn.com/Jenss
  • Thursday, September 15, 2011 8:06 AM
     
     

    hi,

    Thanks for the reply... We didnt do any changes..as it is sql express it got installed automatically when we install the lync... so how do  we proceed to check n resolve this issue

  • Thursday, September 15, 2011 9:56 AM
     
     

    Hi,

    Thanks for the reply. I don't see any NT Authority/ Network Service user under security -> logins in sql server security..cn you help me to proceed further

  • Thursday, September 15, 2011 11:28 AM
    Moderator
     
     Answered

    Well, then add it with the appropriate permissions. if the account isn´t there (either individually or through any group membership) it doesn´t have any permissions to access the database unless granted to public.

    -Jens


    Jens K. Suessmeyer http://blogs.msdn.com/Jenss