This topic contains 6 replies, has 2 voices, and was last updated by Anonymous 9 years, 4 months ago.
9th November 2008 at 5:48 am #2690
I’m running Windows XP Pro SP3, and had a problem installing Firefly Media Server SVN-1696. Specifically, the installer claims to be skipping WindowsInstaller -xxxx, but then executes it. It never returns. When I try to kill the install using the Task Manager, it takes a couple of tries.
What could I be doing wrong?
David9th November 2008 at 1:39 pm #17855
After killing the installation attempt, Firefly is in H:Program FilesFirefly Media Server, but there is no service to start or stop. The taskbar tool says that I need to be an administrator in order to install the software.
If I doubleclick on the file that appeared to hang, WindowsInstaller-KB893803-v2-x86.exe, it indicates that the service pack that I am running (Windows XP SP3) is newer than the update I’m trying to install.
When I try to reboot later, it appears that some application that was trying to uncompress files had hung, and I have to kill that process.9th November 2008 at 7:20 pm #17856
Are you a local administrator?9th November 2008 at 7:55 pm #17857
Yes, I am a local administrator.11th November 2008 at 9:49 pm #17858
That was a good idea – when I run FireflyShell.exe, the start server button is greyed out, and it tells me that I need to be a local administrator in order to run it.
My computer is not a member of a domain, so “local” is perhaps a misnomer. My user has administrator privileges.
Any other ideas?
David12th November 2008 at 3:22 pm #17859
Well you did install Bonjour and the whatnot?
Can you see in the system / application etc. log for any messages of the installer or firefly?
Has the service been created at least?
What about runnnig firefly manually in the foreground iE through a command prompt window? That should always work.13th November 2008 at 3:58 am #17860
I turned off my network, turned off Spybot Search & Destroy and Avast Antivirus, and re-ran the installer. It hung in the same place. I started up the Task Manager, and killed the task that the installer was running. The rest of the install process completed successfully.
You must be logged in to reply to this topic.