Failed .NET 2.0 Framework install with error code 1935, Hresult 0x

[garybroz]

I cant sort out why I cant install the .Net Framework on Windows 2003 Server
Standard Edition. It does the same thing every time I try despite renaming
mscoree.dll and double checking permissions etc. I have installed the 2.0
Framework on 2003 Server without issue before.

The error is; Error 1935 Error installing Assembly Microsoft.VC80.CRT public
token 1fc8b3b9ale18e3b. I can see the manifest file talks about msvcr80.dll
and msvcp80.dll, but have no idea why it is failiing.

Help.......?!?!?

Thanks in advance!

[garybroz]

Waited for a bit then reininstalled the OS. It was just a development
evironment so it was ok. I reinstalled all the same functions, but changed
the order in which I did the installs, and now everything works. I installed
App Server Role first thing after OS, then ASP2.0, then SQL Server 2000 then
SQL SP3 THEN Windows Updates.

When the error below was created the only difference was that the ASP2.0
install came last. Dont know if I hit a fluke (ie not likely repeatable
issue), or a real issue with the Beta?

Hope this helps someone someday.

Post by garybroz
I cant sort out why I cant install the .Net Framework on Windows 2003 Server
Standard Edition. It does the same thing every time I try despite renaming
mscoree.dll and double checking permissions etc. I have installed the 2.0
Framework on 2003 Server without issue before.
The error is; Error 1935 Error installing Assembly Microsoft.VC80.CRT public
token 1fc8b3b9ale18e3b. I can see the manifest file talks about msvcr80.dll
and msvcp80.dll, but have no idea why it is failiing.
Help.......?!?!?
Thanks in advance!

...

[Chris Brown ()]

There are 2 downloads from microsoft
and I came across this same problem.......

Various links around the internet and abroad will talk about
the runtime!
but here's the deal- > 607 works for what was released
and then came the 907 version

Predisposed frigggen objects ect.

I was surfing the sites and finnaly figured out that
the download of the Runtime had to be within the 607 version
and not the 907

Visual Studio Developer will install on the 607
but error out with all sorts of crap on the 907 version.

SQL Express 2005 Beta
will work with either 1 but the Administrator program will
only work with the 907 aka newer version....

the beta stuff needs to be uninstalled and deleted
then reinstalled over it self !
There are many files the beta leaves over and then when you install the version that's suspose to work it will errror out
if the assemblies are still present in the same folder
and somtimes if they haven't been unregistered.

Like my error right now has to do with Microsoft.VC80.CRT
The visual Developer 8 beta 1 is failing to install and the
runtime for 607 because all the asemblies never got removed
:(

Now I have to hunt and peck through stuff and delete here and there and reregister here and there to get things to work right
lol.

Last thing that may help you
only one runtime may be present in regards to 907 and 607
all the beta stuff works fin on 607 except that webmatrix crap.
It winds up disposing objects left and right.

If you get a lock up in IIS force the 1.1 to be the master
default runtime and 2.0 to be still present
by using the
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
the file will be called aspnet_regiis.exe
this will get you out of alot of trouble :)

Look at the runtimes in
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607
C:\WINDOWS\Microsoft.NET\Framework\v2.0.40903

Good Luck..........
Most of all the beta stuff will run fine on the 607
Most of the microsoft downloads are the 907 version


**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...