How To Resolve Ice64 Error
09/06/2005 Software Deployment Package Development Ok, another Newbie Question waring. I purchased The "Repackaging and Application Migration using AdminStudio" course. The course came with a disk containing sample projects (exercises). I have been trying to work with the "Sample App 3000" ism file. I ran the "Full MSI Validation Suite" under the Build > Validate menu as the course instructs to do. I receive the following error: The directory SAMPLE_APP1 is in the user profile but is not listed in the RemoveFile table. http://dartools/iceman/ice64.html Directory Directory SAMPLE_APP1 Error Code: ICE64 Don't ask me what the web address is about I haven't a clue. When I double click the error I am taken to the Direct Editor "Directory" table. Highlighted in "red" is the following information. There are other columns but those are blank so I didn't include them here. Directory - (s72) = SAMPLE_APP1 Directory_Parent -(S72) = PersonalFolder DefaultDir -(l255) = SAMPLE~1|Sample App ISAttributes -(14) = 0 The data above is actually formatted in Rows and Columns in the editor but because the formatting doesn’t hold up in a simple text editor I rearranged it into a simple list When I navigate to the RemoveFiles table I see this: Once again these are actually column headings FileKey -(s72) Component_-(S72) FileName -(L255) DirProperty - (S72) InstallMode - (i2) It is my understanding that if I want to remove a folder I should leave the file columns blank. When I click on the Component column I get a drop down menu so I must choose one of the predefined properties. None of the properties I can choose from correspond to what I'm seeing in the "Directory" table. Its also my understanding that if I want the file removed during an uninstall I need to set the InstallMode = 2. No matter what I put in the columns under the RemoveFile table I keep getting the same "The directory SAMPLE_APP1 is in the user profile but is not listed in the RemoveFile tab
do stress hints) as to what to do with specific ICE error messages. If you go into my tutorial you'll see that some ICE errors can disappear by fixing other ICE errors. With practise, you'll be able to feel-your-way to resolve most if not all ICE errors. The SDK also hints how to fix these ICE errors. Just click the SDK icon and search like this: ICE38 not: ICE 38 ICE02 (Taken from Wise newsgroups) > Registry: 'primarykey' cannot be the key registry key for > Component: 'PerMachine'. The RegKey belongs to > Component: 'notes.exe' http://dartools/iceman/ice02.html > Component KeyPath PerMachine > Evaluation: ICE02 To fix this, go to the Setup Editor page and the Components tab. Browse down to http://www.itninja.com/question/error-ice64-and-the-removefile-table the component named "PerMachine" (which might even be highlighted in red) and right-click, choose "Details". Under the "Key Path Type:" drop-down, choose "File Key Path", and then choose any file from the "File Key Path:" drop-down just below it. > The directory Lotus_Applications is in the user profile but is not listed in the RemoveFile table. > http://dartools/iceman/ice64.html Directory Directory > Lotus_Applications > Evaluation: ICE64 This one is simply what it says... During the install, the "Lotus Applications" folder is created http://www.dawnstar.com.au/wpshelp/procedures/fix_ice.html in the Start Menu. If you want to delete it during the Uninstall, add it to the RemoveFile table. (Follow the examples in the RemoveFile table and the directions in the MSI Help.) ICE33 ICE33 warnings are next to impossible to fix. The warning message hints to use the ProgId and Class tables. Discussing with other peers reveals that any attempt to fix ICE33 warnings are futile and will break the package. For John_McFadyen, ICE33 warnings are not so impossible to fix: When you have an ICE33 error, you can find the relevant inprocsvr32 key for that error. Then trace it back to the DLL which owns the COM registration. Remove the DLL from the package, register it on the local machine [using regsvr32] then import it back into the package. (in some cases you may wish to keep the component code) which is another step. On import, Wise will correctly pick up the ProgId/Class details. You may be required to select rescan COM data from the components view and you will find Wise correctly allocates the COM tables. The [ICE Error causing] registry data can then be safely removed. ICE38 ICE38 states that any component that installs to the user profile must have a registry key as its KeyPath. You have 2 ways to fix this: -Create a bogus entries in registry in the HKCU and make them part of the component causing the error. -Steal (aka move) a HK
error. ICE23:--------CAUSE:ICE23 posts an error message if the tab order of controls does not form a single closed loop in the dialog box. SOLUTION:The fix for http://poornnimaa.blogspot.com/2011/07/fix-for-ice-error-2360-and-64.html this problem is to change the value of the "Control_Next" column of the http://geekswithblogs.net/EltonStoneman/archive/2008/12/12/wix-errors-ice50-and-ice64-again.aspx error dialog to "InstallNow". ICE60:--------CAUSE:ICE60 checks that files in the File table meet the following condition:If the file is not a font and has a version, then it must have a language. ICE60checks that no versioned files are listed in the MsiFileHash table. SOLUTION:Below are the steps to fix the first case: 1. how to Double click on the error and find the file. 2.Add "0" to the "Language" column of that file in the file table. Below are the steps to fix the second case: 1. Double click on the error and find the file causing the error in the "MsiFileHash" table. 2. Delete the entire row. CAUSE: ICE64 posts a warning or an error in a roaming situation if a how to resolve new directory in the user profile that should be removed is not removed. SOLUTION: To fix this, we need to create a row forthat folder in the RemoveFile table. Below are the steps to fix ICE64. Double click on the error message and find the directory causing the error. Copy the name of the Directory and find the component in which it resides. Goto "RemoveFile" table and add a new row. FileKey - Specify the name of the directory(The directory name which has been copied). DirProperty - Specify the same name givenin FileKey Column. Component_ - Specify the component in which thedirectory resides. InstallMode - 2 (Settingit to2 is meant to remove it at the package removal time). FileName - Can be left blank. ICE64:-------- Posted by Poornnimaa at 03:00 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Followers Blog Archive ▼ 2011 (76) ► August (1) ▼ July (44) Installing msi with if condition using wise script... How to package Adobe Photoshopelements 8.0 How to package AdobePhotoshop elements 9 using wis... Installing adobereader apps with multiple msp file... Install and uninstall Adob
2000AD.My Pluralsight CoursesReal World Big Data in AzureJune 2015 | Getting Started with Ubuntu February 2015 | Five Essential Tools for Building REST APIs December 2014 | Executable Specifications: End-to-End Acceptance Testing With SpecFlowAugust 2014 | IDisposable Best Practices for C# DevelopersJune 2014 | Message Queue Fundamentals in .NETApril 2014 | C# Extension Methods December 2013 | Implementing the Reactive Manifesto with Azure and AWS October 2013 | Nginx and PHP Fundamentals July 2013 | Caching in the .NET Stack: Inside-Out June 2013 | My Other Recent Posts Getting Started with Ubuntu Submitting HDInsight Storm Applications from Visual Studio - Gotcha! Versioning in WebAPI using Route Constraints Out now: www.essentialresttools.net, tools for building better REST APIs Five Essential Tools for Building REST APIs Configure Azure storage to return proper response headers for blob GETs Databases? Where we're going, we don't need databases Executable Specifications: End-to-end Acceptance Testing with SpecFlow badapi.net just got badder Welcome to www.badapi.net, a REST API with badly-behaved endpoints News This is the *old* blog. The new one is at blog.sixeyed.com Post Categories TFS Visual Studio SQL Server Metrics Code Analysis Code Coverage Workitems MSDN Live 2010 Code Contracts Build Branching MTM Testing Extensions Unit Testing IFix Git NuGet NUnit Archives August 2015 (2) July 2015 (4) June 2015 (3) May 2015 (1) February 2015 (2) December 2014 (3) October 2014 (2) September 2014 (2) August 2014 (1) July 2014 (1) June 2014 (4) May 2014 (1) April 2014 (2) February 2014 (1) January 2014 (1) December 2013 (5) November 2013 (2) October 2013 (6) September 2013 (1) August 2013 (2) July 2013 (2) June 2013 (1) April 2013 (4) November 2012 (2) October 2012 (1) September 2012 (4) August 2012 (1) May 2012 (2) April 2012 (2) January 2012 (2) December 2011 (2) October 2011 (3) September 2011 (2) June 2011 (2) May 2011 (2) March 2011 (3) October 2010 (3) September 2010 (1) August 2010 (4) July 2010 (4) June 2010 (1) May 2010 (3) April 2010 (3) November 2009 (7) October 2009 (2) September 2009 (7) June 2009 (4) May 2009 (3) April 2009 (4) March 2009 (8) February 2009 (4) January 2009 (2) December 2008 (6) November 2008 (2) October 2008 (6) September 2008 (6) July 2008 (4) June 2008 (6) May 2008 (4) April 2008 (10) Elton Stoneman This is the *old* blog. The new one is at blog.sixeyed.com << Networking Virtual PCs with the Same Computer Name | Home | Generic WCF Error Handler for ESB Guidance >> Wix Errors ICE50 and ICE64 Comments (22) | Share [Source: http://geeks