SOLVED Console Extensions cannot connect to the database through administration service - 2403

[Yann-Loïc]

Hello everyone who read this post. I did a fresh installation of CM 2403 in lab environment. I got the message that you can read in the subject of the post. And here it is the screen shot.



Here is the messages I got in the AdminUI.ExtensionInstaller.log


And the following are from SmsAdminUI.log


Everything seems to work correctly but that. If you have any idea about the problem, I will be glad to test it.

 

[Prajwal Desai]

What I understand is it is the webview2 extension that has failed to install. Can you repair the console and see if that helps - https://www.prajwaldesai.com/repair-configuration-manager-console/

 

[Yann-Loïc]

Thanks your reply. Repairing changes nothing. Perhaps I did something wrong during the post-configuration You have to know many things :
- It's a technical preview
- I don't use a PKI solution. I don't know if it necessary for Extension Console.
- I can't see updates in Updates and Servicing node and I know there are at least 2 updates no OOB (
KB28290310 and KB26186448)
- I can get the OOB updates and make it available in Updates and Servicing node.
- The Software Update Point doesn't show Products and Classification.

 

[Prajwal Desai]

You didn't mention it was a technical preview in your initial query. Now you say it's technical preview 2403 in your previous response. And there is no TP 2403 at all. So you have to first confirm what version of ConfigMgr is installed.

 

[Yann-Loïc]

Sorry about that. I thought that version was a TP.
Here are the good information.

 

[Prajwal Desai]

Alright, If I am correct, you are seeing that error only when you access the console extensions? The other issues that you mentioned may be occurring because you haven't configured the roles correctly.

 

[Yann-Loïc]

Yes that's right. I installed TP 2405 and I had the same issue.

 

[Prajwal Desai]

Yes that's right. I installed TP 2405 and I had the same issue.

It's an extension related issue. If you are referring to TP 2405, this version has a known issue, which is the inability to import or establish a console connection with the PowerShell ConfigMgr module - https://www.prajwaldesai.com/sccm-technical-preview-2405-new-features/

 

[Yann-Loïc]

Hello Prajwaldesai, I think that my problem comes from certificates. I have no PKI on my infrastructure and I don't want to configure one. I am going to find a tutorial to put in service a self signed certificate. I will tell you if it works. Thanks for you time and don't waste more.

 

[Prajwal Desai]

Ok, try those steps. Keep us updated.

 

[Yann-Loïc]

Hello Prajwal,

I got it and I think solution will remind you something.
First, I noticed that I had sometimes another issue occuring when I started the console configuration manager as you can see below in AdminService.log.


I asked chatgpt to help me. Among a bunch of idea, It gave me this one :

2. Add the​

If the assembly is loaded from a network location or SCCM considers its location untrusted, you can try enabling the loadFromRemoteSources feature in the .NET configuration file.

1. Open the .NET configuration file for AdminService (usually located at C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config).
2. Look for the <runtime>section.
3. Add the following code in this section to allow the loading of assemblies from remote locations:
   <runtime>
   <loadFromRemoteSources enabled="true"/>
   </runtime>
4. IISreset

And it works fine.