DependOnService does not work as expected

I have several services that retrieve their initialization
configuration from a database hosted on a SQL server express. All the
services have the SQL server defined in their DependOnService value in
the registry and should therefore not be launched until the SQL server
is ready to accept their connection. What I observe however is that
only a subset of the services is able to connect to the sql server,
and not even always the same subset.
I have tried to Google this problem but without success. Has no one
out there encountered this problem' If so, is there a solution to it?
Any ideas are welcome,
AriI seem to have found a solution: By pausing for 5seconds between
starting up my services they are all successful in connecting to the
database. The problem seems to be that SQL Server express is not able
to service 'simultaneous' logins.
/Ari
developari@.hotmail.com wrote:
> I have several services that retrieve their initialization
> configuration from a database hosted on a SQL server express. All the
> services have the SQL server defined in their DependOnService value in
> the registry and should therefore not be launched until the SQL server
> is ready to accept their connection. What I observe however is that
> only a subset of the services is able to connect to the sql server,
> and not even always the same subset.
> I have tried to Google this problem but without success. Has no one
> out there encountered this problem' If so, is there a solution to it?
> Any ideas are welcome,
> Ari|||<developari@.hotmail.com> wrote in message
news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
>I seem to have found a solution: By pausing for 5seconds between
> starting up my services they are all successful in connecting to the
> database. The problem seems to be that SQL Server express is not able
> to service 'simultaneous' logins.
>
More likely that SQL Server takes a few seconds to be ready to accept
connections, after the service starts up.
David|||Hi David,
It was my initial thought that the SQL Server had to wait some time
after the service started up before being able to accept connections.
But then I did some tests that dis-proved it: I tried waiting up to 5
minutes after the computer start-up before starting up the services
and then starting them up all in one go. This gave me the same
problems.
My conclusion is that the server is not able to accept such a rapid
succession of login-attempts.
Can you think of a better way of avoiding this problem then starting
up the services in a bat-file where I wait a few seconds between each
start-up?
/Ari
P.s. The SQL Server service is configured to start up automatically.
David Browne wrote:
> <developari@.hotmail.com> wrote in message
> news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
> >I seem to have found a solution: By pausing for 5seconds between
> > starting up my services they are all successful in connecting to the
> > database. The problem seems to be that SQL Server express is not able
> > to service 'simultaneous' logins.
> >
> More likely that SQL Server takes a few seconds to be ready to accept
> connections, after the service starts up.
> David