/build/static/layout/Breadcrumb_cap_w.png

MSI Error 1406 and NO letter in ProductVersion

>>>>>>> This thread has been posted to WinInstall Errors also, but i think it belongs more to general forum because it is not a WinInstall Error.. It's more a common MSI problem..

Hello all,

i hope I can get some support here because I am really tired with this problem.

I generated a big MSI package of ProEngineer/Wildfire (CAD Application) using Wininstall LE. Eveything is fine, but when I install the package on a test client (logged on as Administrator) I got the message (taken from Eventlog)

Produkt: Wildfire_2_0 -- Error 1406. Value WIFEAT00000001 could not be written to key UNKNOWN\Products\ADA25C92EF09A5F4484222C18814C0E4\Features. System Error .
Please check whether you have access rights to this key or contact support.
>> I had to translate this to english, because it was in german

Very strange is that it happens at the end of installation. Remaining time is 0sec.

When I click "ignore" on this error message, everything is fine and the package installations finished and the software is ready to use. But I cant distribute the packacke with this error hands-free.

I found out that this error is often based on letters in the ProductVersion. But I do not have letters in the ProductVersion. ProductVersion is 1.0. The msiexec version was originally 2.0. But I upgraded it for testing purposes to 3.0 - without any effect!

At this point I really dont know where to search for a solution anymore. So any help would really be appreciated. A "ignore errors" for msiexec would be enough for the first step if it is possible.

0 Comments   [ + ] Show comments

Answers (6)

Posted by: bheers 19 years ago
Second Degree Blue Belt
0
check to see if there is a space in the version.
Posted by: volkerkalt 19 years ago
Senior Yellow Belt
0
I have updated the error message because i posted a wrong (but similar) one.

Please read the error message and description again, - now it is the right one.

Maybe you have an idea what the problem is.

regards,

Volker
Posted by: bheers 19 years ago
Second Degree Blue Belt
0
can you post a verbose log of this application install.


msiexec /l*v "c:\lg.log" /i "d:\MyProduct\MyProduct.msi"

also try this

http://forums.veritas.com/discussions/thread.jspa?messageID=4446
Posted by: MSIMaker 19 years ago
2nd Degree Black Belt
0
At a guess I would say that you have an INI file which is being processed during the installation. It is trying to write to the registry but the capture hasnt captured the correct hive and its giving you an error.

First thing is to open the msi and look in the INI file table for the function.

Next is to do a search for the string error your getting. WIFEAT00000001 could not be written to key UNKNOWN\Products\ADA25C92EF09A5F4484222C18814C0E4\Features. System Error

Search for WIFEAT00000001 and then ADA25C92EF09A5F4484222C18814C0E4. This will give you an idea of where in the install your getting the error.

IF it is an INI file doing it then possibly grab the data from the INI file and put it into the registry yourself.....this might sort it out straight away.
Posted by: volkerkalt 19 years ago
Senior Yellow Belt
0
I've logged all actions of the MSI file now.

As already mentioned I am trying to package ProE / Wildfire, a big CAD application, so the MSI size is about 700mb and the generated log file has a size of 60MB.

So I post only the part concerning the error message. If the whole log file is needed please email me at: Volker.Kalthaus@gkndriveline.com

I'm testing the MSI package within a VMWare Image. I havent tested it on "real" client systems. Normally VMWAre is very fine for testing the packages.. But could it be, that the error is related to the VMWAre Image?... Will definetly test the package on a "clean" client on Monday...

Here we go with the log:

============= BEGIN OF LOG ==============

MSI (s) (3C:D0): Executing op: IniWriteRemoveValue(Section=Pro_E_Section,Key=WAIT_FRPROE,Value=250,Mode=0)
WriteIniValues: Datei: proobj.ini, Abschnitt: Pro_E_Section, Schlüssel: WAIT_FRPROE, Wert: 250
MSI (s) (3C:D0): Executing op: IniWriteRemoveValue(Section=Pro_E_Section,Key=PROOBJ_HELPFILE,Value=C:\PTC\proeWildfire_2_0\text\usascii\proole.hlp,Mode=0)

WriteIniValues: Datei: proobj.ini, Abschnitt: Pro_E_Section, Schlüssel: PROOBJ_HELPFILE, Wert: C:\PTC\proeWildfire_2_0\text\usascii\proole.hlp

