Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1097639" data-attributes="member: 82144">[USER=27598]@mrkaras[/USER]In your log files I can see three occasions where the TV service starts successfully:<ul>
<li data-xf-list-type="ul">2014-08-25 19:26:56,557</li>
<li data-xf-list-type="ul">2014-08-26 05:13:54,265</li>
<li data-xf-list-type="ul">2014-08-26 19:00:04,962</li>
</ul>I can't tell for sure whether these are automatic or manual starts, but on all three occasions the successful start is immediately preceded by a failed attempt... so I guess they're manual starts.In the TV Server log the failures looks like this:When I compare with the application event logs I see the following sequence...1. Windows tells the SQL Server service to start:&quot;26/08/2014 6:52:26 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Server&quot;;&quot;Information&quot;;&quot;Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)&nbsp;&nbsp; Mar 29 2009 10:11:52&nbsp;&nbsp; Copyright (c) 1988-2008 Microsoft Corporation&nbsp;&nbsp; Express Edition (64-bit) on Windows NT 6.1 &lt;X64&gt; (Build 7601: Service Pack 1)&quot;;&quot;1073758893&quot;2. SQL Server reports it is ready for connections. Presumably the SQL Server service tells Windows it has finished starting at this point:&quot;26/08/2014 6:52:29 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Server&quot;;&quot;Information&quot;;&quot;Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].&quot;;&quot;1073767872&quot;&quot;26/08/2014 6:52:29 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Server&quot;;&quot;Information&quot;;&quot;Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].&quot;;&quot;1073767872&quot;3. Windows tells the TV Server service to start:[2014-08-26 18:52:29,052] [Log&nbsp; ] [4&nbsp; ] [DEBUG] - Setting up EventWaitHandle with name: Global\MPTVServiceInitializedEvent4. SQL Server reports login failure:&quot;26/08/2014 6:52:30 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Logon&quot;;&quot;FailureAudit&quot;;&quot;Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: &lt;local machine&gt;]&quot;;&quot;3221243928&quot;&quot;26/08/2014 6:52:31 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Logon&quot;;&quot;FailureAudit&quot;;&quot;Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: &lt;local machine&gt;]&quot;;&quot;3221243928&quot;5. TV Server fails to start:&quot;26/08/2014 6:52:35 PM&quot;;&quot;TV Server&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;Service cannot be started. Error: DatabaseUnavailableUnclassified Gentle.Common.GentleException: The database backend (provider SQLServer) could not be reached. Check the connection string: Password=***;Persist Security Info=True;User ID=sa;Initial Catalog=MpTvDb;Data Source=Mediaserver\SQLEXPRESS;Connection Timeout=30; ---&gt; System.Data.SqlClient.SqlException: Cannot open database &quot;MpTvDb&quot; requested by the login. The login failed. Login failed for user 'sa'.&nbsp; at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)&nbsp; at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)&nbsp; at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)&nbsp; at System.Data.SqlClient.SqlConnection.Open()&nbsp; at Gentle.Provider.SQLServer.SQLServerProvider.GetConnection()&nbsp; --- End of inner exception stack trace ---&nbsp; at Gentle.Common.Check.FailWith(Severity severity, Error error, Exception e, String ...&quot;;&quot;0&quot;6. SQL Server reports it has loaded the TV Server database:&quot;26/08/2014 7:00:05 PM&quot;;&quot;MSSQL$SQLEXPRESS&quot;;&quot;Server&quot;;&quot;Information&quot;;&quot;Starting up database 'MpTvDb'.&quot;;&quot;1073758961&quot;7. You manually start TV Server successfully:&quot;26/08/2014 7:00:11 PM&quot;;&quot;TV Server&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Service started successfully.&quot;;&quot;0&quot;So, in short it appears like the problem is that SQL Server is saying it can accept connections before it has loaded the TV Server database... which results in TV Server's attempts to connect to its database being rejected. To me SQL Server's behaviour seems illogical, and I'm not sure that there is much TV Server can do about this.In answer to your questions:Services are started by Windows.Windows starts a given service when all pre-requisite services for the service have successfully started.When TV Server is installed and configured, it registers the TV service and includes a pre-requisite reference to the SQL Server service (or MySQL service - depending on what database engine you choose) that you configure.What I'm trying to say with the above statements is:<ol>
<li data-xf-list-type="ol">It is not the TV service's responsibility to wait for SQL Server. Windows manages when services are started. 
</li>
<li data-xf-list-type="ol">Windows should already be configured to wait for the SQL Server service to finish starting before attempting to start the TV service.</li>
</ol>On the second point: the application event logs appear to show Windows is indeed waiting until the SQL Server service is started before attempting to start the TV service. The question is why SQL Server is saying it is ready for connections when clearly it is not able to accept TV Server's connection attempt... and I'm not able to answer that.Sorry but you're going to need to be more precise - like &quot;the 26th at 7:26pm&quot;. &quot;Yesterday&quot; at the time you wrote that could be the 25th, 26th or 27th for all I know, especially considering I don't know what time zone you're in.No, not common as far as I know.No, the TV service is not crashing SQL Server.</blockquote>

[QUOTE="mm1352000, post: 1097639, member: 82144"] [USER=27598]@mrkaras[/USER] In your log files I can see three occasions where the TV service starts successfully: [LIST] [*]2014-08-25 19:26:56,557 [*]2014-08-26 05:13:54,265 [*]2014-08-26 19:00:04,962 [/LIST] I can't tell for sure whether these are automatic or manual starts, but on all three occasions the successful start is immediately preceded by a failed attempt... so I guess they're manual starts. In the TV Server log the failures looks like this: When I compare with the application event logs I see the following sequence... 1. Windows tells the SQL Server service to start: "26/08/2014 6:52:26 PM";"MSSQL$SQLEXPRESS";"Server";"Information";"Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) ";"1073758893" 2. SQL Server reports it is ready for connections. Presumably the SQL Server service tells Windows it has finished starting at this point: "26/08/2014 6:52:29 PM";"MSSQL$SQLEXPRESS";"Server";"Information";"Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].";"1073767872" "26/08/2014 6:52:29 PM";"MSSQL$SQLEXPRESS";"Server";"Information";"Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].";"1073767872" 3. Windows tells the TV Server service to start: [2014-08-26 18:52:29,052] [Log ] [4 ] [DEBUG] - Setting up EventWaitHandle with name: Global\MPTVServiceInitializedEvent 4. SQL Server reports login failure: "26/08/2014 6:52:30 PM";"MSSQL$SQLEXPRESS";"Logon";"FailureAudit";"Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]";"3221243928" "26/08/2014 6:52:31 PM";"MSSQL$SQLEXPRESS";"Logon";"FailureAudit";"Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]";"3221243928" 5. TV Server fails to start: "26/08/2014 6:52:35 PM";"TV Server";"(0)";"Error";"Service cannot be started. Error: DatabaseUnavailableUnclassified Gentle.Common.GentleException: The database backend (provider SQLServer) could not be reached. Check the connection string: Password=***;Persist Security Info=True;User ID=sa;Initial Catalog=MpTvDb;Data Source=Mediaserver\SQLEXPRESS;Connection Timeout=30; ---> System.Data.SqlClient.SqlException: Cannot open database "MpTvDb" requested by the login. The login failed. Login failed for user 'sa'. 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 Gentle.Provider.SQLServer.SQLServerProvider.GetConnection() --- End of inner exception stack trace --- at Gentle.Common.Check.FailWith(Severity severity, Error error, Exception e, String ...";"0" 6. SQL Server reports it has loaded the TV Server database: "26/08/2014 7:00:05 PM";"MSSQL$SQLEXPRESS";"Server";"Information";"Starting up database 'MpTvDb'.";"1073758961" 7. You manually start TV Server successfully: "26/08/2014 7:00:11 PM";"TV Server";"(0)";"Information";"Service started successfully.";"0" So, in short it appears like the problem is that SQL Server is saying it can accept connections before it has loaded the TV Server database... which results in TV Server's attempts to connect to its database being rejected. To me SQL Server's behaviour seems illogical, and I'm not sure that there is much TV Server can do about this. In answer to your questions: Services are started by Windows. Windows starts a given service when all pre-requisite services for the service have successfully started. When TV Server is installed and configured, it registers the TV service and includes a pre-requisite reference to the SQL Server service (or MySQL service - depending on what database engine you choose) that you configure. What I'm trying to say with the above statements is: [LIST=1] [*]It is not the TV service's responsibility to wait for SQL Server. Windows manages when services are started. [*]Windows should already be configured to wait for the SQL Server service to finish starting before attempting to start the TV service. [/LIST] On the second point: the application event logs appear to show Windows is indeed waiting until the SQL Server service is started before attempting to start the TV service. The question is why SQL Server is saying it is ready for connections when clearly it is not able to accept TV Server's connection attempt... and I'm not able to answer that. Sorry but you're going to need to be more precise - like "the 26th at 7:26pm". "Yesterday" at the time you wrote that could be the 25th, 26th or 27th for all I know, especially considering I don't know what time zone you're in. No, not common as far as I know. No, the TV service is not crashing SQL Server. [/QUOTE]

Verification