dotnetfx_cleanup_tool

  • Thread starter Thread starter Tom Penharston
  • Start date Start date
T

Tom Penharston

I have an open case with Microsoft where all outcomes are riding on
the .NET Framework Cleanup Tool (current version 6.00.3790). I think
it's a very useful tool but it's not working exactly as I need it to.
I'm running Windows Server 2003 Standard x64 SP2.

I sent dozens of screenshots to MS including my cleanup procedure, re-
installation, and error event IDs. Each time I got a response with
slightly modified instructions to download and run the tool yet again.

So, I've run the tool many times over the last three weeks. Lately
I'm trying it with my various apps and services disabled: SQLExpress,
SQL Backup Exec (11d), Symantec Endpoint Protection Manager (11),
Quickbooks database Service (9). My results are nearly identical
whether services are running or disabled.

Lately, after I "successfully" clean all versions of .NET Framework,
Add/Remove programs still displays versions 1.1 and 3.5 present on the
server. Oddly enough, the Windows Installer Cleanup does not show
that they are available for removal. Clearly the two tools do not
agree on reg keys or other files. I have no baseline to tell me when
a version of .NET is actually removed.

Immediately after restart all of my services try to run once again.
I'm greeted with a general Microsoft Visual C++ Runtime Error which
seems to be okay. I'm not sure which app or service is popping the
error, but it goes away after reinstall .NET Framework, so at least
one application is satisfied.

Unfortunately I can't a get a perfectly clean re installation. I've
tried reinstalling .NET Framework two different ways: Automatic
Updates and the 3.5 redistributable. Both methods report "success"
but immediately after re installation I'm prompted for automatic KBs
which fail, including KB 953297 and 951847. No amount of restarts
clears the issue. I can only hide the updates. According to
Microsoft tech support this indicates that the installations were not
clean.

Various app components have been failing through out this process. I
first noticed failure of Symantec LiveUpdate coinciding with .NET
Framework 2 SP 2 errors, knock on wood this particular error cleared
up and LiveUpdate ran a couple of times, but another feature of Backup
Exec, Remote Agent Wizard, has been completely compromised; it hasn't
run for a month. I've corresponded with Symantec over the phone and
email. It seems like I need to clear all .NET Framework errors and
updates before I can get a level playing field. Endpoint Protection
Manager was completely frozen twice since this issue began; and I had
to do a full re installation both times.

The download page for SQL Express 2005 indicates that .NET Framework
2.0 is a requirement for SQL Express. That connection is easy to
make. It's been a lot more difficult to make the other connections.
I still don't know exactly which Symantec apps require which .NET
versions. I'm going on faith that I need a clean removal and a clean
installation of version 3.5.

I think the problem is that the free Cleanup Tool isn't accurate
enough for my scenario, and MS support still isn't providing an
officially sanctioned alternative.

Are there any steps I can take to prepare the server, prior to running
the tool?

Are there ways to remove .NET Framework manually with little risk?

This issue is costing the company in terms of user productivity and
support hours.

Thanks for your advice,
Tom Penharston
 
I suspect MS would have told you all that I am about to list...


Tom said:
I have an open case with Microsoft where all outcomes are riding on
the .NET Framework Cleanup Tool (current version 6.00.3790). I think
it's a very useful tool but it's not working exactly as I need it to.
I'm running Windows Server 2003 Standard x64 SP2.

I sent dozens of screenshots to MS including my cleanup procedure, re-
installation, and error event IDs. Each time I got a response with
slightly modified instructions to download and run the tool yet again.

So, I've run the tool many times over the last three weeks. Lately
I'm trying it with my various apps and services disabled: SQLExpress,
SQL Backup Exec (11d), Symantec Endpoint Protection Manager (11),
Quickbooks database Service (9). My results are nearly identical
whether services are running or disabled.
Click to expand...


At least Symantect EPM depends on IIS. After uninstalling/reinstalling,
etc, it would seem likely the default version of ASP.Net is not set
correctly.

Lately, after I "successfully" clean all versions of .NET Framework,
Add/Remove programs still displays versions 1.1 and 3.5 present on the
server. Oddly enough, the Windows Installer Cleanup does not show
that they are available for removal. Clearly the two tools do not
agree on reg keys or other files. I have no baseline to tell me when
a version of .NET is actually removed.
Click to expand...


Have you looked (or been told to look at) the Microsoft Installer
Cleanup Utility? http://support.microsoft.com/kb/290301.


Immediately after restart all of my services try to run once again.
I'm greeted with a general Microsoft Visual C++ Runtime Error which
seems to be okay. I'm not sure which app or service is popping the
error, but it goes away after reinstall .NET Framework, so at least
one application is satisfied.

Unfortunately I can't a get a perfectly clean re installation. I've
tried reinstalling .NET Framework two different ways: Automatic
Updates and the 3.5 redistributable. Both methods report "success"
but immediately after re installation I'm prompted for automatic KBs
which fail, including KB 953297 and 951847. No amount of restarts
clears the issue. I can only hide the updates. According to
Microsoft tech support this indicates that the installations were not
clean.
Click to expand...


Have you looked at the "Known Issues" sections here
http://support.microsoft.com/kb/953297, and here
http://support.microsoft.com/kb/951847?

