ICE+Errors

//Not a standard action and not found in CustomAction or Dialog tables// - The Wisecall custom action is added with the merge module if it’s not already in the wise package. This exists in almost all the CTC packages.
 * //Unknown action: 'WiseCall' of InstallExecuteSequence table.//

Errors relating to non-advertised shortcuts or the CTAPPS shortcuts folder:

Both of these errors can be ignored if the component installs to either the CTAPPS shortcuts folder or a subfolder of CTAPPS as the folder will install to the all users profile due to the use of the property ALLUSERS=1.
 * //Component  installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file.//
 * //Component  has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file.//

As above, if the component is relating to the CTAPPS shortcut then this error can be ignored. However if the component contains registry keys in HKCU as well as per-machine data (i.e. HKLM registry keys, files, folders) then this is a failure. HKCU registry keys should be associated to a separate component called HKCU or CurrentUser, or something to that affect.
 * //Component  has both per-user and per-machine data with a per-machine KeyPath.//

This can be ignored as it relates to the fact that a x64 custom action is being used in the package when the package specifies an x86 platform in the package template summary. Normally x64 MSI actions would only be contained in a x64 package, otherwise the actions would install to the x86/WOW environment within the Win7 x64 OS. Since the custom action is the only x64 element of the package then this is not a concern.
 * //This package contains 64 bit custom action script  but the Template Summary Property does not contain Intel64 or x64//.

// The directory name: WindowsVolume is the same as one of the MSI Public Properties and can cause unforeseen side effects. //

This occurs when there is an entry in the Directory table for WindowsVolume which is effectively the same as the public property ROOTDRIVE=C:\. Normally, Wise uses the WindowsVolume entry only when TARGETDIR cannot be used to create a folder path on the ROOT. The unforeseen side affects it speaks of occur when you set the ROOTDRIVE property to a drive that is not the same as the current WindowsVolume. For example; in a Citrix environment where the apps may be installed to D:\Apps and the WindowsVolume is still C:\, then when installing the package Windows installer will not be able to determine which drive letter it should use. Since we always use ROOTDRIVE=C:\ and since the WindowsVolume is also always C:\ then this is not a concern and therefore can be ignored.