SOLVED Configuration Managment Console not connecting

[LRPH]

Greetings,

New to SCCM please bare with me.

Have one site and everything is running off the same host. The host is server 2019 std and the current version of SCCM is 2107. Recently applied windows updates to the server and now the management console will not connect. Attempted a site reset and monitored the logs and I am getting the following.

Sitecomp.log - A network-related or instance-specific error has occurred while establishing a connection to SQL server. Server is not found or not accessible. Check if insurance name is correct and if SQL server is configured to allow remote connections **failed to connect to SQL server, connection type: SMS access.

CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection

CSiteControlEx::GetMasterSCF: Failed to read site information from database. Retry in 5 seconds….



ConfigMgrSetup.log - A network-related or instance-specific error has occurred while establishing a connection to SQL server. Server is not found or not accessible. Check if insurance name is correct and if SQL server is configured to allow remote connections. ***Failed to connect to the SQL Server, connection type: (site fqdn) Master.

INFO: SQL Connection failed. Connection: (site server) master, Type: Unsecure

Any ideas on what to check and also what I can do to resolve the issue?

Thanks in advance.

 

[LRPH]

I found something new when trying to stop the SQL service. When I attempt to stop the service from the command line I am presented with a "Service is not started" message. When I attempt to start the service I am presented with "service could not be started" error 17051.

Digging into the error message it comes down to the licensing. looking at the licensing it does say it is using a evaluation license. I suppose the evaluation has expired, thus not starting the service.

This leads me to a follow on question. If I change the license type to express will this break the SQL database that is in place for SCCM?

 

[Garth]

I found something new when trying to stop the SQL service. When I attempt to stop the service from the command line I am presented with a "Service is not started" message. When I attempt to start the service I am presented with "service could not be started" error 17051.

Digging into the error message it comes down to the licensing. looking at the licensing it does say it is using a evaluation license. I suppose the evaluation has expired, thus not starting the service.

This leads me to a follow on question. If I change the license type to express will this break the SQL database that is in place for SCCM?

SQL Express is NOT supported for CM site server. You get a free SQL Standard lic when you purchase CM so....

 

[LRPH]

SQL Express is NOT supported for CM site server. You get a free SQL Standard lic when you purchase CM so....

That is good news. However, I believe the SCCM that was deployed had a separate SQL server installed (on the same server). The version that is installed is a evaluation version of 2017 SQL Enterprise.

I have tried to apply a STD license and one of the checks failed with a "Rule "SQL Server 2017 edition downgrade" generated a warning.
The selected edition downgrade path is not valid. The source Evaluation edition and the target Standard edition is not a supported path."

I think this has to do with the eval version being enterprise. How can I switch the sql version to a 2017 std version? or is it safe to proceed?

 

[Garth]

Because of the way SQL enterprise stores data in some cases, the only supported method is to start over from scratch.

I have heard of people using the detach and attach method to downgrade SQL BUT I wouldn't do that as I would be afraid thing will not work correctly down the road.

So... IMO you need to start clean with everything, SQL, CM, new site code, etc.