Microsoft sql server ошибка 1225

Remove From My Forums

Question
I encountered a problem with my SQL Server 2014 Standard edition. It is denying me access to the Management Studio and I cannot access the SQL Server from Visual Studio. The error message reads,

«Cannot connect to SQL. Additional information: 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: TCP Provider, error: 0 — the remote computer refused the network connection.) (Microsoft SQL Server, Error: 1225). The remote computer refused the network connection.»

My SQL Server is a stand-alone installation and I have all the permissions. I would be grateful if anyone could help me with tips on how to solve this problem.

Thank you.

Longinus.

LOE

Источник

Remove From My Forums

Question
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 Serverinstance Specified)

How Can i solve this?
- Edited by
  
  Tuesday, March 25, 2014 6:17 AM

Answers

1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect(«YourServerName»,$_)) «server listening on TCP port $_» }
7. Check firewall settings if step 5 or 6 connectivity test fails

Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/

MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM
Check the below
1. SQL Server are up are runing
2. check the correct instance name
3. add in exception in firewall
4. check if anti virus is using it
5. check the sql browser services
Ramesh Babu Vavilla MCTS,MSBI
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM

Источник

Remove From My Forums

Question
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 Serverinstance Specified)

How Can i solve this?
- Edited by
  
  Tuesday, March 25, 2014 6:17 AM

Answers

1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect(«YourServerName»,$_)) «server listening on TCP port $_» }
7. Check firewall settings if step 5 or 6 connectivity test fails

Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/

MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM
Check the below
1. SQL Server are up are runing
2. check the correct instance name
3. add in exception in firewall
4. check if anti virus is using it
5. check the sql browser services
Ramesh Babu Vavilla MCTS,MSBI
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM
- Proposed as answer by
  Shanky_621MVP
  Tuesday, March 25, 2014 4:04 PM
- Marked as answer by
  tracycai
  Tuesday, April 1, 2014 7:34 AM

Источник

When try to connect to SQL Server from Microsoft Server Management Studio, I got an error: 1225 occurred; few days ago, it was working fine, but now this error occurs:

Screen Shot Error: 1225 in Microsoft Server Management Studio

When try to start SQL Server from Services (local) Error 3417 occurred
Screen Shot Error: 3417 in Services (local)

When try to start to SQL Service Agent through services, then another error #1068 occurs:

Screen Shot Error: 1068 in Services (local)

jarlh

41.2k8 gold badges43 silver badges62 bronze badges

asked Mar 8, 2018 at 6:11

When I faced similar issue, I did following:

In windows RUN type eventvwr.msc (or go to WindowsEventViewer)
Windows Event viewer will be opened.
Go to Application Events
Try to login to sql server again (it will fail of-course)
Now refersh the ApplicationEvents again.
You will see the recent error even logged.

This will tell you exact error.

In my case, my SQL version was expired. And I only knew it from event log.

The only solution I had was to re-install sql server.

answered Mar 8, 2018 at 6:20

SSDSSD

1,3752 gold badges13 silver badges20 bronze badges

Who knows the mess you made. Just go to:

Start > Microsoft SQL Server 2019 > SQL Server Installation Center > Maintenance > Repair

and when it asks to «browse to the media folder» I found mine under

C:SQL2019Developer_ENU

the SETUP:EXE file is what you are looking for

enter image description here

follow all the steps of the Repair tool and you will be good to go

answered May 24, 2020 at 21:57

answered Feb 4, 2021 at 12:13

MikeRyzMikeRyz

1891 gold badge2 silver badges18 bronze badges

Источник

Remove From My Forums

Question
The remote computer refused the network connection… I’m getting this error message which probably is very generic and I apologize for that however, not sure how to resolve this issue… So far I’m able to fix it by resetting my Setting > Accounts
«Sign in with a local account instead» to using my online Microsoft account… This problem came about when I started using my company’s VPN link to remote desktop into work… However, now it’s back again and not sure what to do?
Maybe this isn’t related but ever since my company started using a more secure method to log into work from home, my home system thinks the network is disconnected and I no longer can access any external devices, my SQL server, etc. until I disconnect
the VPN link and even then specifically my SQL Server will still give me that error message Error: 1225?

