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.

(0) Share

Report

Posted on by NissenB

Hello everyone,

I need your help. I have been struggling with this error since days and I don't seem to find the solution.

For a Devops mapping purpose, I had to rename my Virtual Machine (did it with SQL). I made sure the updates were made.
After since, Whenever I compile a model I get this error in Visual Studio 2019 (see below). On the other hand, Synchronize Database is not showing any erros.

When I open the Log file of the model result compilation, (file name : BuildModelResult) I noticed that it is calling the old name of the VM :

<Moniker>Initialization of cross reference database failed. Connection:Data Source=OLDNAME;Initial Catalog=master;Integrated Security=True;Connect Timeout=100;ConnectRetryCount=5;ConnectRetryInterval=10 failed with exception message:System.Data.SqlClient.SqlException (0x80131904)</Moniker>

I will be greatful for any thoughts to help me with this.

Thanks alot!

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

huijij 19,813 on at

Like (0)

Report
Copy link

Link copied!

Hi,

You can follow up the MS document to troubleshoot the errors:

docs.microsoft.com/.../network-related-or-instance-specific-error-occurred-while-establishing-connection

Was this reply helpful? Yes No
Prajakta 5 on at

Like (0)

Report
Copy link

Link copied!

Hello, I am also facing same error. What was the solution to your problem ? I can see below link is marked as answer but there are a lot of things in that. Which specific was the solution to your problem. Appreciate you feedback. Thanks in advance !

Was this reply helpful? Yes No
Suggested answer

San Artham 3,177 on at

Like (0)

Report
Copy link

Link copied!

The file "AosService\PackagesLocalDirectory\bin\DynamicsDevConfig.xml" likely has entries pointing to other VM.

Check the file and update the entries as needed.

Was this reply helpful? Yes No