I'm running Windows Home Server for a while now and I really like it.
It's based upon Windows Server 2003 and normally you just administer it remotely with the Windows Home Server Console or Remote Desktop.
So it's usually just waiting there at the login screen and running only services.
Therefore I would like to be able to run UE as a service.
Currently it just shuts down immediately
It would be extra great if the UI could just be brought up once I log in but I could manage that myself by stopping the service, starting UE, ending it and running the service again.
Could you please look into that and let me know if it feasible ?
Running UE as a service
It is not free, but might this help?
http://run-exe-as-service.qarchive.org/
http://run-exe-as-service.qarchive.org/
I have already tried some programs that promised the gui like that.
I can also start it as a service using srvany from the Windows 2003 Resource Kit.
Problem is that it starts fine as a service when I'm logged on to the desktop.
But when it should start on computer bootup it just fails to and exits immediately
Thanks for your answer though !
I appreciate you thinking with me.
I can also start it as a service using srvany from the Windows 2003 Resource Kit.
Problem is that it starts fine as a service when I'm logged on to the desktop.
But when it should start on computer bootup it just fails to and exits immediately
Thanks for your answer though !
I appreciate you thinking with me.
Try http://www.firedaemon.com/ if you have not already.
It has extensive features to handle also software, which require interactive desktop to start properly.
Haven't tried myself, but I would be surprised if that couldn't get UE running as a service at boot with proper options.
Couple of caveats though:
1. UE is not designed to run as a service, and therefore when user logs off, UE will most likely stop too (however, firedaemon should have no problem in detecting this and restarting it in the backround again)
2. You may have problems with tray icons etc of UE (depending on if Alex has implemented tray icon handling correctly or not - many many software have this implemented "quickly" and you may lose the tray icons in many ways, including when run as service at boot).
3. It may be difficult to show the UE user interface after logon, but firedaemon has some options to alleviate this.
It has extensive features to handle also software, which require interactive desktop to start properly.
Haven't tried myself, but I would be surprised if that couldn't get UE running as a service at boot with proper options.
Couple of caveats though:
1. UE is not designed to run as a service, and therefore when user logs off, UE will most likely stop too (however, firedaemon should have no problem in detecting this and restarting it in the backround again)
2. You may have problems with tray icons etc of UE (depending on if Alex has implemented tray icon handling correctly or not - many many software have this implemented "quickly" and you may lose the tray icons in many ways, including when run as service at boot).
3. It may be difficult to show the UE user interface after logon, but firedaemon has some options to alleviate this.
Turning UE into a full-blown serviceable process would indeed take some work (main thing to consider would be to separate UI & core completely, so UI would only run on a user request and core as a service).
However, there are much simpler tasks to check to just make UE compatible with the myriad of 3rd party apps which can run arbitrary apps as a service:
Mainly, need to handle WM_QUERYENDSESSION and WM_ENDSESSION, so that UE doesn't unnecessarily shut down when user logs off (enabled via -service cmdline option, perhaps).
There probably isn't any need to actually disable tray-icon, (unless UE crashes due to it failing to bind when there's no interactive user). Moreso, UE should check if there is a systemtray to bind to and check periodically if there is a need to re-bind.
Those two considerations make most apps runnable as a service.
However, I have no interest in running UE as a service myself, so I haven't checked anything - those are just general requirements for an app to be runnable as a service. There may be other issues of course, depending on what the app expects from the running environment.
However, there are much simpler tasks to check to just make UE compatible with the myriad of 3rd party apps which can run arbitrary apps as a service:
Mainly, need to handle WM_QUERYENDSESSION and WM_ENDSESSION, so that UE doesn't unnecessarily shut down when user logs off (enabled via -service cmdline option, perhaps).
There probably isn't any need to actually disable tray-icon, (unless UE crashes due to it failing to bind when there's no interactive user). Moreso, UE should check if there is a systemtray to bind to and check periodically if there is a need to re-bind.
Those two considerations make most apps runnable as a service.
However, I have no interest in running UE as a service myself, so I haven't checked anything - those are just general requirements for an app to be runnable as a service. There may be other issues of course, depending on what the app expects from the running environment.
Thanks for all the replies guys !!
Actually it's not necessary for UE to become a full blown service.
Would be nice ofcourse but it's not the essence of my request.
I tried firedaemon and it behaves the same as srvany.
When I'm logged on to the desktop and try to start UE as a service using either srvany or firedaemon it start up and works perfectly.
But when the computer restarts and it should execute UE as a service both srvany and firedaemon fail.
I discovered this through the restart feature of firedaemon where it will just restart the executable if it's not responding.
In the event log I can see firedaemon trying to start UE and then a few seconds later there's the message that the process can't be found and tries to restart it again.
srvany just tries to start it once and then dies.
So there is something preventing UE to be run like this through these programs. I don't know what it is but I'm sure Alex has got a much better clue on this.
Whenever I want to see the UI I just stop the service. Then execute UE normally, do my managing like selecting posts to download and then quit UE again and start up the service again.
So it will just keep on downloading selected messages and getting the headers every 360 minutes like I've set it when it is being run as a service.
This is actually all I need.
A full blown service would indeed be nice but I reckon this will be major programming work.
Finding what prevents UE to be started without a desktop being present would be not that hard I guess.
Ofcourse UE should also keep running when the user logs off of the desktop.
I hope I made myself clear in what I need.
If not please ask
Actually it's not necessary for UE to become a full blown service.
Would be nice ofcourse but it's not the essence of my request.
I tried firedaemon and it behaves the same as srvany.
When I'm logged on to the desktop and try to start UE as a service using either srvany or firedaemon it start up and works perfectly.
But when the computer restarts and it should execute UE as a service both srvany and firedaemon fail.
I discovered this through the restart feature of firedaemon where it will just restart the executable if it's not responding.
In the event log I can see firedaemon trying to start UE and then a few seconds later there's the message that the process can't be found and tries to restart it again.
srvany just tries to start it once and then dies.
So there is something preventing UE to be run like this through these programs. I don't know what it is but I'm sure Alex has got a much better clue on this.
Whenever I want to see the UI I just stop the service. Then execute UE normally, do my managing like selecting posts to download and then quit UE again and start up the service again.
So it will just keep on downloading selected messages and getting the headers every 360 minutes like I've set it when it is being run as a service.
This is actually all I need.
A full blown service would indeed be nice but I reckon this will be major programming work.
Finding what prevents UE to be started without a desktop being present would be not that hard I guess.
Ofcourse UE should also keep running when the user logs off of the desktop.
I hope I made myself clear in what I need.
If not please ask
Ah, there seems to be some dependency in UE that prevents it from starting up when interactive desktop is not available.Michaelm wrote: When I'm logged on to the desktop and try to start UE as a service using either srvany or firedaemon it start up and works perfectly.
...
But when the computer restarts and it should execute UE as a service both srvany and firedaemon fail.
...
In the event log I can see firedaemon trying to start UE and then a few seconds later there's the message that the process can't be found and tries to restart it again.
Did you try disabling UE "tray icon"? (it may crash if trying to bind in non-existent system tray)
If that does not help, Alex probably has some ideas and can do something about it.
Also, have you checked UE logs if they might indicate what went wrong?
My suspicion is that there simply is some UI dependent code which does not fail gracefully when desktop is not available and throws an exception which is not caught & handled. Most likely something trivial which Alex could circumvent.