Answers

which port is running for mssql ?

On a default instance, SQL Server listens on TCP/1433 by default. This can be changed. On a named instance, unless configured differently, SQL Server listens on a dynamic TCP port. What that means is should SQL Server discover that the port is in use, it will
pick another TCP port. How clients usually find the right port in the case of a named instance is by talking to the SQL Server Listener Service/SQL Browser. That listens on UDP/1434 and cannot be changed. If you have a named instance, you can configure a static
port and if you have a need to use Kerberos authentication/delegation, you should.

What you’ll need to determine is what port your SQL Server is listening on. Then you’ll need to get with your networking/security folks to determine if they allow communication to that port via VPN. If they are, as indicated, check your firewall settings. Some
systems have multiple firewalls (my laptop is an example). If so, you’ll need to check all the firewalls on your system.

If all of those are correct, verify the server doesn’t have an IPSEC policy that restricts access to the SQL Server port via IP address. That also could result in you being blocked.

http://stackoverflow.com/questions/669372/not-connecting-to-sql-server-over-vpn

Please click Mark As Answer if my post helped.
- Proposed as answer by
  
  Thursday, January 7, 2016 10:35 AM
- Marked as answer by
  Lydia ZhangMicrosoft contingent staff
  Friday, January 8, 2016 6:42 AM

Источник

Remove From My Forums

Question
The remote computer refused the network connection… I’m getting this error message which probably is very generic and I apologize for that however, not sure how to resolve this issue… So far I’m able to fix it by resetting my Setting > Accounts
«Sign in with a local account instead» to using my online Microsoft account… This problem came about when I started using my company’s VPN link to remote desktop into work… However, now it’s back again and not sure what to do?
Maybe this isn’t related but ever since my company started using a more secure method to log into work from home, my home system thinks the network is disconnected and I no longer can access any external devices, my SQL server, etc. until I disconnect
the VPN link and even then specifically my SQL Server will still give me that error message Error: 1225?

Answers

which port is running for mssql ?

On a default instance, SQL Server listens on TCP/1433 by default. This can be changed. On a named instance, unless configured differently, SQL Server listens on a dynamic TCP port. What that means is should SQL Server discover that the port is in use, it will
pick another TCP port. How clients usually find the right port in the case of a named instance is by talking to the SQL Server Listener Service/SQL Browser. That listens on UDP/1434 and cannot be changed. If you have a named instance, you can configure a static
port and if you have a need to use Kerberos authentication/delegation, you should.

What you’ll need to determine is what port your SQL Server is listening on. Then you’ll need to get with your networking/security folks to determine if they allow communication to that port via VPN. If they are, as indicated, check your firewall settings. Some
systems have multiple firewalls (my laptop is an example). If so, you’ll need to check all the firewalls on your system.

If all of those are correct, verify the server doesn’t have an IPSEC policy that restricts access to the SQL Server port via IP address. That also could result in you being blocked.

http://stackoverflow.com/questions/669372/not-connecting-to-sql-server-over-vpn

Please click Mark As Answer if my post helped.
- Proposed as answer by
  
  Thursday, January 7, 2016 10:35 AM
- Marked as answer by
  Lydia ZhangMicrosoft contingent staff
  Friday, January 8, 2016 6:42 AM

Источник

There was an ip change on the sql server and after that I cannot connect from other machines ssms but can connect locally .

The firewall is disabled on the server and moreover its listening on port 1433 and all the network protocols are open named pipes, shared memory and tcpip.

TCP/IP properties IPAII — TCP port set to 1433 and TCP Dynamic Ports are blank

Am i missing something?

CR241

1,4551 gold badge14 silver badges31 bronze badges

