Error installing PSU with MS SQL

Hi!
I cant get the installation of PSU 4.3.1 to work with MS SQL. I have tried different conection strings in appsettings.json file and they all fail with “Cant start Service”
Strings I have tried
“ConnectionString”: “Server=SQL_Server\MSSQLSERVER;Database=PSU;Trusted_Connection=True;”
This gives error: Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SNI_PN11, error: 25 - Connection string is not valid)
—> System.ComponentModel.Win32Exception (87): The parameter is incorrect.

Connection string:
Server=SQL_Server;Database=PSU;Trusted_Connection=True;TrustServerCertificate=True;
Gives error: Microsoft.Data.SqlClient.SqlException (0x80131904): CREATE DATABASE permission denied in database ‘master’.

My user is sysadmin.

How is a connectionstring supposed to be formated? Are instance name required? I have tried the standard MSSQLSERVER

\Twinnis
Product: PowerShell Universal
Version: 1.4.6

Here is an example of what i have working

“ConnectionString”: “Server=PC1\\PC1,61038;Database=PSU;Integrated Security=true;TrustServerCertificate=True”,

Am Hosting PSU in IIS in a windows 2022 server with SQL express installed on the same server.

Thanks!
But I dont get it to work. I am wondering you have in your string PC1\PC1,61038. Why do you have server name two times in your string? Perhaps its different string for express. I dont use SQL express, instead I use SQL Server.

Does anyone have a working string for connecting to SQL Sever?

It’s the same you need server name \instancename. SQL strings are the same for sql or sql express there is no difference

What error you are getting when trying sql string? You also need to find your port number and include that in the connection string

I found the problem, PSU server computer account must have rights in remote SQL Server.
Thanks for your answers!