I have two SQL Servers at two different servers:
SERVER 1: SQL Server Enterprise edition 2008 r2 64bit
SERVER 2: SQL Server Standard edition 2008 64bit
I have db_admin permission on both SQL Server, when I am connecting server 1 from server 2 then it is connecting(means connecting enterprise from standard) but when I am doing reverse it is not connecting. How can I resolve it?
Note: When I am connecting SERVER 1 from other servers with same SQL Server edition and vice versa, it is connecting well.
The edition is not going to be relevant if you are using SSMS. When you cannot connect, the problem is usually a configuration issues but if it works both ways to other servers, that might not be the case. Try the below first.
In the server properties dialog of Server 2, go to the Connections tab on the left. About 3/4 of the way down is an option to "Allow remote connections to this server". It should be checked.
If it is checked, the next thing to do is verify what port the server is on. If it is not on the standard 1433, you will need to add the port to the connection (e.g. MyServer,1234)
Related
This is the error when connecting to server
Please help. When connecting to sql server using odbc.
You're trying to connect to a SQL Server instance that is running on a server that is in a different Windows domain than the client. Either the domains need to trust each other, or you need to login using SQL Server authentication instead of Windows authentication.
I have two virtual machines runs on my laptop, let's say their name are VMApp and VMDB, and both are runs the same OS, Windows Server 2008 R2.
On VMDB, I installed all SQL Server 2008 features except the Reporting Services. in contrast, I installed only SQL Server 2008 Reporting Services on VMApp.
I run Reporting Services Configuration Manager on VMApp and point the Server Name to the VMDB's computer name, then I got an error message
"A connection to the computer cannot be established"
I enabled the named pipe from SQL Server Configuration Tools on VMDB, but I still get that error message on VMApp.
I think the problem is not network connection because the VMs are connected in same domain network and they could ping each other.
Sorry for this dumb case because I am newbie in SQL Server, and I really appreciate any help from you guys!
Regards,
Chrisma Andhika
You cant set the DB path to SERVERNAME\INSTANCENAME on the configuration manager. There isnt even that option. First you set the server:
and then the DB:
where exactly are you having your issue?
FYI: try to enable SQL Browser on VMDB or to connect by IP if you cant enable browser
I am using SQL Server 2008 Enterprise on Windows Server 2008 Enterprise. The server runs SQL Server 2008 is machine M1. I have tried using SQL Server Management Studio on machine M2 could be connected to M1. But I can not use another machine M3 to connect to M1. Any ideas what is wrong? I am not sure whether it is the issue at M1 side or M3 side? Any check list?
Error message is, provider: named pipeline provider program, error 40 -- can not open connection to SQL Server (Microsoft SQL Server: error 53).
thanks in advance,
George
On M1 you need to enable TCP/IP in SQL Server Configuration Manager, under "Protocols for MSSQLSERVER". In addition to this you need to open at least port 1433 in the Windows Firewall
I have installed SQL Server 2008 Developer on Windows 7 (64 bit). In SQL Management Studio I cannot register the default instance MSSQLSERVER. It cannot find it although the service is running. I get the message:
Cannot connect to PHOENIX\MSSQLSERVER.
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: 25 - Connection string is not valid)
(Microsoft SQL Server, Error: 87)
However SQL Server Management Studio does show the SQL Server 2005 Express instance (that was installed with VS 2008 Pro) which appeared as already registered. I am using Windows Authentication as I installed it in mixed mode.
How do I connect to an MSSQLSERVER instance using SQL Server Management Studio?
I always connected as:
[machine_name]/[instance_name]
and it wasn't able to connect. What works is connecting simply as:
[machine_name]
This is probably due to the fact that I am running a DEFAULT instance.
Check if the server allows remote connections on TCP/IP port 1433.
this can be checked by SQL Server 2008 configuration manager.
Go to network configuration and check if tcp/ip is enabled. If not enable this one.
I've installed sql2008 express sp1 on my laptop that's running the beta 1 of windows 7. The problem that I'm experiencing is a combination of dynamic ports/firewall/windows 7.
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I was first experiencing this problem when I was trying to connect to sql with the management tools, but as soon as I enabled Sql Server Management Tools as a program to go through the firewall it worked out fine. Now the problem is when I launch my web site it gives me that error. I've also positive that sql browser is running and I've enabled tcp/ip and named pipes in the sql express service.
So does anyone have any thoughts as to how to resolve this?
Are you using the same instance name in both SSMS and your web application?
Commonly, people will try to connect based upon the machine name exclusively, for instance "MySQLServer". SQL Server Express installs a named instance by default, whose default name is SQLExpress. If this is the case, try connecting to "MySQLServer\SQLExpress" instead (omitting the quotes, of course).
Go into SQL Server Configuration Manager - under Programs - Microsoft SQL Server 2008 - Configuration Tools - and make sure that under SQL Server Network Configuration - Protocols for SQLExpress, that Named Pipes is enabled (by default it is not).
Yes, I'm aware of both scenarios. I've setup as a named instance and as a default instance as well, and adjusted the connection strings, neither worked.
I've also enabled named pipes and no go. It has everything to do with windows 7 firewall, but couldn't figure it out so I just installed server 2008 standard edition and voila.
I suspect the fact that it uses dynamic ports is another issue with windows 7.