Esko Logo Back to Esko Support
Choose your language for a machine translation:
Skip to end of metadata
Go to start of metadata


Description

A standard Automation Engine (up to version 16.1.1), ArtiosCAD or WebCenter installation on a clean system requires SQL Server 2014 to be installed on that system. The prerequisites installation procedure takes care of this and will install both SQL Server 2014 Express Edition and all of its own prerequisite components.

From Automation Engine 18.0 onwards, this is no longer an issue as Automation Engine 18.0 ships with a SQL Express 2017, which no longer needs the .NET Framework 3.5. This version needs the .NET Framework 4.6.1. The Automation Engine installer will check and install the .NET Framework 4.6.1 (if the installed version is lower). For this version, there exists an offline installer which is distributed along with Automation Engine 18.0.

One of these second-order prerequisites is the .NET Framework 3.5 SP1 component. Unfortunately, on Windows Server 2012 R2, Windows Server 2012, Windows 8.x systems and later, this component sometimes require manual intervention of an operator to install properly.

As Microsoft does not distribute a stand-alone installer for this component, the prerequisite installation procedure instructs the operating system to enable it instead. The OS may then try to reach out for a valid source, such as the Microsoft Windows Update channel, to download the payload of the component (as for the OS versions mentioned, this payload is not readily available).

In case such a download is initiated, this action may fail for instance due to one of the following reasons:

  1. The access to the Microsoft Windows Update channel is blocked on the computer by a group policy.
  2. Access to the Microsoft Windows Update channel is prohibited by other measures or there is no internet connection possible at all.

For the first case, the group policy might be adapted. The procedure to follow is described in the Procedure 1: method A or B section below.

For the second case, either a network connection should be set up, or an original Windows (operating system) installation medium (e.g. a Windows DVD) must be used to enable the .NET Framework 3.5 SP1 component. The procedure to follow is described in the Procedure 2: Method A or B section below.

If in the first case, the policy cannot be adapted (e.g. because it is defined as a global policy by the IT department), the procedure for the second case can be considered.

Procedure 1: With Internet Access, without a Windows installation medium

Method A: Adapt Windows group policy for optional component installation and component repair

Applies to Windows Server 2012 R2, Windows Server 2012 and Windows 8.x

In case the system is configured to use Windows Server Update Services (WSUS) for servicing, it may occur that fetching and installing the .NET Framework 3.5 SP1 component is not possible (f.i. because its payload is not available on the WSUS server and there is no other way configured to get to it).

Follow the steps in this procedure to change the Windows group policy (if allowed by the IT-policy) to contact Windows Update directly to obtain optional installation or repair content instead of going through Windows Server Update Services (WSUS).

Note that in case of doubt, or when the IT-policy would not allow for it, Procedure 2 can be considered as well.

  1. In the Search box (from Settings or from Everywhere), type Group Policy and then click Edit group policy.
  2. Go to Computer Configuration > Administrative Templates > System and select Specify settings for optional component installation and component repair.
  3. Double-click this entry, or right-click to select Edit policy setting.
    1. Select the Enabled radio button.
    2. Select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box.
    3. Click Apply and then click the OK button.
  4. Now go back to the Automation Engine installer and try to install the Prerequisites again.
    If the .NET Framework 3.5 SP1 component installation still fails, the access to the Windows Update channel is probably blocked by (an)other rule(s) in the IT-policy.
    In that case, follow Procedure 2 below to install the component using a Windows Installation medium.
  5. If needed, revert the changes to these settings after the Automation Engine installation is completed.

Method B: Adapt Windows Registry for optional component installation and component repair

Applies to Windows Server 2012 R2, Windows Server 2012 and Windows 8.x

This procedure directly changes the registry entries of the machine. This can be considered a solution for IT professionals. 

It is advised to take a backup of the registry before attempting to edit the registry. Mal-performed registry edits can harm your system and render it useless.

  1. Go the the Windows icon, type "regedit" and open the app.
  2. Create a new "Servicing" key on the following location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing


  3. Add a new DWORD key: RepairContentServerSource with decimal value 2 or hexadecimal value 0x00000002


  4. The result should look like

 

You can now install .Net 3.5 through the normal Add/Remove features wizard from Windows or using the Automation Engine, ArtiosCAD or WebCenter DVD. 

Full key path: [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing] "RepairContentServerSource"=DWORD(2)

Procedure 2: Using a Windows installation medium

Follow one of the methods in this procedure to enable the .NET Framework 3.5 SP1 component, making use of an available Windows installation medium (such as an original Windows distribution DVD).

Method A: Adapt Windows group policy for optional component installation and component repair

Applies to Windows Server 2012 R2, Windows Server 2012 and Windows 8.x

Follow the steps given below for this method to change the Windows group policy (if allowed by the IT-policy), to obtain optional installation or repair content from an alternate source.

  1. In the Search box (from Settings or from Everywhere), type Group Policy and then click Edit group policy.
  2. Go to Computer Configuration > Administrative Templates > System and select Specify settings for optional component installation and component repair.
  3. Double-click this entry, or right-click to select Edit policy setting.
    1. Select the Enabled radio button.
    2. Specify the Alternate source file path as a fully qualified path to a (shared) folder that contains the contents of the \sources\sxs folder from an original Windows installation medium.
      example 1: D:\sources\sxs (with D: the drive letter corresponding to your DVD-reader or other appropriate distribution medium)
      example 2: \\server_name\share\Win8sxs
    3. Click Apply and then click the OK button.
  4. Now go back to the Automation Engine installer and try to install the Prerequisites again.

  5. If needed, revert the changes to these settings after the Automation Engine installation is completed.

Method B: Via the Add Roles and Features Wizard

Applies only to Windows Server 2012 R2 and Windows Server 2012

Follow the steps for this method to install the .NET Framework 3.5 SP1 component manually.

  1. In the Search box (from Settings or from Everywhere), type Windows features and then click the Turn Windows features on or off.
  2. The Add Roles and Features Wizard opens.
  3. Click Next in the windows (shown in the screenshot) that follows.




  4. In the Select features window, enable the .NET 3.5 Features option and then click Next.
  5. Click the Specify an alternate source path link.
  6. Type a fully qualified path to a (shared) folder that contains the contents of the \sources\sxs folder from an original Windows installation medium.
    example 1: D:\sources\sxs (with D: the drive letter corresponding to your DVD-reader or other appropriate distribution medium)
    example 2: \\server_name\share\Win8sxs and click OK to start the installation
  7. Click the Install button.


  8. Please wait while the .NET Framework 3.5 is installing on your system, then click Close to leave the Add Roles and Features Wizard dialog.
  9. Now go back to the Automation Engine installer and try to install the Prerequisites again.

More detailed information on installing windows roles and features using the Features Wizard can be found on the following link
https://docs.microsoft.com/en-us/windows-server/administration/server-manager/install-or-uninstall-roles-role-services-or-features#BKMK_installarfw

Article information
Applies to

Automation Engine 16.x and older

WebCenter all versions

ArtiosCAD all versions

Created

 

Last revised
Author

LEFR

GDM

Case Number
Contents