Quantcast
Channel: AutoSPInstaller
Viewing all articles
Browse latest Browse all 2279

Commented Unassigned: dotNetFX4.5 "missing" [22100]

$
0
0
Before first use of AutoSPInstaller 3.99.51 the host (Windows Server 2012 R2 Standard) had all recent dotNet versions installed, including NDP46-KB3045557-x86-x64-AllOS-ENU.exe which 'upgrades' dotNet Framework 4.5 ("dotNetFX45") to 4.6

AutoSPInstaller then stops part way through installation saying that dotNetFX45 is not installed. any attempt to re-install dotNetFX45 then confirms that it is already installed. Further installation of AutoSPInstaller cannot continue.
Comments: ** Comment from web user: philoj **

For anyone who runs into this, the problem is that the SharePoint 2013 installer doesn't recognize .Net Framework 4.6 (or later) - so if you've installed the 4.6 framework, you can't move forward.

You *can* uninstall the .Net Fx 4.6. The problem here is that every time MSFT updates the damn thing, they change the KB number, and there's no easy way to find the new one. Currently the latest update that does it is KB3102467 - uninstall that from Add/Remove programs and SharePoint 2013 will install easily.

However, if they update the 4.6 framework again, you'll have to go hunting through your installed updates to find it. Obviously the number will be after 3102467.

I used this PowerShell to dump a list of installed updates to a CSV file:

```
$Session = New-Object -ComObject "Microsoft.Update.Session"
$Searcher = $Session.CreateUpdateSearcher()

$historyCount = $Searcher.GetTotalHistoryCount()

$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date,

@{name="Operation"; expression={switch($_.operation){

1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}

}}} | Export-Csv -NoType -Path c:\temp\Updates.csv

```

Then I opened the CSV in Excel, highlighted the column with the KB numbers, and did a find & replace - replace "KB" with "https://support.microsoft.com/en-us/kb/" and you've got a list of URLs that will open the page for the KB article. Then open each page until you find a .Net Framework 4.6 installer.

(This was because as of January 2016 there's no web service to resolve a KB number to an article description, and you can't scrape pages because they're dynamic - a javascript framework that fills the content after it loads. What I think of the TechNet team right now isn't suitable for mixed company)

That was the quickest way I could find. If you can do better, please leave a note here for posterity.


Viewing all articles
Browse latest Browse all 2279

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>