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
Related
I updated my Windows 7 to SP1 for the purpose to install Visual Studio 2013. I am successfully done my job to install Visual Studio 2013. But the problem arises when I try to install SQL Server 2008 or 2008 R2 Management Studio.
The SQL Server service is not running in services.msc and the SQL Server Browser service is not even listed in SQL Server Configuration Manager.
Please help me because I have install SQL Server 2008 Management Studio several times and update it also to SQL Server SP1 but still not running SQL Server service in services.msc.
Due to this I cannot connect my database engine.
Providing I also enter the correct instance name several times by following the link
Cannot register default instance MSSQLSERVER in SQL Server 2008
I have a copy of SQL Server 2008 and SQL Server 2014 on my machine.
Reporting services has been installed and configured for both instances
SQL Server 2008 instance - machinename\SQL08
SQL Server 2014 instance - machinename
However I can't connect to the 2008 instance of the report server.
From SSMS 2014 I see the following
From SSMS 2008 I see the following
From the Reporting Server Configuration for 2014 I get the following, which shows that it can connect to the 2014 report server
From the Reporting Server Configuration for 2008 I get the following, which shows that it isn't able to see any servers
When I enter the 08 reporting instance I get the following error message.
Has anyone seen this WMI error message and know how to resolve it?
Can you please make sure the reporting service is actually running? From the run command type "Services.msc" and search for SQL Server Reporting Services. It should be running and set to "Automatic"
If its running and issue still persist then please check your firewall.
Hope this helps!
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)
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 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.