asked Aug 30, 2018 at 13:00

SQL_NoExpertSQL_NoExpert

1,0071 gold badge10 silver badges34 bronze badges

Possible Solutions

Did you restart the SQL Server instance after the IP address was changed? If not, then the SQL Server was possibly still listening on the old IP address.

When connecting locally you normally utilise the Shared Memory connection, that is why you were able to connect locally, but not from remote (see 1.). The Shared Memory connection does not require the IP address. You can verify this by running the following query after connecting locally:

select 
    sdec.net_transport, 
    sdec.session_id, 
    sdes.login_name 
from sys.dm_exec_connections as sdec 
join sys.dm_exec_sessions as sdes 
    on sdec.session_id = sdes.session_id

Possible output:

net_transport session_id  login_name
-------------------------------------------------
TCP           51          NT SERVICEReportServer  
Shared memory 52          DomainAccount
Shared memory 55          NT SERVICESQLSERVERAGENT
Shared memory 54          NT SERVICESQLSERVERAGENT
Shared memory 53          NT SERVICESQLSERVERAGENT
Session       55          NT SERVICESQLSERVERAGENT
Session       55          NT SERVICESQLSERVERAGENT
Shared memory 56          NT SERVICEReportServer
Shared memory 57          DomainAccount

TCP = IP Connection
Shared memory = Local Connection

Your local connection would show up as a Shared memory connection.

Did you flush the DNS cache on your other server/computer before you tried connecting? Sometimes cleaning the cache will resolve IP <> Hostname resolutions issues:
```
 ipconfig /flushdns
```
Verifying the network configuration in the SQL Server Configuration Manager can help resolve issues. Possible errors:
- IP Address does not exist (See 1.: Reboot Instance)
- IP Address is not configured to listen (Set Enabled: Yes and Active: Yes)

After rebooting the SQL Server instance check the SQL Server Errorlog file to verify that it is indeed listening on the TCP stack:

2018-08-30 16:15:47.12 spid15s     Server is listening on [ 'any' <ipv6> 1433].
2018-08-30 16:15:47.13 spid15s     Server is listening on [ 'any' <ipv4> 1433].
2018-08-30 16:15:47.13 spid15s     Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ].
2018-08-30 16:15:47.13 spid10s     The resource database build version is 12.00.5589. This is an informational message only. No user action is required.
2018-08-30 16:15:47.13 spid15s     Server local connection provider is ready to accept connection on [ \.pipesqlquery ].
2018-08-30 16:15:47.14 Server      Server is listening on [ ::1 <ipv6> 1434].
2018-08-30 16:15:47.15 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-08-30 16:15:47.15 Server      Dedicated admin connection support was established for listening locally on port 1434.
2018-08-30 16:15:47.15 SQL Server is now ready for client connections. This is an informational message; no user action is required.

This instance was previously not listening on the TCP stack:

2018-08-24 08:36:09.06 spid15s     Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ].
2018-08-24 08:36:09.07 spid15s     Server local connection provider is ready to accept connection on [ \.pipesqlquery ].
2018-08-24 08:36:09.08 Server      Server is listening on [ ::1 <ipv6> 1434].
2018-08-24 08:36:09.08 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-08-24 08:36:09.08 Server      Dedicated admin connection support was established for listening locally on port 1434.
2018-08-24 08:36:09.09 spid15s     SQL Server is now ready for client connections. This is an informational message; no user action is required.

It could be a firewall rule that hasn’t been adapted to the new IP address of the server. In that case you would have to have your company’s network department look at the rules on the firewall and fix the rule for your server or if you only having issues with your Windows Firewall, check the rules there.
_{(Added from comments)}

answered Aug 30, 2018 at 14:19

John K. N.John K. N.

15.7k10 gold badges45 silver badges100 bronze badges

Источник

Microsoft sql server ошибка 1225

Question

Question

Answers

Question

Answers

Question

Answers

Question

Answers

Possible Solutions

А вот еще интересные материалы: