Application Pool trouble connecting database

On 13 Jul, 08:54, Jaap <jan.sonnem... DeleteThis @gmail.com> wrote:
> On 13 jul, 09:19, "Egbert Nierop \(MVP for IIS\)"
>
>
>
> <egbert_nie... DeleteThis @nospam.invalid> wrote:
> > "Jaap" <jan.sonnem... DeleteThis @gmail.com> wrote in message
>
> >news:1184306750.843593.313550@57g2000hsv.googlegroups.com...
>
> > > Sometimes when the W2003 is restarted the IIS applications cannot
> > > connected to MSSQL.
>
> > > When the Application Pool is manually stopped and again started the
> > > connection to MSSQL succeeds.
> > > (Recycle this Application Pool doesn't give this result.)
>
> > > I think this has to do with IIS requests from visitors during
> > > restarting with an IIS service started but the MSSQL is not yet ready.
> > > Via the Application Pool a MSSQL connection is being initiated, but
> > > failes. This state remaines until manual stop/start the pool.
>
> > Do you see errors in the SQL Server event log? (Such as out of a limitation
> > of connections?)
>
> NO errors or warnings found in the SQLServer log !

Are you running IIS and SQL on the same server? It might be case of
staggering the startup so that SQL starts first and IIS when complete.
 >> Stay informed about: Application Pool trouble connecting database 

"Jaap" <jan.sonnemans.DeleteThis@gmail.com> wrote in message
news:1184306750.843593.313550@57g2000hsv.googlegroups.com...
> Sometimes when the W2003 is restarted the IIS applications cannot
> connected to MSSQL.
>
> When the Application Pool is manually stopped and again started the
> connection to MSSQL succeeds.
> (Recycle this Application Pool doesn't give this result.)
>
> I think this has to do with IIS requests from visitors during
> restarting with an IIS service started but the MSSQL is not yet ready.
> Via the Application Pool a MSSQL connection is being initiated, but
> failes. This state remaines until manual stop/start the pool.

Do you see errors in the SQL Server event log? (Such as out of a limitation
of connections?)
 >> Stay informed about: Application Pool trouble connecting database 

On 13 jul, 12:22, grego <gregorei....TakeThisOut@gmail.com> wrote:
> On 13 Jul, 08:54, Jaap <jan.sonnem....TakeThisOut@gmail.com> wrote:
>
>
>
>
>
> > On 13 jul, 09:19, "Egbert Nierop \(MVP for IIS\)"
>
> > <egbert_nie....TakeThisOut@nospam.invalid> wrote:
> > > "Jaap" <jan.sonnem....TakeThisOut@gmail.com> wrote in message
>
> > >news:1184306750.843593.313550@57g2000hsv.googlegroups.com...
>
> > > > Sometimes when the W2003 is restarted the IIS applications cannot
> > > > connected to MSSQL.
>
> > > > When the Application Pool is manually stopped and again started the
> > > > connection to MSSQL succeeds.
> > > > (Recycle this Application Pool doesn't give this result.)
>
> > > > I think this has to do with IIS requests from visitors during
> > > > restarting with an IIS service started but the MSSQL is not yet ready.
> > > > Via the Application Pool a MSSQL connection is being initiated, but
> > > > failes. This state remaines until manual stop/start the pool.
>
> > > Do you see errors in the SQL Server event log? (Such as out of a limitation
> > > of connections?)
>
> > NO errors or warnings found in the SQLServer log !
>
> Are you running IIS and SQL on the same server? It might be case of
> staggering the startup so that SQL starts first and IIS when complete.- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -

Any idea how to arrange that IIS starts AFTER SQL has completed?
Or is it possible checking if there is a valid connection in the
Application Pool and if not then programmatically Stop and Restart
the Application pool?
 >> Stay informed about: Application Pool trouble connecting database 

On 13 Jul, 12:12, Jaap <jan.sonnem....RemoveThis@gmail.com> wrote:
> On 13 jul, 12:22, grego <gregorei....RemoveThis@gmail.com> wrote:
>
>
>
> > On 13 Jul, 08:54, Jaap <jan.sonnem....RemoveThis@gmail.com> wrote:
>
> > > On 13 jul, 09:19, "Egbert Nierop \(MVP for IIS\)"
>
> > > <egbert_nie....RemoveThis@nospam.invalid> wrote:
> > > > "Jaap" <jan.sonnem....RemoveThis@gmail.com> wrote in message
>
> > > >news:1184306750.843593.313550@57g2000hsv.googlegroups.com...
>
> > > > > Sometimes when the W2003 is restarted the IIS applications cannot
> > > > > connected to MSSQL.
>
> > > > > When the Application Pool is manually stopped and again started the
> > > > > connection to MSSQL succeeds.
> > > > > (Recycle this Application Pool doesn't give this result.)
>
> > > > > I think this has to do with IIS requests from visitors during
> > > > > restarting with an IIS service started but the MSSQL is not yet ready.
> > > > > Via the Application Pool a MSSQL connection is being initiated, but
> > > > > failes. This state remaines until manual stop/start the pool.
>
> > > > Do you see errors in the SQL Server event log? (Such as out of a limitation
> > > > of connections?)
>
> > > NO errors or warnings found in the SQLServer log !
>
> > Are you running IIS and SQL on the same server? It might be case of
> > staggering the startup so that SQL starts first and IIS when complete.- Tekst uit oorspronkelijk bericht niet weergeven -
>
> > - Tekst uit oorspronkelijk bericht weergeven -
>
> Any idea how to arrange that IIS starts AFTER SQL has completed?
> Or is it possible checking if there is a valid connection in the
> Application Pool and if not then programmatically Stop and Restart
> the Application pool?

Try changing the IIS Admin Service to be a dependancy of MSSQL serice.
That way, the load order will be so that SQL starts
before IIS admin. Or you could create a batch file thats executed that
will stop and start iis once the server has started. Another way
is to use a service like sitescope/servers alive or servervantage to
monitr your logs and detect such error...and add an action to restart
a
process/service.

Applications I work with handle a SQL crash and reconnect after its
restarted without an app pool refresh or recycle. I would seriously
ask your developers to look at this however.
 >> Stay informed about: Application Pool trouble connecting database