VL Web Deployment Install cannot connect to remote DB

[PatrickF]

I created a VL web deployment based on the shipped VL web template for LANSA V15 EPC150050 on Windows Server 2019. What is different from my previous deployments is that the Web Application will use SQL Server (not Express) 2019 which is on a Remote Windows Server from the Application Server.
I am using msiexec.exe as Local Administrator with these switches to install msiexec.exe /i <appname>_v1.0.0_en-us.msi DBSV=MKLANSADB01 SUDB=1 ALLUSER=1

I have created a local SQL user named WEBUSER password WEBUSER and verified it can connect using SQL Server Management Studio and via an ODBC connection System DSN I created on the Server where I want to install the MSI. SQL Server 2019 is installed with defaults and the default instance name is MSSQLSERVER, so I only need to provide the Server Name. SQL Browser Service is running so the SQL Service is visible on the network. I manually installed ODBC Driver 17 for SQL Server because the VL IDE used it and it wasn't on the target windows server.
However when I install the MSI I get the error below, when the deployment step is trying to create an ODBC System DSN. Questions are :
1) Does the DBSV setting need to be specified differently when it is remote ?
2) What protocols need to be running or started so that the deployment tool can create the DSN ? Why would it be different from me creating the DSN manually as shown on the right of the screen shot with a successful test
3) Can I mod the deployment and have the deployment use a DSN that I have pre-created on the target windows server for the Remote Database where the Application Database will be installed ?

Deployment DSN Create Error.png (90.83 KiB) Viewed 18163 times

[Dino]

Maybe this can give a clue

viewtopic.php?f=3&t=2716&p=8158&hilit=Karl#p8178

[PatrickF]

Hi Dino

While there may be similarities with the use of a Remote DB, I think in the earlier issue, the serving of web pages after the deployment of the MSI had completed was the issue, whereas my issue is that the deployment hard crashes at the point where the deployment attempts to create the DB connection, before actually creating the database and populating the tables with data.
The 3 questions I posed in my original post, were not relevant to the older topic.