1402 Error During Uninstallation of Certain MSI Products
Updated: 09 Sep 2009 | 1 comment
Scenario when this happens :
When we perform Uninstallation of an msi using a deployment tool when the user is not logged in \ non admin user is logged in
Error Log says :
Product: Roxio Media Manager -- Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference. System error 87. Verify that you have sufficient access to that key, or contact your support personnel. Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference. System error 87. Verify that you have sufficient access to that key, or contact your support personnel.
Solution :
Opening up the specific registry keys for the users .HKEY_LOCAL_MACHINE\SOFTWARE\Roxio
Opening up the specific registry keys for the users .HKEY_LOCAL_MACHINE\SOFTWARE\Roxio
blog entry Filed Under:
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Configuring Altiris Client Management Suite Altiris Deployment Solution Symantec Management Platform (Notification Server) Wise Packaging Basics Altiris Server Management Suite Best Practice Compatibility Tip/How to Helpdesk Solution Altiris IT Asset Management Installing Workflow Solution Ghost Solution Suite Windows Reporting Performance Upgrade Features ServiceDesk 7.x Database Agents Dell Management Products
Comments
Something is wrong with your package or your deployment solution
The account used by your deployment solution should be running with local admin privileges and therefore should not have any restrictions on the HKLM/Software/Roxio/Preference registry key, unless someone has used lockpermissions and forgotten to add back the administrators group.
Although the solution of opening up the specific registry keys does solve this issue, it does not resolve the underlying problem that caused this issue in the first place.
I would recommend investigating the Roxio package first, to see if the problem is caused by bad packaging (either by the vendor or subsequently).
From what I recall, Roxio has a long history of being a very flaky package to install.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.