Sergy mate

Here is text from the link you suggested:

1.Insufficient privileges for writing to that particular registry key.
I am Admin. What more priviledges do I need to have?

2.On Windows NT machines, the installation is attempting to create a registry key off of the HKEY_LOCAL_MACHINE hive in the Windows registry. Windows NT does not allow this.

I do not create the keys nor what keys are needed. That is done by the installer to install the runtimes and register them.


3.An invalid setup version is specified.

I just created this version so I do not follow this point.

4.MSI 1.1 or 1.2 is used, rather than MSI 2.0.

How to know the version number?


5.On Windows 95, 98, and Me machines, a registry key size limit is exceeded.
This is a Win200 Server

6.A binary registry value has spaces, for example, 01 00 04 80 00 00.
See point 2 above.


I am surprised that no one else has found this error except I remember reading something similar somewhere but cannot remember where.

Guess there is no current solution?

Thanks for your prompt reply.

Bernard


>Hi Bernard,
>
>Setup created by ISX LE VFP is just a wrapper around Windows Installer and ERROR 1406 is generated by Windows Installer. Did you eliminate all posible causes of this error as outlined in http://support.installshield.com/kb/view.asp?pcode=ADTUN200E&articleid=Q107090 ?
>
>
>>I need to install the VFP runtimes on our servers which run Win2K.
>>
>>I have created a single Installation EXE for this with the option of installing for current user or ALL users. This has been done with the InstallShield version found on the VFP7 CD.
>>
>>Every time I try to install the runtimes START, SETTINGS, ADD/REMOVE PROGRAMS and then install, I get 3 very similar errors:
>>
>>1. ERROR 1406: Could not write value "VersionMajor" to key
>> UNKNOWN\PRODUCTS\6AAASED....E1435B\INSATALLPROPERTIES. Verify that you have sufficient access to that key, or contact your support personnel.
>>
>>2. ERROR 1406: Similar message except :
>>
>> HKEY_LOCAL_MACHINE\SOFTWARE\MICRO$OFT\WINDBLOWS\CURRENTVERSION\UNINSTALL\{ASD .....etc
>>
>>3. Similar to 2 except the key {....} is different. I just click on Ignore and the runtime is installed.
>>
>>I am logged in with ADMINISTRATOR rights.
>>
>>I have searched all over but have not found any reference to this except a small one on the InstallShield KB site where they blame the Windblows Installer version.
>>
>>Does anyone know of a fix for this?
>>
>>Thanks
>>
>>Bernard Bout