MSI (s) (3C:D0): Executing op: ActionStart(Name=SelfRegModules,Description=Module werden registriert,Template=Datei: , Ordner: )

Aktion 11:01:30: SelfRegModules. Module werden registriert
MSI (s) (3C:D0): Executing op: ProgressTotal(Total=5,Type=1,ByteEquivalent=1300000)
MSI (s) (3C:D0): Executing op: SetTargetFolder(Folder=C:\PTC\proeWildfire_2_0\dsrc\i486_nt\obj\)
MSI (s) (3C:D0): Executing op: RegSelfReg(File=mfc42.dll,FileID=WIFILE00000201)
SelfRegModules: Datei: mfc42.dll, Ordner: C:\PTC\proeWildfire_2_0\dsrc\i486_nt\obj\
MSI (s) (3C:D0): Executing op: SetTargetFolder(Folder=C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\bin\)
MSI (s) (3C:D0): Executing op: RegSelfReg(File=jpicom32.dll,FileID=WIFILE00001523)
SelfRegModules: Datei: jpicom32.dll, Ordner: C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\bin\
MSI (s) (3C:D0): Executing op: RegSelfReg(File=jpinsp.dll,FileID=WIFILE00001530)
SelfRegModules: Datei: jpinsp.dll, Ordner: C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\bin\
MSI (s) (3C:D0): Executing op: RegSelfReg(File=jpishare.dll,FileID=WIFILE00001531)
SelfRegModules: Datei: jpishare.dll, Ordner: C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\bin\
MSI (s) (3C:D0): Executing op: SetTargetFolder(Folder=C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\javaws\)
MSI (s) (3C:D0): Executing op: RegSelfReg(File=JavaWebStart.dll,FileID=WIFILE00001553)
SelfRegModules: Datei: JavaWebStart.dll, Ordner: C:\PTC\proeWildfire_2_0\i486_nt\obj\J2RE14\javaws\
MSI (s) (3C:D0): Executing op: ActionStart(Name=RegisterUser,Description=Benutzer wird registriert,Template=)
Aktion 11:01:31: RegisterUser. Benutzer wird registriert
MSI (s) (3C:D0): Executing op: UserRegister(Owner=KIT,Company=GKN Automotive GmbH,ProductId=none)
RegisterUser: {29C52ADA-90FE-4F5A-8424-221C88410C4E}
MSI (s) (3C:D0): Executing op: ActionStart(Name=RegisterProduct,Description=Produkt wird registriert,Template=)
Aktion 11:01:31: RegisterProduct. Produkt wird registriert
MSI (s) (3C:D0): Executing op: ChangeMedia(,MediaPrompt=Legen Sie den Datenträger ein: ,,BytesPerTick=0,CopierType=0,,,,,,IsFirstPhysicalMedia=1)

MSI (s) (3C:D0): Executing op: DatabaseCopy(DatabasePath=C:\WINNT\Installer\6d184.msi,ProductCode={29C52ADA-90FE-4F5A-8424-221C88410C4E},,,)

MSI (s) (3C:D0): Executing op: ProductRegister(UpgradeCode={7DEC4BD5-2FEF-488D-BACF-66142057FA44},VersionString=1.0,,,,InstallSource=N:\ptc\,Publisher=Default Manufacturer,,,,NoModify=1,,,,,,,,EstimatedSize=673339)

RegisterProduct: {29C52ADA-90FE-4F5A-8424-221C88410C4E}
MSI (s) (3C:D0): Executing op: ProductCPDisplayInfoRegister()
MSI (s) (3C:D0): Executing op: ActionStart(Name=PublishFeatures,Description=Produktfunktionen werden veröffentlicht,Template=Funktion: )

