Failed to install Input Director's Windows Service error

[guelah75]

I am attempting to install version 1.2.2 on a Windows XP Pro machine
(service pack 3) but the installer fails on the Windows Service
portion on the install.

Any help would be great!

Thank you
guelah75

[Shane]

On Jul 22, 7:51 am, guelah75 <guela...@gmail.com> wrote:
> I am attempting to install version 1.2.2 on a Windows XP Pro machine
> (service pack 3) but the installer fails on the Windows Service
> portion on the install.
>

What error message are you seeing?

Open Control Panel / Add + Remove Applications and see if Input
DIrector is in the list of installed applications. If it is,
uninstall it (and say yes to clearing its configuration). Reboot your
machine and then try installing again.

Regs,

Shane.

[erik petersen]

Screen shot of error message attached to this email, thank you for the help on this!

--
You received this message because you are subscribed to the Google Groups "Input Director" group.
To post to this group, send email to input-d...@googlegroups.com.
To unsubscribe from this group, send email to input-directo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/input-director?hl=en.

[Shane]

On Jul 28, 6:11 am, erik petersen <guela...@gmail.com> wrote:
> Screen shot of error message attached to this email, thank you for the help
> on this!

Hi,

Try right-clicking on the Input Director installer and selecting 'Run
as Administrator'. Did that help?

Regs,

Shane.

[Duane]

I have the exact same problem, but let me confess more info.

It was running great, XP SP3. This machine is getting old and clunky,
I went into MSConfig and turned off a bunch of stuff to hopefully help
me out.... well next reboot it complained about not being able to
start the ID service I think. I did this once before so I ignored it,
planning on reinstalling later.

I removed it via the icon in the program group, said to save my
config.

Downloaded 1.2.2, attempted install and get exact same thing. I
looked, and the service was still in SERVICES so I went through the
registry and killed that off, rebooted.

Still the same error. I do not have administrator password but I'm
pretty sure I can install anything on this machine as I have had it 4
years and can get away with anything so far.

I'm going to grab your newer beta and try that for the heck of it.
Thanks for any ideas.

[DocGolden]

Any further action taken on this issue? I'm seeing the same problem
on a laptop I'm trying to get up & running. My system is Win XP Pro
SP3. My first attempt at an install was w/ 1.2.2.76. I have since
downloaded 1.2.2.1.86 to try & get the install to complete. Any
suggestions on a fix or workaround would be greatly appreciated.

Thanks!

[DocGolden]

As a follow up. I was finally able to get it to install. Our network
admins install Symantec End-Point Protection on our machines. After I
removed this, I was able to get the install to complete.

However, w/ 1.2.2.1.86, I was not able to use the application b/c I
would get a 'Fatal Error' w/ a message about not being able to create
the configuration file. I went back to 1.2.2.76 & was able to
successfully install & configure. After an upgrade again to
1.2.2.1.86, I seem to be running fine.

Hope this helps someone.

[Shane]

On Oct 7, 1:42 am, DocGolden <mdunkl...@gmail.com> wrote:
> As a follow up.  I was finally able to get it to install.  Our network
> admins install Symantec End-Point Protection on our machines.  After I
> removed this, I was able to get the install to complete.

Hi,

Thanks for providing this information. I've got another user hitting
the same problem - I'll find out whether he is also running Symantec
End-Point Protection.

> However, w/ 1.2.2.1.86, I was not able to use the application b/c I
> would get a 'Fatal Error' w/ a message about not being able to create
> the configuration file.  I went back to 1.2.2.76 & was able to
> successfully install & configure.  After an upgrade again to
> 1.2.2.1.86, I seem to be running fine.

I think there is a bug in build 86 that causes a problem when
creating / upgrading its configuration. I'm in the process of trying
to track it down now.

Regs,

Shane.