Today, i success install SQL Server 2014 Standard Edition to production server. The Services run well, like my setting before. I only make Database Engine, Agent and Browser Service run automatically, others manual. I try using Management Studio to connect to database and run.
I try to configure using SQL Server Configuration Manager to run Management Studio remotely. when i try to remote access from my pc using Management Studio, I get error like this.
I try every solution on site that have been search like on Microsoft Site (https://msdn.microsoft.com/en-us/library/ms175043.aspx), but still that error happen. I believe this is more about Firewall, but i do not know what point that should allow. every port have been allowed. I do not get good result.
I found my solution on MSDN blog (http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx). they give me 5 solution.
I try to configure using SQL Server Configuration Manager to run Management Studio remotely. when i try to remote access from my pc using Management Studio, I get error like this.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I try every solution on site that have been search like on Microsoft Site (https://msdn.microsoft.com/en-us/library/ms175043.aspx), but still that error happen. I believe this is more about Firewall, but i do not know what point that should allow. every port have been allowed. I do not get good result.
I found my solution on MSDN blog (http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx). they give me 5 solution.
- Make sure your server name is correct, e.g., no typo on the name.
- Make sure your instance name is correct and there is actually such an instance on your target machine. [Update: Some application converts \\ to \. If you are not sure about your application, please try both Server\Instance and Server\\Instance in your connection string]
- Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
- Make sure SQL Browser service is running on the server.
- If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
and solution No. 5 works for me, I add new role on Advanced Firewall to allow sqlbrowser service.
Comments
Post a Comment