Installing VO Service

Kevin,

What dlls does depends say it needs? When installing a service, all of dlls that are needed need to be located in the program directory. You cannot be assured of a path.

Regards,

Willie


<kdmurphy@eircom.net> wrote in message news:d7637580-b877-41e3-b908-aa33efd0ff6e@q77g2000hsh.googlegroups.com...
> Hi,
>
> Can anyone give me any pointers for this?
>
> I have built an application using the nVO Service example in VO27 and
> this works fine from the command line.
>
> I created an installer - using two different programs, Setup Factory
> and Advanced Installer. The service gets installed but it fails to
> start. Trying to start it manually also fails. It does not matter
> whether it is installed using the Services option or run it as an
> Action. However, if I simply install the files and then manually run
> it from a command prompt it works okay.
>
> Has anyone any ideas?
>
> Thanks in advance.
>
> Kevin

Geoff,

I will send them on to you later. Is the email address I indicated
above th correect oe to use?

Kevin

On Feb 6, 9:41*pm, "Geoff Schaller"
<geo...@softwareobjectivesx.com.au> wrote:
> Just the installer and the folder with the files to install.
>
> I'd like to see what the installer creates.
>
> "kdmur...@eircom.net" <kdmur...@eircom.net> wrote in message
>
> news:eb4b3835-770e-467e-8c5a-adacc6ecd15c@v67g2000hse.googlegroups.com:
>
> > Geoff,
>
> > > Let's start with basics. If you create the service and install it
> > > manually, it is ok. Yes?
>
> > Yes if I install it manually it works fine. It is the standard VO
> > Service example included with VO27, only th service name changed.
>
> > > When you install with the installer, it won't start?
>
> > Correct it appears in the Service Manager but will not start either by
> > the installer or manually fter the installer puts it in.
>
> > > You can manually start the installed service?
>
> > No
>
> > > The one factor affected by the installer is "who" is doing the install
> > > and that user can influence the installed outcome.
>
> > I have tried it as a 'local service' i.e. no account details; and with
> > the user name I log in to Windows with. This I assumed would work as I
> > cn install it from th command line.
>
> > > Is this XP or Vista?
>
> > Windows XP
>
> > > (Want to send me the installer project and some exes?)
> > At this point in time I do not have the installer file to hand. When I
> > get back to that machine (1700 GMT this evening) I will do a couple of
> > checks and send it on. Will I send it to geoff at
> > softwareobjectives .com.au?
>
> > What do you need just the installer or anything else as well?
>
> > Kevin

Wille,

Would this not affect the runnign of th application when installed
manually as well? If I check the properties of te service it points to
the folder the file and ll DLLs are in.

Kevin

On Feb 7, 3:09*am, "Willie Moore" <will...@wmconsulting.com> wrote:
> Kevin,
>
> What dlls does depends say it needs? When installing a service, all of dlls that are needed need to be located in the program directory. You cannot beassured of a path.
>
> Regards,
>
> Willie
>
> <kdmur...@eircom.net> wrote in messagenews:d7637580-b877-41e3-b908-aa33efd0ff6e@q77g2000hsh.googlegroups.com...
> > Hi,
>
> > Can anyone give me any pointers for this?
>
> > I have built an application using the nVO Service example in VO27 and
> > this works fine from the command line.
>
> > I created an installer - using two different programs, Setup Factory
> > and Advanced Installer. The service gets installed but it fails to
> > start. Trying to start it manually also fails. It does not matter
> > whether it is installed using the Services option or run it as an
> > Action. However, if I simply install the files and then manually run
> > it from a command prompt it works okay.
>
> > Has anyone any ideas?
>
> > Thanks in advance.
>
> > Kevin

Dave,

Thanks for the help you did offer. I even tried to modify the code to
get the VOSRVC to start the service fro the command line - thinking
that might work. as yet I've ad no success on that front.

Kevin

