Hi,
Had this a few times now, but thought it best to report it as other people may be experiencing this issue?..
Installing a version of Deadline v5 beta (any version) if the previous beta version of Deadline has been installed and running normally on a Win7x64 OS system, sometimes causes the installer from the next version release to not execute correctly when I try to install it.
- Let’s say, I have beta 8 on my Win7x64 OS system installed to “c:\deadline”.
- Run Deadline monitor, slave, submit some jobs, done.
- already logged in as a user with Admin rights, so extract repository from downloaded zip file and double-click the installer.
- nothing happens, but in task manager the installer.exe is running.
- wait ~10mins. Nothing. so restart machine.
- works fine, first time.
Its happened too many times now to be just Win OS having a “fit”. Can anyone else repeat this pattern?
(I actually think this was happening to me during beta v4.1 cycle as well, which again I was on Win7, instead of XPx64…)
Mike
Hi Mike,
We’ve never seen this problem here, and you’re the first to report it. We’ve all moved to Windows 7 here after the change to Thinkbox, and we’re constantly running both the client and repository installer, so if this was a widespread issue, I think we would have seen it at least once. I also followed your steps to reproduce, and that worked fine here.
Are there any Deadline processes running when you run the installer? If so, does closing all of them make a difference?
Cheers,
OK, Thanks.
The only process running is the deadline launcher.
As this doesn’t seem wide-spread, it may well be my machine…
Thanks,
Mike
Just tested RC1 repository installer and this time, I made sure the deadline launcher.exe was closed and the installer executed fine.
Perhaps we should consider forcing the deadline launcher.exe closed if its running by presenting a warning dialog just like the client installer does?
Mike
That’s strange that you needed to close the launcher for the repository installer to work. I always have the launcher running when I run the repository installer and I’ve never experienced this behavior. The repository installer doesn’t have any interaction with the launcher, or does anything that should conflict with a running launcher, that’s why there is no warning if any of the Deadline applications are running.
If you run the repository installer from a command prompt with the /debug argument, it will create a temporary directory in your user-specific temp folder that will stick around after the installer exits. For example, C:\Users\Ryan\AppData\Local\Temp\ijtmp_7CA26290-CB68-4543-BBC2-C0B03849B8B7. In this temp folder is a file called debug.log. After the installer gets stuck, send us this log file and we’ll see if there are any errors.
Thanks!