I have a Standalone Application (Indy) that runs fine when compiled as an application but when compiled as a service (TIWStart.Execute(False); ) the service starts, the IWServerControllerBaseConfig runs and exits, the IWServerControllerBaseCreate runs and exits. There are timers on the form and they run and execute, but the Service never shows in the service manager as Running, only sits at Starting, and browser connections cannot be made to the service. Any ideas? What has to finish for the service to be "started"?
BTW, This was an update to a service that has been in operational use for 5 years. It is to be version 2.3 but this is the first time I have had this issue. I made updates but can't figure out what could be causing it - and when I disable some changes or replace the items with what was used before it still happens. I can compile version 2.2 with the new Intraweb and it runs as a service fine, so it isn't an Intraweb issue. I just don't know what to look for that would cause it to not tell Windows it was loaded but that doesn't cause an issue when compiled and run as an app.
Thanks
David
BTW, This was an update to a service that has been in operational use for 5 years. It is to be version 2.3 but this is the first time I have had this issue. I made updates but can't figure out what could be causing it - and when I disable some changes or replace the items with what was used before it still happens. I can compile version 2.2 with the new Intraweb and it runs as a service fine, so it isn't an Intraweb issue. I just don't know what to look for that would cause it to not tell Windows it was loaded but that doesn't cause an issue when compiled and run as an app.
Thanks
David