Respondida Services getting disabled

  • sexta-feira, 16 de março de 2012 06:31
     
     

    frnds,

    services in sevices.msc related to appfabric are getting disabled .. i have set the start up type as "Automatic" .. even then i found they are getting disabled after some time(may b a day..)

    do i need to set up some thing to avoid this problem..need some help guys..

Todas as Respostas

  • sexta-feira, 16 de março de 2012 20:00
     
     

    Is it the caching service ? You should ideally not be starting the caching service via SVC but via powershell cmdlets.

    Please look at eventvwr to see why the service stopped/crashed (I assume it stops automatically)

  • sábado, 17 de março de 2012 08:16
     
     

    i checked eventvwr i see the error with connecting to sql-server which caused to crash appfabric.. i feel that this is caused while connecting to sql-server,which is is another remote server.. is this causing the appfabric services to get disabled.. please help me in knowing this ..

  • sábado, 17 de março de 2012 15:00
     
     
    Can you paste the error and call stack here.
  • segunda-feira, 19 de março de 2012 04:46
     
     

    this is the error :

    AppFabric Caching service crashed.{Lease with external store expired: Microsoft.Fabric.Federation.ExternalRingStateStoreException: Renew lease failed ---> Microsoft.Fabric.Data.ExternalStoreException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> Microsoft.ApplicationServer.Caching.ConfigStoreException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

  • segunda-feira, 19 de março de 2012 14:12
     
     

    Service crash is definitely due to the SQL availability issues, I am not sure if this (the crash) causes service to get disabled also. Also always start the cluster using the start-cachecluster cmdlet

    How many nodes are there in your cluster ? Seeing these issues, you may want to consider seed node onloading (for 3 or more nodes)  instead of letting SQL do cluster management.


  • terça-feira, 20 de março de 2012 04:41
     
     

    there is a single node in my cluster, i tried to add this to distributedcache.exe (config file)

      <fabric>
        <key name="ExternalRingStateUpdateTimeout" value="360" />
      </fabric>

    and in recovery tab of my services i changed the "resetfailcount" days to 0  .. and "resetserviceafter" 0 minutes..

    i see that my services are not getting disabled..

    but in my events there is log entered  20 times in 15 mts... there 2 different errors like below,

    is this a right approach or u suggest any thg..

    AppFabric Caching service crashed with exception {Microsoft.ApplicationServer.Caching.ConfigStoreException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, 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.ApplicationServer.Caching.SqlServerCustomProvider.BeginTransaction()
       --- End of inner exception stack trace ---
       at Microsoft.ApplicationServer.Caching.SqlServerCustomProvider.BeginTransaction()
       at Microsoft.ApplicationServer.Caching.ClusterConfigDictionaryReader.GetConfigs[T](String type)
       at Microsoft.ApplicationServer.Caching.ServiceConfigurationManager.InitializeHostsData(IClusterConfigurationReader globalConfig)
       at Microsoft.ApplicationServer.Caching.ServiceConfigurationManager.InitializeDataFromGlobalConfig()
       at Microsoft.ApplicationServer.Caching.VelocityWindowsService.StartService(Boolean deleteTKT)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()}. Check debug log for more information

    AppFabric Caching service crashed with exception {Microsoft.ApplicationServer.Caching.ConfigStoreException: Cannot open database "AppServer_Local" requested by the login. The login failed.
    Login failed for user 'VALUEMOMENTUM\VAMSEZ218$'. ---> System.Data.SqlClient.SqlException: Cannot open database "AppServer_Local" requested by the login. The login failed.
    Login failed for user 'VALUEMOMENTUM\VAMSEZ218$'.
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, 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.ApplicationServer.Caching.SqlServerCustomProvider.BeginTransaction()
       --- End of inner exception stack trace ---
       at Microsoft.ApplicationServer.Caching.SqlServerCustomProvider.BeginTransaction()
       at Microsoft.ApplicationServer.Caching.ClusterConfigDictionaryReader.GetConfigs[T](String type)
       at Microsoft.ApplicationServer.Caching.ServiceConfigurationManager.InitializeHostsData(IClusterConfigurationReader globalConfig)
       at Microsoft.ApplicationServer.Caching.ServiceConfigurationManager.InitializeDataFromGlobalConfig()
       at Microsoft.ApplicationServer.Caching.VelocityWindowsService.StartService(Boolean deleteTKT)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()}. Check debug log for more information

  • terça-feira, 20 de março de 2012 19:56
     
     

    Your cache cluster is not going to be of much help if SQL is down or inaccessible.

    You can use powershell cmdlets to confirm connectivity to the provider store, you can even write a script to do it periodically. The access denied error to the SQL DB shouldnt come, did you face any issues while configuring the service on SQL ? Did you use the GUI or the command line tool ?

  • quinta-feira, 22 de março de 2012 07:20
     
     

    no i didjnt face any issues while configuring the service on SQL, i have used command line tool..

    and how can i confirm the connectivity through powersheel..

    now my services are not getting disabled , as i have mentioned above im getting the error logged in evevts 20 times in 15 mts of time span in a day..

    any help in overcoming that, the error was the same that i have mentioned above..

  • quinta-feira, 22 de março de 2012 17:33
     
     Respondido

    The reason for disabling of cache service could very well be the SQL connectivity issues causing appfabric to crash continuously.

    Could you try and use xml provider as config store and verify if you still hit this issue ?

    • Marcado como Resposta Kumar's terça-feira, 27 de março de 2012 06:51
    •  
  • terça-feira, 27 de março de 2012 06:51
     
     

    sure ankit i will try  with xml provider..