asked
default Instance installation is successfull but unable to install a named instance?
Hi, I have recently installed new OS on my Test machine, ever since then i am sussessfull with MSSQLSERVER (default instance) installation but unable to install a named instance, The thing is throught out the installation process till the end I am not seeing a single error msg even at the end of the installation process(its clean and successfull), but when i open the management studio to connect to the Database engine it is firing the following ERROR MSG TITLE: Connect to Server Cannot connect to SERVER6. 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) Note: 1.I have checked the TCP/IP protocols etc those are enabled and fine 2.I used the same installation files and setup on my previous OS,the installation was successfull then and now i am using the same version and same edition of the OS that i used to have before and the same installation setup files , but failing to install a named instance is there anything related to winows firewalls even i tried installing turning windows firewalls off ,on etc but no luck.
is the new service installed - check in Services to see that there are two SQLServer services, especially one that has your instance name beside it.
This site functions according to votes. For all helpful answers below, show this by clicking on the thumbs up next to those answers. If any one answer lead to a solution, indicate this by clicking on the check mark next to that answer.
Hey there As you've already set named pipes and tcp to enabled for the named instance the next thing to check would be that the browser is turned on. This is used to establish the connection, namely which port the named instance is using. Try that. Good luck. Final note, with regard the firewall - the browser service uses UDP port 1434
Yes @DenisT @kev Riley @FatherJack SQl service instance which i have installed is running...but when i opened the ssms, i am unable to connect to the Database Engine (Unable to Login) After seeing the error message in installation wizard-->setup support rules that "Make sure appropriate ports are open to enable Remote Accessing" I followed below steps... created new in bound rules 135 – Transact SQL Debugger 1433 – SQL Traffic 1434 – SQL Browser Traffic 2383 – SQL Analytics Traffic 4022 – SQL Broker Traffic not only enabled TCP/IP but also i'v entered the port number 1433 in the properties of TCP?IP after right clicking it, Enabled all windows firewall remote access options in windows firewall-->Allow a feature or program through windows firewall.. nothing is working out,still scratching my head.. and finally followed the steps in the below link
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx No luck yet :(
Just to confirm, as you've not explicitly answered this question yet: can you start SSMS on the server itself and connect to the SQL instance? (thereby excluding all network and firewall issues)
Yes @Mart i AM sure its started and the SQL Broker's start up type is Automatic and loged On as "Local Service".
@kev Riley I am able to start the SSMS But Unable to Connect to the Named Instance but I am able to connect to the Default Instance
A named instance will not be on 1433 - it will, by default, be set to a dynamic port. The default instance already has 1433 registered.
Not being able to connect to the named instance suggests either the SQLBrowser service isn't running (or running correctly - try restarting it), or you are not referring to the named instance correctly - I do this all the time and put the `\` the wrong way round!! If you can resolve the issue locally on the server (using SSMS locally I mean) then that's one step towards solving the whole picture.
Just for test, open import wizard from any database on default instance of SQL sever, for Data source choose SQL server native Client (11?) and than check if you see named instance in drop down list for Server Name? If you see named instance, copy that name, and connect via SSMS. Also, you need be a (minimaly) member of public server role on named instance.
20 People are following this question.
