I'm using InstallAware 6.1 Studio.
We have an executable that we're installing into $TARGETDIR$ that needs to be installed as a service and then started.
We can't seem to figure out how to make this work from the Services section, using Install Service. It asks for a Service entry point file, but every combination we use apparently doesn't work.
Since it doesn't accept variables in the Service File name, I assumed we'd select the source file from our local computer which it would pull from and place in the distribution. But when the installer runs, it has some error and lengthy file name it appears to be trying to pull from. So then we removed the path and just put the name of the EXE file - nope.
Since our file is not yet installed on the computer, how can we facilitate this? Can it be performed using the simple dialogs in the editor, or are we going to have to write script?
Any help would be appreciated.
Basically we want to install our EXE called MyService.exe into $TARGETDIR$ (not sure if it should be in Files also, but have tried both ways), and after we put the file on the user's disk at $TARGETDIR$, we want to install that EXE as a Service and start it - seems simple enough.
What are we doing wrong?
(PS - docs are terrible regarding this, and no examples, very frustrating)
Installing Service...
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Really..
What would have helped would be that your manual actually explained what you expect for the Service entry point file to be, not to mention whether or not the same EXE file should be included in the Files section. It doesn't.
Instead of asking for screenshots, you could have spent your time simply answering the simple question we posed - what should a paid customer of your product place in that field and how does your software handle it for the service installation process.
Instead of asking for screenshots, you could have spent your time simply answering the simple question we posed - what should a paid customer of your product place in that field and how does your software handle it for the service installation process.
-
vincemcc00
- Posts: 5
- Joined: Fri Jul 13, 2007 9:12 am
-
Bo Andersen
- Posts: 33
- Joined: Mon Jul 16, 2007 5:07 am
- Location: Denmark
Still stuck
Any solutions to this issue? What the heck is supposed to go into that field? Are there any docs or posts that walk you through installing a service using InstallAware?
I had the exact same problem, and have a solution
I had an "Install File" command (so I could get my service exe installed onto the target pc), followed by an "Install Service" command so the service was 'installed' into Windows.
I deleted the "Install File" command, so there was only the "Install Service" command, and the service successfully installed!
When I build my install, IA says it has "copied service MyService.exe" into the build. The "Install service" command must implicitly copy the file from your local PC into the 'target folder'.
That's what the entry point file must mean.
It is a shame that the documentation couldn't have mentioned that "install service" also performs an implicit "install file"
Edit: I understand more now. Reading the "install service" dialog carefully, I noticed that the second field on the first tab is 'install folder'. The reason you can't do an "install file" and and "install service" is (presumably) because the "install service" goes to copy the file in but finds it is already there. Maybe the file is locked and so the implicit copy from the "install service" fails, and so the rest of the "install service" command doesn't run.
I had an "Install File" command (so I could get my service exe installed onto the target pc), followed by an "Install Service" command so the service was 'installed' into Windows.
I deleted the "Install File" command, so there was only the "Install Service" command, and the service successfully installed!
When I build my install, IA says it has "copied service MyService.exe" into the build. The "Install service" command must implicitly copy the file from your local PC into the 'target folder'.
That's what the entry point file must mean.
It is a shame that the documentation couldn't have mentioned that "install service" also performs an implicit "install file"
Edit: I understand more now. Reading the "install service" dialog carefully, I noticed that the second field on the first tab is 'install folder'. The reason you can't do an "install file" and and "install service" is (presumably) because the "install service" goes to copy the file in but finds it is already there. Maybe the file is locked and so the implicit copy from the "install service" fails, and so the rest of the "install service" command doesn't run.