Various app components have been failing through out this process. I
first noticed failure of Symantec LiveUpdate coinciding with .NET
Framework 2 SP 2 errors, knock on wood this particular error cleared
up and LiveUpdate ran a couple of times, but another feature of Backup
Exec, Remote Agent Wizard, has been completely compromised; it hasn't
run for a month. I've corresponded with Symantec over the phone and
email. It seems like I need to clear all .NET Framework errors and
updates before I can get a level playing field. Endpoint Protection
Manager was completely frozen twice since this issue began; and I had
to do a full re installation both times.

The download page for SQL Express 2005 indicates that .NET Framework
2.0 is a requirement for SQL Express. That connection is easy to
make. It's been a lot more difficult to make the other connections.
I still don't know exactly which Symantec apps require which .NET
versions. I'm going on faith that I need a clean removal and a clean
installation of version 3.5.

I think the problem is that the free Cleanup Tool isn't accurate
enough for my scenario, and MS support still isn't providing an
officially sanctioned alternative.

Are there any steps I can take to prepare the server, prior to running
the tool?

Are there ways to remove .NET Framework manually with little risk?
Click to expand...

What shows under the folder %WINDOWS%\Microsoft.Net after you have
completely uninstalled using the cleanup tools?
 
Thanks Mike,
Microsoft did not provide your level of detail.

I suspect MS would have told you all that I am about to list...

At least Symantect EPM depends on IIS.  After uninstalling/reinstalling,
etc, it would seem likely the default version of ASP.Net is not set
correctly.
Click to expand...

Where does IIS report the default version of ASP.NET?
Have you looked (or been told to look at) the Microsoft Installer
Cleanup Utility?  http://support.microsoft.com/kb/290301.
Click to expand...

Yes, msicuu2 has been the least helpful utility in all of this, but I
keep going back to it as a reference. I have three ways to check
currently installed versions (1) Add Remove Programs (2) msicuu2 (3)
\Windows\microsoft .net directories.
Have you looked at the "Known Issues" sections here http://support.microsoft.com/kb/953297, and here http://support.microsoft.com/kb/951847?
Click to expand...

KB953297 describes my situation. I didn't get the exact Event IDs
mentioned in the article, but it's still a good reference.
What shows under the folder %WINDOWS%\Microsoft.Net after you have
completely uninstalled using the cleanup tools?
Click to expand...


This is a great question. I've tried every combination of removal
tools (1) Add Remove Programs (2) msicuu2.exe (3) and the .NET
Framework Setup Cleanup Utility. Here's shows after I'm done
"cleaning":

C:\WINDOWS\microsoft.net\authman\1.2
C:\WINDOWS\microsoft.net\Framework\v1.1.4322
C:\WINDOWS\microsoft.net\Framework\v2.0.50727
C:\WINDOWS\microsoft.net\Framework64\v2.0.50727

Add or Remove Programs
Microsoft .NET Framework 1.1
Microsoft .NET Framework 3.5 SP1
Update for Microsoft .NET Framework 3.5.SP1 (KB963707)
Hotfix for Microsoft .NET Framework 3.5.SP1 (KB958484)
Hotfix for Microsoft .NET Framework 3.5.SP1 (KB953595)

Windows Install Cleanup Utility (msicuu2.exe) shows nothing left
from .NET Framework.

Please note that the .NET directories above do not match Add Remove
Programs. Add/Remove is hung up on version 3.5. The directory is
still showing 2.0 for both i86 and x64. They both agree on 1.1.

I'm not sure what to try next.

Thanks for your response,
-Tom Penharson
 
I previously wrote, "...the .NET Framework Cleanup Tool (current
version 6.00.3790). I got that version number from the installer
properties. It's just a cab extractor. I think I should go with the
build date in the history file to eliminate any confusion. The
current build date is October 29th 2009 for Aaron Stebner's utility.
http://blogs.msdn.com/astebner/pages/8904493.aspx

Also, KB923100 describes the steps that I'm taking"
http://support.microsoft.com/kb/923100/ Microsoft responded to my
case with very similar steps. This article is the source of my
redistributables.

I just made some progress with 3.5, but 1.1 is still a problem. I'll
report back soon.
 
Tom said:
I previously wrote, "...the .NET Framework Cleanup Tool (current
version 6.00.3790). I got that version number from the installer
properties. It's just a cab extractor. I think I should go with the
build date in the history file to eliminate any confusion. The
current build date is October 29th 2009 for Aaron Stebner's utility.
http://blogs.msdn.com/astebner/pages/8904493.aspx

Also, KB923100 describes the steps that I'm taking"
http://support.microsoft.com/kb/923100/ Microsoft responded to my
case with very similar steps. This article is the source of my
redistributables.

I just made some progress with 3.5, but 1.1 is still a problem. I'll
report back soon.
Click to expand...

Sorry, I'm just coming up for air from my daytime hobby...

Previously you asked about the .Net version for asp.net. You can set
that in the "Default Website" properties tab on the ASP.Net settings.
There is a dropdown for each version, 2.0.50272 or 1.1.4322.

Also, I think I would have blown away anything under
%windows%\Microsoft.Net, after having supposedly uninstalling the
frameworks, and then rebooted. That should convice the installers that
the frameworks aren't there, even if the control panel thinks they are
there.

I hope you have made more progress/success.
 
Back
Top