Visual Studio 2019 cannot connect to Biztalk 2020 Server on different machine

t8eo 1 Reputation point

I have installed Visual Studio 2019 and Biztalk Server 2020 in a Windows 10 Pro VM (Hyper V). The Biztalk project in Visual Studio can see the Biztalk without problem. Trying to use the Visual Studio 2019 on my Windows 10 Pro PC (not in VM) and the Biztalk Server 2020 in the VM then the Biztalk Visual Studio project cannot connect to Biztalk. In the project properties in the deployment tab I fill correctly the server but in the configuration Database says "The target principal name is incorrect. Cannot generate SSPI context.". I have disabled the firewall on my pc and on the VM without result. Also I mention that I am not in domain. So I can only do the development in the same VM with the Biztalk Server. Is any solution to this? Thank you

Microsoft BizTalk Server
Microsoft BizTalk Server
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
349 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Kamlesh Kumar 3,861 Reputation points

    Dear member,

    Thank you for posting your question on the Q&A platform.

    Need clarification here, what do you mean by "Biztalk Visual Studio project cannot connect to Biztalk", is it possible to share the screenshot of the working configuration and not working error?

    Here I would suggest a couple of things that you can check,

    1. Check if you are using the same account or the account that use for VS have access to BizTalk VM as well.
    2. Check if you are able to connect BizTalk databases from your local machine where Vs is installed.
    3. Check if TCP/IP is enabled on BizTalk VM.

    Kamlesh Kumar

    0 comments No comments

  2. Colin Dijkgraaf 1,346 Reputation points

    It has never been possible to use Visual Studio to deploy to a BizTalk Server apart from the local one.

    If you want to deploy to a different BizTalk Server you need to create a MSI, either by exporting it from the local server or using BTDF or other build process, and running that MSI against that server.

    0 comments No comments