On Feb 6, 8:09*pm, "Dave Francis"
<dave.is.a.spam.free.z...@suilven.com> wrote:
> Kevin,
>
> It sounds like the same sort of problem that *hit. I was using a GUI
> interface and I thought that was the problem. But I can't remember if I
> tried taking that out and running blind. I was up against a deadline on a
> client site, and I created an EXE and added it to the startup program list..
> Not elegant, but it has worked for the last 4+ years without a hiccup, so....
>
> Sorry I can't be more helpful,
>
> Dave Francis
>
> <kdmur...@eircom.net> wrote in message
>
> news:e01c022b-6d6e-44e9-9be3-0748f2755b5d@1g2000hsl.googlegroups.com...
>
> > Dave,
>
> > You asked about the Event Viewer giving any help. This is what it
> > shows:
>
> > Application log
> > Product: Callback Updater -- Error 1920. Service 'FSG Callback
> > Schedule Service' (FSGCallBackService) failed to start. Verify that
> > you have sufficient privileges to start system services.
>
> > System Log
> > The FSG Callback Schedule Service service failed to start due to the
> > following error:
> > The service did not respond to the start or control request in a
> > timely fashion.
>
> > As far as I know I hae the appropriate permissions - especially as I
> > can run the program manually. Searching for the error in the MS KB
> > gives nothing at all.
>
> > Kevin

Geoff, Dave, Willie,

I was getting a copy of the installer to send to Geoff and was
checking it functioned when I spotted something which I thought I
would check out first. It turns out there were two problems - one of
which I was sometimes fixing without realising it.

First was the spaces in the folder name - which I removed on some
occassions.

Second I was putting the '/install' option as a command line argument
which the installer was adding. I spotted this today when looking at
the properties in Service Manager. As to why I missed it before I
don't know but thinking about it makes sense.

Anyway removing both of these fixed the problem.

Thanks for the help.

Kevin

Excellent!

I often find that making a sample fixes things <g>.

Also, if you need spaces in folder names, just enclose the whole path in
double quotes.

Geoff



"kdmurphy@eircom.net" <kdmurphy@eircom.net> wrote in message
news:770b056b-ba9b-43e8-97f7-345cfc5146aa@q39g2000hsf.googlegroups.com:

> Geoff, Dave, Willie,
>
> I was getting a copy of the installer to send to Geoff and was
> checking it functioned when I spotted something which I thought I
> would check out first. It turns out there were two problems - one of
> which I was sometimes fixing without realising it.
>
> First was the spaces in the folder name - which I removed on some
> occassions.
>
> Second I was putting the '/install' option as a command line argument
> which the installer was adding. I spotted this today when looking at
> the properties in Service Manager. As to why I missed it before I
> don't know but thinking about it makes sense.
>
> Anyway removing both of these fixed the problem.
>
> Thanks for the help.
>
> Kevin

Geoff,

I wonder if you can give me any additional pointers on thix one?

If the files are installed in to a folder with no spaces in the path
(eg c:\serviceapp) it install and start fine. If it installs to a
folder like "c:\program files\serviceapp" it fails to start giving a
1053 error. Checking the properties for the ervice shows the path with
quotes.

Any ideas what the problem may be? all the files needed are in the sme
folder.

Kevin

Not sure - stick to a path without spaces for the while.
I'd need to see the app to try to find blame
(Not I have services running on my PC that live all over the place)


"kdmurphy@eircom.net" <kdmurphy@eircom.net> wrote in message
news:4b80992c-adda-4046-b096-4408622814ed@72g2000hsu.googlegroups.com:

> Geoff,
>
> I wonder if you can give me any additional pointers on thix one?
>
> If the files are installed in to a folder with no spaces in the path
> (eg c:\serviceapp) it install and start fine. If it installs to a
> folder like "c:\program files\serviceapp" it fails to start giving a
> 1053 error. Checking the properties for the ervice shows the path with
> quotes.
>
> Any ideas what the problem may be? all the files needed are in the sme
> folder.
>
> Kevin