Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / May 2007

Tip: Looking for answers? Try searching our database.

broken uninstall

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Charles Zhang - 11 May 2007 21:33 GMT
Due to a bug in the custom action for Uninstall, the uninstall process
is rolled back, so that I have no way to uninstall an application.

I even copied the correct custom action DLL to the target folder, I am
still having the same problem.

How could I manually fix this problem?

Thanks

Charles Zhang
Steven Cheng[MSFT] - 14 May 2007 09:59 GMT
Hi Charles,

From your description, you have a VS built setup package which has some
problem with a custom action component which always cause the setup to
rollback during uninstall time, correct?

As for the "bug", do you mean a known issue from the microsoft site or a
potential problem in your code? If the problem is mainly specific to the
custom action class, would you provide some further info on it? What code
have you used in your custom action class(especially in the uninstall
method), if possible, it would be helpful if we can create a simplified
version to repro the exact same problem.

here is a tool for custom action debugging:

#Cool MSI custom action debugging tool
http://blogs.msdn.com/astebner/archive/2005/03/07/388739.aspx

Please feel free to let me know if there is anything I missed.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.
Steven Cheng[MSFT] - 17 May 2007 03:48 GMT
Hi Charles,

How are you doing on this issue, have you got any progress? For the bug, if
it is an existing documented one, you can directly contact CSS for
dedicated support on this.  

http://msdn.microsoft.com/subscriptions/support/default.aspx

Please feel free to post here if you have anything else we can help.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.
Charles Zhang - 17 May 2007 22:20 GMT
The bug is in the custom action class. To be specific, it was in the
"Rollback" method of the class.

Later on, I fixed the bug then copied the DLL the target computer to
overwrote the one with the bug. But it did not do the trick.

I think I might have to manually change the "Setup" database maintained
by the OS. Are there any tools available?

I knows the ways to debug custom action class.

Thanks
Charles Zhang

> Hi Charles,
>
[quoted text clipped - 50 lines]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>  
Phil Wilson - 18 May 2007 19:53 GMT
If the only change you made was to fix the custom action code, and the MSI
file name is the same, you can reinstall the new MSI over the old one with:

msiexec /i  your.msi REINSTALL=ALL REINSTALLMODE=vomus

Signature

Phil Wilson
[Microsoft MVP Windows Installer]

> The bug is in the custom action class. To be specific, it was in the
> "Rollback" method of the class.
[quoted text clipped - 58 lines]
>>  This posting is provided "AS IS" with no warranties, and confers no
>> rights.
Charles Zhang - 21 May 2007 01:18 GMT
Thank.

This fixed my problems.

Charles Zhang

> If the only change you made was to fix the custom action code, and the MSI
> file name is the same, you can reinstall the new MSI over the old one with:
>
> msiexec /i  your.msi REINSTALL=ALL REINSTALLMODE=vomus

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.