Microsoft .Net 4.0 – Installation – Problems – Considering drive:….

Microsoft .Net 4.0 – Installation – Problems – Considering drive:….

We have this server with a bad-drive that has being slowly dying.

Thanks to Storage Vendor’s Smart Technology we had plenty of time and we knew the end will be any day now.

Last weekend added a new drive.  As the machine has two hard-drives bay thought why not keep the current drive and just add a new one and hopefully copying old data files from old drive to new one will be a bit easier.

So being struggling to get applications installed on this machine all week long.

Today it is Microsoft .Net Framework 4.5

Downloaded the Framework and launched it.

But, it disappeared to Timbuktu.

Tried again a few times, but same thing.  I can prove it…The numerous retries are in “Task Manager”.  So as the app remains in “Task Manager” and so I know they am not dead, just stuck.

So stopped the “aborted” the unsuccessful tried installing a few times.
Googled for aborted, stopped, “Window never appears” Microsoft .Net Install.

Nothing really.

So like Nathalie Makoma – Talk with God – “http://www.dailymotion.com/video/x4k1np_nathalie-makoma-talk-with-god_music“, or rather unlike her, Googled some more.

This time … Googled for “Microsoft .Net ” “Log file”.

This time got clear guidance on where “Microsoft .Net” keeps its log file.

Log files are kept in whatever entry is designated via environment variable as your Temp Folder.

So off I went to clear my current Temp Folder, re-launched the setup, and thanks Goodness now I have a log file that can make me bright.

The complete, post successful install log file is pasted below:

[9/15/2012, 10:14:25] === Logging started: 2012/09/15 10:14:25 ===
[9/15/2012, 10:14:25] Executable: C:\downloads\Microsoft\Microsoft.Net\v4.5\dotnetfx45_full_x86_x64.exe v4.5.50709.17929
[9/15/2012, 10:14:25] --- logging level: standard ---
[9/15/2012, 10:14:25] Successfully bound to the ClusApi.dll
[9/15/2012, 10:14:25] Error 0x80070424: Failed to open the current cluster
[9/15/2012, 10:14:25] Cluster drive map: ''
[9/15/2012, 10:14:25] Considering drive: 'C:\'...
[9/15/2012, 10:14:25] Considering drive: 'D:\'...
[9/15/2012, 10:14:25] Considering drive: 'E:\'...
[9/15/2012, 10:14:25] Considering drive: 'F:\'...
[9/15/2012, 10:14:25] Considering drive: 'G:\'...
[9/15/2012, 10:27:18] Drive 'G:\' is rejected because it can't be written to
[9/15/2012, 10:27:18] Considering drive: 'I:\'...
[9/15/2012, 10:27:18] Drive 'I:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'J:\'...
[9/15/2012, 10:27:18] Drive 'J:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'K:\'...
[9/15/2012, 10:27:18] Drive 'K:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'L:\'...
[9/15/2012, 10:27:18] Drive 'L:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'M:\'...
[9/15/2012, 10:27:18] Drive 'M:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'N:\'...
[9/15/2012, 10:27:18] Drive 'N:\' is rejected because of the unknown or unsuitable drive type
[9/15/2012, 10:27:18] Considering drive: 'R:\'...
[9/15/2012, 10:27:18] Drive 'E:\' has been selected as the largest fixed drive
[9/15/2012, 10:27:18] Directory 'E:\42e5d087791f32b39bd436\' has been selected for file extraction
[9/15/2012, 10:27:18] Extracting files to: E:\42e5d087791f32b39bd436\
[9/15/2012, 10:27:28] Extraction took 9.625 seconds
[9/15/2012, 10:27:28] Executing command line: 'E:\42e5d087791f32b39bd436\\Setup.exe   /x86 /x64'
[9/15/2012, 10:32:12] Exiting with result code: 0x0
[9/15/2012, 10:32:12] === Logging stopped: 2012/09/15 10:32:12 ===

Starting from [9/15/2012, 10:14:25] to [9/15/2012, 10:27:18] – 13 minutes – the Installation along with MS Windows tried accessing folders on the old drive.

Yes, one drive, Drive G:, took most of that time.  That drive is probably not recognizable / formatted for MS Windows.

Now I know all I needed was to have and hold faith for 15 minutes.

Finding a way to disable the bad drive via BIOS will happen once I Google some more.

For now, I am trying to see if “Disabling the device” via “Disk Management” will hold.

References:

  1. Troubleshooting Blocked .NET Framework Installations
    http://msdn.microsoft.com/en-us/library/hh925569.aspx
  2. Troubleshooting .Net Install Failures
    http://blogs.msdn.com/b/varungupta/archive/2010/06/22/troubleshooting-net-framework-4-install-failures.aspx?PageIndex=3
  3. Aaron Stebner’s Web Log
    http://blogs.msdn.com/b/astebner/archive/2010/05/12/10011664.aspx
  4. How to remove a logical drive
    http://www.ehow.com/how_5993437_remove-logical-drive.html

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s