service start fails on XP embedded

[riddler]

Hi,

I have written a service that starts on XP Pro but fails to start on
startup on XP embedded.

When i add a mapped network drive, the service starts on startup.
However my service has nothing to do with a mapped network drive.

When the system is fully started, the service starts also.

I have tried to solve the problem by adding dependencies on my service
without succes.

When i boot and i go to the services, I see my service as starting.

I get an Event ID 7009 and Event ID 7000 from service control manager.

 

[henry markov]

When you componetized the service did you expand "Resources" and then open
and complete the "Service Data?" If so perhaps you can state the field
values you used.

HM

 

[riddler]

When you componetized the service did you expand "Resources" and then open
and complete the "Service Data?"  If so perhaps you can state the field
values you used.

HM

I haven't made a component of it yet.
I install it manual after FBA for the moment.

 

[Francesco Gigante]

Try this test:

wait 30 seconds before login by user and password: if your service can
start when you wait to login, then you have my same problem. I solved
it by writing a service without "interact with desktop" properties and
I handled the starting of my others services by it.
I don't know XPe has this strange behavior... Do someone know?

 

[riddler]

Try this test:

wait 30 seconds before login by user and password: if your service can
start when you wait to login, then you have my same problem. I solved
it by writing a service without "interact with desktop" properties and
I handled the starting of my others services by it.
I don't know XPe has this strange behavior... Do someone know?

So if i am reading this right, you say that i have to make a service
that starts my service?
Because i can't go without "interact with desktop".
I did the test and it is indeed the behaviour that you describe:
wait 30s to login and then the service starts.
if i autologin, my service keeps hanging in starting before failing to
start.

 

[Francesco Gigante]

Yes, you need to make a very simple windows service who can work
without "interact with desktop"
and set it as automatic start: this service must start your real
service: the important thing is that
it must wait about 30-45 seconds before trying to start your real
service! (This is very important)

Set your application service as manual start and let it start by the
simple service.
I cannot find any other more simple solution... I try with
dependencies as you did, but without success me too.
Now the solution with master and slave services works well for me.

I think this behaviour is due to some strange handling of the network
by XPE. But I'm not sure about that.
If someone could explain us why XPE has this behaviour, it would be
very appreciated by me!

Regards,

Francesco Gigante

 

[riddler]

Do you also lose the problem if you add a netwerk map(it doesn't have
to exist)?
I made a similar workaround but those 40s shouldn't be there.

If someone could explain us why XPE has this behaviour, it would be
very appreciated by me!

I second that motion