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
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