Aktion 11:01:34: PublishFeatures. Produktfunktionen werden veröffentlicht
MSI (s) (3C:D0): Executing op: FeaturePublish(Feature=WIFEAT00000001,,Absent=2,Component=9X!@dDI'T?y{Qh2*U_-oElFJ2L9v_9B4W2?r-OFk$Lv,1h,}}@d?SqZmeX3Sdc,(1=5T-=!1-Oj0tBxeDtu3lrt%_??k,&S8A2+]VImfZ&iba=g=t+zhEZD'?e2$!io0@?U{88X2io$x+k[A9dEJ+ALD~Q^C8bbMUUD@!H

Yyb9Ys6Z.?zrS4^%irJC,hF@3K&'Z$C[uUYGSz5.3[c@(@843svWnBE9zYM6Thz8k6nC-_-@^ZaRQ*`~yV^A9U2QJa,7y_zz4ex.(%e92c{dGWZY~[)ff]PfN*t=fa0l)p@ebyg]c&Pkz@eAE)O?6a.ZwH*poZf2GfM=}=l8@!sj}lD%_}obB},=lZ7O6qDGta{ul3Da({i9}P+Z-ykJtyF1v94k%fi?0Rq7`m&s'm]7EEF+w`U9a7ddNFs]n0n

)ins)~$a8oW)uzK'8$7Gk{m@Heqt?jgglmQt?!OsJVla^9Q3?3%-fAW{7'RE4OTCAEUIAIQynNqKq0_~$D`bQ!.O?9!_EkA5{]kL9.np+N)7A,vD}-P)Mr(3Wz)&T.xz9[-Uc0}xo68`KfF*uqjj9uBC&*UXgEucPz_2y.~J@7Wr,TKCc's}AaIrhr^h=1x+Z_7[UD,0o@cz+b0i9L.u%zXWqBZzq~hD5UH'=Di3KxCH4*!9{M$]Qu5=?p3,Ovk

tX$'EKmCVuNBI=l9BV!iyx%-F`CjD7c~v89_lKXZqDs$ShMPb*apa8Kh.O7y[D=TBW1SP1+6*=4JRz8j.@GpXF~hTe%gm9%Oabe]estrWlnr+`~@)ApyWXO]%]_oX@ikLEsRD?h=e0C]XGY!c2Vqi4^CD@Jio~t97N-Kh`IaER1-RA~BT3j)fs9+pwqF=$wbm8}XJ2LkLHnihVDPrU.Ry=dL?0,TZv{-^}15{i@2TA^XCf]m7_ck9fYPMB1ab=B

MUZthl$Pf8]m+gHBTSA&Z
PublishFeatures: Funktion: WIFEAT00000001
MSI (s) (3C:D0): Note: 1: 1406 2: WIFEAT00000001 3: Products\ADA25C92EF09A5F4484222C18814C0E4\Features 4: 1450
Fehler 1406. Wert WIFEAT00000001 konnte nicht unter den Schlüssel UNKNOWN\Products\ADA25C92EF09A5F4484222C18814C0E4\Features geschrieben werden. Systemfehler . Überprüfen Sie, ob Sie ausreichende Zugriffsrechte auf diesen Schlüssel besitzen, oder setzen Sie sich mit dem Supportpersonal in Verbindung.

MSI (s) (3C:D0): Produkt: Wildfire_2_0 -- Fehler 1406. Wert WIFEAT00000001 konnte nicht unter den Schlüssel UNKNOWN\Products\ADA25C92EF09A5F4484222C18814C0E4\Features geschrieben werden. Systemfehler . Überprüfen Sie, ob Sie ausreichende Zugriffsrechte a

uf diesen Schlüssel besitzen, oder setzen Sie sich mit dem Supportpersonal in Verbindung.


MSI (s) (3C:D0): Executing op: ActionStart(Name=PublishProduct,Description=Produktinformation wird veröffentlicht,)
Aktion 11:29:36: PublishProduct. Produktinformation wird veröffentlicht
MSI (s) (3C:D0): Executing op: ProductPublish(PackageKey={29C52ADA-90FE-4F5A-8424-221C88410C4E})
1: {29C52ADA-90FE-4F5A-8424-221C88410C4E}
MSI (s) (3C:D0): Note: 1: 1402 2: UNKNOWN\Installer\Products\ADA25C92EF09A5F4484222C18814C0E4


========= END OF LOG =================

Thanx to any1 supporting me on this problem.

It is very important to get this software being distributed as package.

So thanks for all the assistance. I hope we will be able to find a solution.

Regards,

Volker
Posted by: VikingLoki 19 years ago
Second Degree Brown Belt
0
Uff Da! Yerman log file! Ya, dat ouch my noggin. [&:]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