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 / Languages / Managed C++ / May 2005

Tip: Looking for answers? Try searching our database.

Installation oddies with Beta 2 of languages

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dann Corbit - 03 May 2005 20:28 GMT
Several fascinating problems have occurred with attemped installations of the
latest beta 2 versions of the .NET languages (including VC++).

mscorsvw.exe has been using 99% of my CPU for 17 hours.  More than one
billion page faults have occurred.  Here is an image of the Windows Task
Manager:
ftp://cap.connx.com/pub/mscorsvw-is-not-my-friend.jpg

In addition, I am now in a remarkable catch-22 situation.  Somehow, the one
beta product that did not get removed during my following of the installation
instructions for the new products was "Microsoft MSDN Express Library 2005
Beta - English"
and yet the .NET 2.0 Beta was removed.  So, when I try to remove the product
"Microsoft MSDN Express Library 2005 Beta - English" it crashes every time.

There seems to be no way to remove that product from my machine.

Interestingly, it is also impossible to install any of the new tools while
that product is still installed.

I suggest that the installations of these tools can be improved.
Jochen Kalmbach [MVP] - 03 May 2005 20:39 GMT
Hi Dann!

> There seems to be no way to remove that product from my machine.
>
> Interestingly, it is also impossible to install any of the new tools while
> that product is still installed.
>
> I suggest that the installations of these tools can be improved.

No. I suggest that you should be aware of the word "beta"!

Signature

Greetings
  Jochen

   My blog about Win32 and .NET
   http://blog.kalmbachnet.de/

Dann Corbit - 03 May 2005 20:48 GMT
> Hi Dann!
>
[quoted text clipped - 6 lines]
>
> No. I suggest that you should be aware of the word "beta"!

Point taken.  I certainly can expect strange happenings when installing beta
products.  For that reason, I installed on a secondary machine rather than my
normal development box.

Be that as it may, I do hope that there is some way to recover other than
"reformat"

Has anyone a useful notion as to how I may move forward?
Carl Daniel [VC++ MVP] - 03 May 2005 22:53 GMT
>> Hi Dann!
>>
[quoted text clipped - 15 lines]
>
> Has anyone a useful notion as to how I may move forward?

1. Get the Windows Installer Cleanup Utility.
   http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

2. Delete the installer packages for all of the .NET 2.0 and VS 2005
products installed on your machine.

3. Delete all of the directories where .NET 2.0 or VS 2005 products were
installed.

4. Reboot

5. Re-install

If that doesn't work, you're down to nuking it from space - it's the only
way to be sure.

-cd
Dann Corbit - 03 May 2005 23:18 GMT
> >> Hi Dann!
> >>
[quoted text clipped - 31 lines]
> If that doesn't work, you're down to nuking it from space - it's the only
> way to be sure.

Unfortunately, I installed:
WindowsInstaller-KB884016-v2-x86.exe
as recommended by the SQL*Server beta.

It seems that this is incompatible with other tools, such as the "Windows
Installer Cleanup Utility."

If I should somehow become bold/loony enough to try again to install the
betas, is it a bad idea to install the SQL beta together with the .NET betas?

If so, then I would suggest moving the SQL beta to another area, or
mentioning the incompatibility.

If not, then procedures which can be followed even by a nitwit would be nice
for nitwits like me.
Carl Daniel [VC++ MVP] - 03 May 2005 23:49 GMT
>> If that doesn't work, you're down to nuking it from space - it's the
>> only way to be sure.
[quoted text clipped - 5 lines]
> It seems that this is incompatible with other tools, such as the
> "Windows Installer Cleanup Utility."

Bummer.  Hopefully they'll produce an updated version of the cleanup tool.

> If I should somehow become bold/loony enough to try again to install
> the betas, is it a bad idea to install the SQL beta together with the
> .NET betas?

No, they're fine together, but make sure you only install "matched sets"
(e.g. VS 2005 beta 2 and SQL Server 2005 April CTP), and always install SQL
Server first.

-cd

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.