DX Infrastructure Management

  • Private Community
 View Only
Back to Library

NFA 9.3.7 Install/Upgrade .NET Framework v 4.7 and 4.6.2 

Aug 08, 2017 11:20 AM

Microsoft recently released a patch, ref KB3186539 which automatically installs .NET Framework v 4.7. 

CA does not support this version in 9.3.7, we support .NET Framework version 4.6.2.

 

See;

 

https://docops.ca.com/ca-network-flow-analysis/9-3-7/en/installing/system-recommendations-and-requirements/windows-servers/install-net-framework

 

CA engineering confirmed that when the code freeze for the release of 9.3.7 was in place, .NET Framework v 4.7 had not yet been released, so therefore it was not tested with NFA 9.3.7, and therefore it is NOT supported.

 

If you have installed the patch, and then tried to install 9.3.7 on your Havester, the install script will halt having detected that v 4.7 is in place.

 

If you did install the MS patch, as a workaround you can uninstall it, by going to Windows,

Control Panel>Programs>Programs and Features

Uninstall an update' > KB3186539.

 

It is our intention to support .NET Framework v 4.7 in a future release of NFA.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Christopher Walsh
Feb 27, 2018 09:14 AM

FYI you may see a similar error for Anomaly Detector 9.3.8 which can be resolved by following the document below:

Can't add Anomaly Detector to NFA / NPC /CAPC - CA Knowledge 

 

You may also still get a warning if .NET 4.7.1 is installed, but it will let you continue the installation/upgrade.

Christophe_Sperandio
Aug 09, 2017 01:05 PM

Yes no problem. I understand it was not released yet. I'm just stating the QA tests with this version should be considered as a priority on the to-do list!

Charles Nack
Aug 09, 2017 09:59 AM

Chris, when NFA was compiled and tested .NET 4.7 was not yet released. We need to QA against it first to ensure its supportability and any changes to .NET that may cause issues. We have added this to our backlog but don't have an ETA as of yet.

Christophe_Sperandio
Aug 09, 2017 03:33 AM

Is there anything planned about this? Because asking a customer to downgrade something which comes with Windows Update won't be accepted by everyone, especially if we don't state clearly it's a temporary workaround for the installation and can then be upgraded again without breaking the support.

Simon Sage
Aug 08, 2017 02:02 PM

Also worth knowing adding the following to the registry on the server stops dot net from being updated to 4.7

 

 

  1.  Tap on the Windows-key, type regedit.exe, and hit the Enter-key on the keyboard. This should start the Windows Registry Editor.

  2.  Go to the key: HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP

  3.  Right-click on NDP and select New > Key.

  4.  Name that key WU.

  5.  Right-click on WU, and select New > Dword (32-bit) Value.

  6.  Name it BlockNetFramework47.

  7.  Set its value to 1 (double-click it to set value).

Related Entries and Links

No Related Resource entered.