WLD 5.1 hangs when installing
Author: dhermanus
Creation Date: 9/2/2008 12:08 PM
profile picture

dhermanus

#1
Hi,

I've downloaded the 5.1 developer demo version.
However it hanged when I tried to install it.
(hanged on the fifth bar of the installshield)

Deddy
profile picture

Eugene

#2
Please create a support ticket indicating as much detail about your configuration as possible.
profile picture

Cone

#3
Make sure to give the installer ample time. There's a minor bug in InstallShield (scripting) that causes the installer to take more time than expected if .NET Framework 1.0 isn't installed on the target machine. Even so, I've never seen an install take more than about 1 minute.

Also, the .NET Installer could try to access the internet. If your firewall asks you if it's "okay", you can say either yes or no, but you need to acknowledge that dialog for the installation to continue.
profile picture

dhermanus

#4
It took more than 20 mins before I had to stop the install shield by using end task and there's no firewall
turned on Microsoft or others.

There are 4 dll files that has already been copied to the WL5 directory before I had to end task to stop the install shield. (Community.Comission.dll, ControlLibrary, FidelityComponents, Log4Net).

Hope this helps.

Thanks,
Deddy
profile picture

Cone

#5
It doesn't help, sorry. Please follow Eugene's cue, it would be a better starting point.
profile picture

dhermanus

#6
I'll try to manually install the ,NET framwork 1.0 first and see how it goes.
If that doesn't work then i'll go to support.

profile picture

Eugene

#7
Hi Deddy. I see your trial record, therefore installing .NET 1.1 must have worked for you?
profile picture

Eugene

#8
Note to everyone: please install and activate WLD5 using Administrator account. Trying to do it as a regular user can cause problems.
profile picture

inrodwetrust

#9
Hi Eugene,

Is there a way to get WLD to run in usermode(without using runas), as it tries to re-register. I've set the data dirs to allow user r/w but no diff,(often does the trick in cases like this). I searched the registry to look for a way to copy any entries from the admin a/c to the user a/c but couldn't find any.

Any ideas?


Regards
profile picture

Cone

#10
Which Version of WLD are you referring to?
profile picture

inrodwetrust

#11
5.1, that's just been released.
Regards
profile picture

inrodwetrust

#12
It's Ok, worked it out, I just copied the admin "Application Data\Fidelity Investments" dir from docs & settings to the equivalent user dir.

profile picture

Cone

#13
Clearly copying that directory is an extraordinary measure that shouldn't be necessary. I'd like to know more about the environment and the trouble you had. Please give more details, starting with your O.S.
profile picture

inrodwetrust

#14
XpPro...But...
If it's unique to my machine it's more than likely a host protection program that probably blocked a function on install or something...I'd probably have to reinstall it to find out what happened.
So I wouldn't worry about it.
profile picture

Cone

#15
Okay, thanks. I'll look at it anyway to make sure at non-admin privileged user can run WLD5 without copying folders.
profile picture

Eugene

#16
When 5.0 just came out, I remember some problems with non-admin rights were solved by allowing the users group to modify and write to Program Files\Fidelity Investments\Wealth-Lab Pro 5.
profile picture

inrodwetrust

#17
Yes, I probably just had to make sure I had the permissions right, I have similar issues with some other programs. Giving the user group read/write permissions to the dir, will often do the trick. But I usually like to minimise user permissions & only allow to the data dir & any config or log files. I get caught out if a new file is created, so the folder needs read/write permissions. I'm not sure if that was the case in this instance. Maybe I'll try a reinstall sometime.
I only go down this track to minimise potentual malware issues. Bit of a pain & but maybe worth it one day.

Regards
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).