SOLVED FATAL ERROR DURING INSTALLING SCCM 2203 WINDOWS SERVER 2019 SQL 2019

[PASCAL JOURDAN]

Hello,

I am looking for some help with a problem I am having when installing a new standalone primary site.
Maybe someone here had the same problem and knows what to do.
The setup is as follows:

Primary site server with 4 cores and 32 Gb RAM
OS is Server 2019 with the latest CU.
SQL Server 2019 with latest CU.
SQL Server Management Studio 18.10 and SQL Server 2019 Reporting services .
I created the SCCM database before running the setup without any issues.

 

[PASCAL JOURDAN]

finding below failed logs
INFO: Creating administrative user and assigning Full Administrator role $$<Configuration Manager Setup><04-06-2023 13:25:30.337-240><thread=816 (0x330)>
INFO: Populate CMPivot Script from 'F:\SMSSETUP\BIN\X64\CMPivotContent.xml' $$<Configuration Manager Setup><04-06-2023 13:25:32.353-240><thread=816 (0x330)>
Successfully populated CMPivot Script. $$<Configuration Manager Setup><04-06-2023 13:25:32.509-240><thread=816 (0x330)>
INFO: Removing byte order marker after reading from file (F:\SMSSETUP\BIN\X64\OperatingSystem.xml) $$<Configuration Manager Setup><04-06-2023 13:25:32.525-240><thread=816 (0x330)>


REPORTING IT TO MICROSOFT TODAY

 

[mka999]

Do you have .Net Framework 4.8 ?
In the ConfigMgrPreq.log, it says at the beginning that .Net framework 4.8 cannot be found on the server. Install .Net Framework 4.8 and try again.

Log errors:
WARN: .NET 4.8 or higher is not installed on LRESVVMGMT13.lealreunion.local.
WARN: Found .NET which version is lower than 4.8.
The following machine(s) fail the .NET 4.8 prereq rule.

 

[PASCAL JOURDAN]

ALL DOWN AT THIS TIME
TKS VERY MUCH BUT 4.8 WAS ALREADY INSTALL I REINSTALL A NEW VM AND SET ALL PREREQUIS BEFORE JOINED SERVER TO DOMAIN ANS ALL IS DOWN NOW .

 

[eshann]

A "FATAL ERROR" can be a frustrating experience for users, especially if they lose important data or work as a result of the error. It's important to follow any prompts or instructions that appear on the screen when a fatal error occurs, and to try to determine the root cause of the error so that it can be resolved or prevented in the future.

 

[Prajwal Desai]

This seems to be more of a DB issue to me. Any reason why the ConfigMgr DB is created before installing the ConfigMgr?

 

[setu_bridge]

Hello Pascal,
Kindly you please tell me, how you solved that fatal error problem during SCCM installation?