ice03
Invalid format string; Table: Registry, Column: Value, Key(s): registry85 ice03.html Registry Value registry85
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry86 ice03.html Registry Value registry86
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry87 ice03.html Registry Value registry87
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry88 ice03.html Registry Value registry88
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry89 ice03.html Registry Value registry89
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry90 ice03.html Registry Value registry90
Evaluation: ICE03
Dialog Resume_Install_Dialog has dead-end tab order at control Bitmap32. ice23.html Control Control Resume_Install_Dialog Bitmap32
Evaluation: ICE23
Component DesktopFolder installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. ice38.html Component Attributes DesktopFolder
Evaluation: ICE38
Evaluation: ICE43
Invalid format string; Table: Registry, Column: Value, Key(s): registry85 ice03.html Registry Value registry85
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry86 ice03.html Registry Value registry86
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry87 ice03.html Registry Value registry87
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry88 ice03.html Registry Value registry88
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry89 ice03.html Registry Value registry89
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry90 ice03.html Registry Value registry90
Evaluation: ICE03
Evaluation: ICE18
Evaluation: ICE23
Evaluation: ICE38
Component DesktopFolder has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file. ice43.html Component Attributes DesktopFolder
Evaluation: ICE43
Invalid format string; Table: Registry, Column: Value, Key(s): registry85 ice03.html Registry Value registry85
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry86 ice03.html Registry Value registry86
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry87 ice03.html Registry Value registry87
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry88 ice03.html Registry Value registry88
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry89 ice03.html Registry Value registry89
Evaluation: ICE03
Invalid format string; Table: Registry, Column: Value, Key(s): registry90 ice03.html Registry Value registry90
Evaluation: ICE03
KeyPath for Component: 'DesktopFolder' is Directory: 'DesktopFolder'. The Directory/Component pair must be listed in the CreateFolders table. ice18.html Component Directory_ DesktopFolder
Evaluation: ICE18
Dialog Resume_Install_Dialog has dead-end tab order at control Bitmap32. ice23.html Control Control Resume_Install_Dialog Bitmap32
Evaluation: ICE23
Component DesktopFolder installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. ice38.html Component Attributes DesktopFolder
Evaluation: ICE38
Component DesktopFolder has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file. ice43.html Component Attributes DesktopFolder
Evaluation: ICE43
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
AngelD
15 years ago
Posted by:
su.deep
15 years ago
Thanks for the respond.
OK the installation is for 10 users. when i installed on my test machine i used all user property. installation looks fine but after installation the icons don't seem to work. Do i have to create a key under HKCU as the error i get...
KeyPath for Component: 'DesktopFolder' is Directory: 'DesktopFolder'. The Directory/Component pair must be listed in the CreateFolders table. ice18.html Component Directory_ DesktopFolder
Evaluation: ICE18
If so please help.
It won't let me create a new advertised shortcut for some reason.
My shortcut table looks like this:
shortcut :softwarename
Directory:Desktopfolder
Name: softwarename
component_ : Desktop folder
target : [shorcutpath1]
arguments:
descrip:
hotkey:0
Icon_:
Iconindex:0
showcmd:1
wrdir: bin
I can ignore other errors but this is causing me the trouble to launch the software from both desktop icon and the startup menu.
OK the installation is for 10 users. when i installed on my test machine i used all user property. installation looks fine but after installation the icons don't seem to work. Do i have to create a key under HKCU as the error i get...
Evaluation: ICE18
It won't let me create a new advertised shortcut for some reason.
My shortcut table looks like this:
shortcut :softwarename
Directory:Desktopfolder
Name: softwarename
component_ : Desktop folder
target : [shorcutpath1]
arguments:
descrip:
hotkey:0
Icon_:
Iconindex:0
showcmd:1
wrdir: bin
I can ignore other errors but this is causing me the trouble to launch the software from both desktop icon and the startup menu.
Posted by:
AngelD
15 years ago
The DesktopFolder for example will be resolved to either %USERPROFILE%\Desktop for per-user or %ALLUSERSPROFILE%\Desktop for per-machine.
Component DesktopFolder has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file. ice43.html Component Attributes DesktopFolder
When a component installes files under %USERPROFILE% they should have a HKCU registry entry as keypath, however if you install to per-machine these files will go under %ALLUSERSPROFILE% instead meaning, machine "based" files.
So in this case solving this ICE is only cosmetic. The ICE rules don't know that it is a per-machine install and doesn't take into account about the ALLUSERS property.
KeyPath for Component: 'DesktopFolder' is Directory: 'DesktopFolder'. The Directory/Component pair must be listed in the CreateFolders table. ice18.html Component Directory_ DesktopFolder
This is also costemtic as the "DesktopFolder" path will alredy exist on the machine so no need to created it, the CreateFolder table is used for creating empty folders as otherwise Windows Installer will remove these during install.
Regarding your shortcut issue:
Make sure that the Component.KeyPath column value points to the executable (File.File column value) you want the shortcut to launch and then set the Shortcut.Target column to the feature holding this component (the Shortcut.Component column value), this will make the shortcut advertised.
Component DesktopFolder has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file. ice43.html Component Attributes DesktopFolder
When a component installes files under %USERPROFILE% they should have a HKCU registry entry as keypath, however if you install to per-machine these files will go under %ALLUSERSPROFILE% instead meaning, machine "based" files.
So in this case solving this ICE is only cosmetic. The ICE rules don't know that it is a per-machine install and doesn't take into account about the ALLUSERS property.
KeyPath for Component: 'DesktopFolder' is Directory: 'DesktopFolder'. The Directory/Component pair must be listed in the CreateFolders table. ice18.html Component Directory_ DesktopFolder
This is also costemtic as the "DesktopFolder" path will alredy exist on the machine so no need to created it, the CreateFolder table is used for creating empty folders as otherwise Windows Installer will remove these during install.
Regarding your shortcut issue:
Make sure that the Component.KeyPath column value points to the executable (File.File column value) you want the shortcut to launch and then set the Shortcut.Target column to the feature holding this component (the Shortcut.Component column value), this will make the shortcut advertised.
Posted by:
su.deep
15 years ago
Thanks to you!!!
Now I got an issue. I am trying to package a network install.
I have an msi that installs via a network. Meaning while installing it should install the core piece from say example. X: network location which actually contains all the folders and files. Which it does as per the guideline. The only thing thats not working is the shortcut. It does not point to the network location where the files are.
I am using WPS. In the working directory it points to the path but not the physical X: If I physically right click the shortcut in the program menu and point to the path which is the network drive it seems to work.
I tired to create a new shortcut but it don't let me point exactly where i want to.
Please Help!
Now I got an issue. I am trying to package a network install.
I have an msi that installs via a network. Meaning while installing it should install the core piece from say example. X: network location which actually contains all the folders and files. Which it does as per the guideline. The only thing thats not working is the shortcut. It does not point to the network location where the files are.
I am using WPS. In the working directory it points to the path but not the physical X: If I physically right click the shortcut in the program menu and point to the path which is the network drive it seems to work.
I tired to create a new shortcut but it don't let me point exactly where i want to.
Please Help!
Posted by:
AngelD
15 years ago
Posted by:
su.deep
15 years ago
Thanks for the help previously!
I have the package ready to get it deployed and i am testing on my lab machines... now an issue has arised regarding the sms deployment.... The packages gets deployed to the machine but if i check on the add remove program it don't seem to be there nor the short cuts show up on the programs menu. But the files are copied to the programfiles folder as necessary. Why does it do that?
Thanks
su.deep
I have the package ready to get it deployed and i am testing on my lab machines... now an issue has arised regarding the sms deployment.... The packages gets deployed to the machine but if i check on the add remove program it don't seem to be there nor the short cuts show up on the programs menu. But the files are copied to the programfiles folder as necessary. Why does it do that?
Thanks
su.deep
Posted by:
anonymous_9363
15 years ago
Posted by:
su.deep
15 years ago
Posted by:
anonymous_9363
15 years ago
I am new to SMS and quite didn't understand the regeditNo offence but the registry file extract I showed is just about as basic as it gets so, if you haven't understood it, your difficulties run much deeper than I have time to devote to (and it's nothing to do with SMS, BTW)
Google for "Group Policy" +"Windows installer" +logging and take it from there.
Posted by:
su.deep
15 years ago
Posted by:
anonymous_9363
15 years ago
I have an issue with deployment a package via SMS it gives me an error saying drive letter error 1327. invalid drive X:Maybe you should try posting this in the 'Deployment' forum? My guess would be, though, that SMS uses the local System account for the actual install and, as you know, System has no access to network resources.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.