Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

This technical note has information related to a problem that may happen when running a Smartclient and a popup error appears.

FIPS are established guidelines for computer security products by the National Institute of Standards and Technology, that is, only methods approved by this standard can be used.

This document shows how to make FIPS configuration so the SmartClient is not blocked. The error appears in version 9.1, and the windows version used was 20H2.

On this page:

Table of Contents
maxLevel3


The problem

Errors

When running the SmartClient, an error appears and was not possible to run the Client:

Error message example


Another error can happen too when running the Framework.

Error message example



The solution

How to solve the issue FIPS configuration

The first step is to press the Windows + R shortcut and open the run popup:


Then, type “gpedit.msc” in Open field and press OK.

An error message says that the file could not be found


Note
titleNote Item

If this popup opens (image above), it means that you do not have the gpedit activated, so you can go to “Appendix A” to do it.


Otherwise, the following window will open:

Local Group Policy Editor screen


The next step is to go to Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options and set the option "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" as Disabled. You can see this in the enumerated image below:

Disable the selected option in the image


With this item is disabled, you are supposed to be able to run your SmartClient project with success.



Appendix A

How to activate the GPEDIT in Windows 10

When you type gpedit.msc in Windows + R, the following popup appears not allowing you to open the “Local Group Policy Editor”. You can follow the solution, which is working for windows version 1809 or up.

An error message says that the file could not be found


You can do the following steps to activate the GPEDIT:

1 - Copy the code below into a notepad and save it with the (.bat) extension.

Code Block
titleCode Block Example
linenumberstrue
@echo off
pushd "%~dp0"
dir /b 
C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt
dir /b 
C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt

for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"C:\Windows\servicing\Packages\%%i"
pause
   


Name the filed with .bat extension


Then, go to the folder you have saved your .bat file and “Run as administrator” as shown in image 8.

Right-click the .bat document and select Run as administrator


The prompt window will open and install the gpedit.

Prompt window


When it is finished, you are able to open the “Local Group Policy Editor” window. Therefore, you can continue in Section 2. <<<<.continue in Section 2 is correct or should we remove it?>>>>



In this section...

Page Tree
root@parent
spacesV10