Uninstall 1.1 SP1 on Server 2003

  • Thread starter Thread starter Jens Thiel
  • Start date Start date
J

Jens Thiel

Hello,

I would like to uninstall the SP1 "critical update" on a Server 2003, but I
can not figure out how to do it. Any idea?

TIA,

Jens.
 
Uninstall the entire framework, reinstall a pre sp1 version.

Why?

Check your application event log for warnings/errors on the install of the
service pack. Most of the SP1 problems are correctable.

Mike
 
Mike Marsh said:
Uninstall the entire framework, reinstall a pre sp1 version.
Click to expand...

How? It's "part of the OS". There is no uninstall option, and I can't
reinstall either.
Why?
Click to expand...

A strange problem: I have a software partially created with managed C++.
Before SP1, the app worked on other installations (different OS, Net 1.1 +
2.0 beta, different Excel versions). Now, it only works on the above SP1
setup and I get the strangest errors on the others. When compiling the same
source (from CVS) on another computer, the errors are gone.
Check your application event log for warnings/errors on the install of the
service pack. Most of the SP1 problems are correctable.
Click to expand...

The SP1 itself installed succesful.

Jens.
 
To answer my own question:

Deinstall KB833987 and KB867460. Reboot. Reinstall KB833987.

The compilation problems described earlier have vanished. Strange, he?

Jens.
 
you mentioned the compiling it on other pc !!! did it have sp1 installed by
any chance ? you mentioned 1.1 & 2.0

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
Jens Thiel said:
To answer my own question:

Deinstall KB833987 and KB867460. Reboot. Reinstall KB833987.

The compilation problems described earlier have vanished. Strange, he?

Jens.
Click to expand...
 
The machine used for compilation was Server 2003 with 1.1 SP1 framework
(install was logged as succesfull) and resulted in non-deterministic
execution errors on other machines having different OS, 1.1 and 2.0
framework combinations. The problem did not occur before the critical update
and vanished after uninstalling. I guess the managed C++ compiler has,
beyond many others, a problem with SP1 somehow.

Jens.

--
http://ManagedXLL.net/
Replace MSDN with my first name when replying to my email address!


Hermit Dave said:
you mentioned the compiling it on other pc !!! did it have sp1 installed by
any chance ? you mentioned 1.1 & 2.0

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
Jens Thiel said:
To answer my own question:

Deinstall KB833987 and KB867460. Reboot. Reinstall KB833987.

The compilation problems described earlier have vanished. Strange, he?

Jens.
Click to expand...
1.1
Click to expand...
 
Hi Jens,

The problem is strange, we can not reproduce the problem on w2k3 with .net
framework sp1 installed. I have searched our internal website and find
nothing about the similar problem. If you can reproduce the problem on
other w2k3 it may be a problem in the .net framework sp1. Since the problem
is somewhat complex, which may need further detailed troubeshooting, if you
still have any concern on this issue I suggest you contact MS PSS for help.

http://support.microsoft.com

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
I agree with Peter's suggestion. Once is a happtence, twice a coincidence,
third time you know you cant be wrong.

It it a try on a clean win2k3 box with 1.1 with sp1 on it. If you still have
problems contact MS at the support Url, that way we can have a bug
confirmation and a resolution in future.

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
 
Hi Jens,

I can't find KB833987, are you sure the number is correct?
I have a problem that my dotnet app is now very slow on the server after sp1
(on xp clients it is running as before). So I like to uninstall also but
can't find any article on it.

Thanks
Bart

Jens Thiel said:
To answer my own question:

Deinstall KB833987 and KB867460. Reboot. Reinstall KB833987.

The compilation problems described earlier have vanished. Strange, he?

Jens.
Click to expand...
 
Sorry, guys. I already spent a weekend on a) finding out what is going wrong
b) finding out how to uninstall that damn thing. No time left to setup a
clean box + recommended updates + Office + VS + other build tools.
 
Hi Jens,

Yes, it is somewhat time-consuming to build such an test environment. But I
think you may simple try to run the application on another machine to see
if the problem persists, which may isolate the problem to machine specific
or code specific since sp1 has added some new features including the
security ones which may prevent the underlying harmful code from running.

Anyway I think you may try to make a simple reproduce sample together with
detailed reproduce steps and send to me by removing the "online" from my
email address.
Just an suggestion, contacting MS PSS will be another approach, if we
confirm this is a problem in our product, you will be refund.

I look forward to your reply.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
"Peter Huang" said:
Yes, it is somewhat time-consuming to build such an test environment. But I
think you may simple try to run the application on another machine to see
if the problem persists, which may isolate the problem to machine specific
or code specific since sp1 has added some new features including the
security ones which may prevent the underlying harmful code from running.
Click to expand...

Hi Peter, to resume, the problem was as follows:

A) Original Setup: Server 2003 + NET 1.1 + VS2003

The application compiled (involving native C++, managed C++ and C#) on this
machine would run on this machine and different test platforms (NT, 2000,
XP; 1.1 and 2.0b1 frameworks).


B) Setup after crititcal update: Server 2003 + NET 1.1 SP 1 + VS2003

When compiling the same source, the application would only run on this
machine and fail on ALL test platforms, on-site and at a client. Compiling
the same source on another developer machine (2000+NET11+VS2003) would still
run on all test platforms and the SP1 machine.

The solution has been cleaned, freshly checked out, the machine booted
inbetween. The code has been Debugged, Purified, etc. without any result.
The problem persisted.


C) Setup after uninstalling the SP1

Problem vanished; like A)
Anyway I think you may try to make a simple reproduce sample together with
detailed reproduce steps and send to me by removing the "online" from my
email address.
Just an suggestion, contacting MS PSS will be another approach, if we
confirm this is a problem in our product, you will be refund.
Click to expand...

I know that a repro case would be best here, but the errors I got could not
be pinned to a certain construct. The errors on the different platforms were
similar and always in managed C++ code, but not the same and not at the same
location. For this reason, I did not try to isolate the problem.

My guess is that the managed C++ compiler has a problem with SP1. I
personally decided to stay away from SP1 for developing purposes.

Thank you very much,

Jens.
 
Hi Jens,

Thank for your detailed information.
Since I did not find any known issue for this problem, I was not able to
figure out what is the matter. Maybe the SP1 is just released, I did not
excluding the possibility that there is problem in the sp1. But without a
reproduce, I can not do further troubleshooting for the problem

I also have tried to compile a simple c# and MC++ program on a windows 2003
+ .net fw 1.1+SP1, and I can run the program on other machine, e.g.
xp,windows 2000.
If you can reproduce the problem with simple C# program(C# program's IL
code is simple than MC++ in the ildasm tool), I think you may try to backup
two compiled exe together with the symbol file(*.pdb) which are compiled on
two machines with or without SP1.

You may try to use the ildasm.exe tool to open the two file and observe
their il code to see if there is any difference.
we can find the tool in the path below.
C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
KB833987 is the GDI+ update, you might not have downloaded that one. I
didn't even bother to uninstall it. I just uninstalled the SP (KB867460) and
everything seems fine.

Bart said:
Hi Jens,

I can't find KB833987, are you sure the number is correct?
I have a problem that my dotnet app is now very slow on the server after sp1
(on xp clients it is running as before). So I like to uninstall also but
can't find any article on it.

Thanks
Bart
Click to expand...
 
No. I am not using VC++ in .NET. I was just getting a strange warning when
opening an ASP.NET project for editing and I saw a lot of problems that other
people were having and I decided that now would not be the time.
 
Back
Top