🚀 go-pugleaf

I'm sorry if this problem doesn't fit in this group as it covers a few
different areas...and sorry for the lengthy subject heading.

I've created a service application and a application to communicate with the
service via TServerSockets, when run from my development environment all is
good, I have no problems connecting to the service and sending and receiving
information.

When I then install the service and application using Installshield, I can
no longer make a successful socket connection.  I'm assuming that this has
something to do with how the service is installed, which I'm assuming is
installed under its own local system account and therefore is causing
problems for me.

I have noticed that when the installshield installs the service, I can start
and stop the service but I can't uninstall the service using /uninstall when
logged into the machine, it is this observation that makes me think that
there is a problem with permissions which is causing my socket connection to
not work.

Just to clarify, if I let installshield install the files but not install
the service application and I manually run "MyService /install", and then
run my application, it is able to communicate properly over sockets with the
service..  So the only difference is in how the service is installed.

I dont' beleive this is a installshield problem as I'm sure if I learned how
to use the api correctly I could reproduce the same thing by having the
service installed in its local system account rather than the account of the
logged in user - alternatively, I could reproduce this my installing the
service under one account and then trying to use it under a different
account

I realise I can get around this problem by having all users logging into the
machine under the same account that the service was installed under, but I'm
looking for a more robust solution that will allow any user account to run
the application and still have abilities to communicate with the service.

I also am not sure where the problem lies, whether its the application, the
socket connection with the service or the service itself...Can anyone help?