Not quite a shameless bump, but close enough...
I have since attempted to work around this problem by adding:
depends= "TermService"
to the command to create the service using sc.exe
Terminal Service is one of the services that shows up deep in the service dependency tree, so I was hoping that by making my service dependent on that, the node agent would start up towards the end and avoid the port already in use exception...
Sadly, my problem persists.
Any help would be deeply appreciated. Anyone familiar enough with windows services that might point me towards starting up my service when a particular user logs into the machine would be very helpful at this point...not sure if it's possible though.
Thanks alot for any input!
John
[Message sent by forum member 'jstalker' (jstalker)]
http://forums.java.net/jive/thread.jspa?messageID=360142