CostFinalize, is unable to resolve a value
I took a snap shot using InstallShield. In the log created during creation of the msi there is message that INSTALLDIR is not defined in the iptions.ini file. Is that a problem? Or just a warning?
During the installation i am getting 1606 Error for the %%USERPROFILE%% "CostFinalize, is unable to resolve a value of an entry defined in the directory tableâ€Â
There is a property in the property table DIRPROPERTY1 = %%USERPROFILE%% i am guessing that is where FileCost is failing. In the directory table DIRPROPERTY1 after the snapshot had DefauldDir set to "." I though it was causing an error so i changed it to %USERP~1|%USERPROFILE%.
Still getting same 1606 error on %%USERPROFILE%%.
Any help would be appreciated.
Thank you.
During the installation i am getting 1606 Error for the %%USERPROFILE%% "CostFinalize, is unable to resolve a value of an entry defined in the directory tableâ€Â
There is a property in the property table DIRPROPERTY1 = %%USERPROFILE%% i am guessing that is where FileCost is failing. In the directory table DIRPROPERTY1 after the snapshot had DefauldDir set to "." I though it was causing an error so i changed it to %USERP~1|%USERPROFILE%.
Still getting same 1606 error on %%USERPROFILE%%.
Any help would be appreciated.
Thank you.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
AngelD
17 years ago
Sound like the DIRPROPERTY1 property as the value of the property will be used instead of the same primarykey in the Directory table.
Remove it from the Property table and author a set directory custom action to set the directory with the value of [%USERPROFILE]\.
Remove it from the Property table and author a set directory custom action to set the directory with the value of [%USERPROFILE]\.
Posted by:
ogeccut
17 years ago
Thanks for the reply. I'll try that. However i think CostFinalize "FileCost" is done under system and thats why it cant see network drive. Maybe i am wrong. But i see it stops at the FileCost.
Posted by:
jmcfadyen
17 years ago
also need to be aware that deploying with users logged out via tools such as SMS can cause this issue as well
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.