Hi, I keep getting a 1406 error when trying to install my repackaged ws_ftp, this is what i get:

1406 error

this is what the permissions look like for this registry-key:

*update* sorry the url was wrong in my first post!!

registry permission

I've also tried to change it so that the "Everyone" group had full permission to COMPONENTS but no luck..

I have noticed that the i dont have the COMPONENTS key in my client computers registry at all before installation of WS_FTP - is this something to do with permission or what? ive looked around in all other threads on this topic and google but no luck.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

-1
If the COMPONENTS registry key is missing, it sounds like your capture is incomplete.

What you should get into the habit of doing when re-packaging is to:
- install your MSI
- remove any flag which the vendor's set-up uses to indicate that the app is already installed
- start a lightweight snapshot tool (e.g. InstallWatch) and take a 'Before' snapshot
- run the vendor's install over the top of yours
- take an 'After' snapshot
- incorporate any relevant changes or additions into your package
- re-test.
Answered 02/14/2010 by: VBScab
Red Belt

Please log in to comment
0
no i dont mean that it isnt captured, just forget this line

"I have noticed that the i dont have the COMPONENTS key in my client computers registry at all before installation of WS_FTP - is this something to do with permission or what? ive looked around in all other threads on this topic and google but no luck. "

:)

the permission problem is the thing i want help wit
Answered 02/14/2010 by: fn86
Senior Yellow Belt

Please log in to comment
0
Are users or administrators allowed to create new keys in the HKLM?

What is the solution to this problem? Help is highly apreciated :)
Answered 02/15/2010 by: fn86
Senior Yellow Belt

Please log in to comment
0

Are users or administrators allowed to create new keys in the HKLM?



Considering its a locked down environment....Users cannot, however Admins can...
Answered 02/15/2010 by: slay_u
Orange Belt

Please log in to comment
0
It doesnt help to change the permissions from the installation expert / registry view

i need some help here guys, i want to give permissions to everyone to write to the HKLM\COMPONENTS key.
Answered 02/15/2010 by: fn86
Senior Yellow Belt

Please log in to comment
0
That's the beginner's way out and you'd be a fool to do that.

Add the key and its branches to the package, via a transform if it's already an MSI supplied by the vendor, re-installing to clients which have already received it, if need be.

Make sure you use the correct structure, too: by default, there's no such key as 'HKLM\Components'.
Answered 02/15/2010 by: VBScab
Red Belt

Please log in to comment
0
thanks for your response vbscab :) the msi is not from vendor (original was installshield exe converted with setupcapture)

anways, are you suggesting that i export the whole COMPONENT key to a .reg file, change the permissions on COMPONENT and then export it in again by a transform?
aren't there any easier way?
Answered 02/15/2010 by: fn86
Senior Yellow Belt

Please log in to comment
0
Huh? How did you get to that conclusion from what I said?!?

Look, forget permissions. It seems clear to me that the application is trying to write a vlue to a registry key (COMPONENTS) which doesn't exist. Find out EXACTLY what the key is (I don't believe it's as simple as HKLM\Components), add that key AND the value that the application is trying to write to your package and re-test.

When you've done that, look up what a transform is, as you seem to be labouring under a major misapprehension.
Answered 02/16/2010 by: VBScab
Red Belt

Please log in to comment
0
After I've runned the legacy setup converter in wise, in the installation expert there are about 24 000 values under different subkeys under HKLC\COMPONENTS\ - which you can see in this picture:

http://img3.yfrog.com/i/62041537.png/

so thats why im curious about your reply, i get the impression that you think these keys doesnt exist in the package?

"Find out EXACTLY what the key is (I don't believe it's as simple as HKLM\Components), add that key AND the value that the application is trying to write to your package and re-test. "

So the thing is that these keys are already in my package as shown in installation expert, and they was captured from the legacy setup convertion.
BUT when running it in debug mode or running a compiled version, i get the permission error that i showed in the first pictures in my first message.

What can i do about this?
Answered 02/18/2010 by: fn86
Senior Yellow Belt

Please log in to comment
0
OK, one, I think your capture is broken. Do you get those keys in that location when you just install the app (forget capturing for now).

Two, I think the machine you're packaging on is broken, since there doesn't seem to be any permissions for the HKLM hive for that key to inherit (presuming its location is correct, of course). I would expect to see at least Administrators, Power Users and System in there!
Answered 02/18/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity