October 10, 2012 at 10:52 pm
We have faced a installation problem in our UAT environment.
1. We have 5 named instance in the UAT machine and no default instance in it.
We have tried to install a default instance, but we received error that the sql service cannot be started for deault instance as it doesnt have permission to start.
We have connected default instance in SQL server, but it is conneting to a existing named instance. How this happened? We tried restarting server, but again we found same issue.
Hence we have installed another named instance...
Can anyone help me. How the default instance is conneting to existing named instance.... If its registry issue, then it might fix by the time of restart.. but didnt...
October 10, 2012 at 11:39 pm
GO to the services and check the name of default instance ,you might be using wrong name
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
October 11, 2012 at 1:29 am
Bhuvanesh
thanks i have checked the services, its showing SQL server(MSSQLSERVER) but in stopped state. But i dont understand how it connecting to the exisiting named instance as default if the service is down.
October 11, 2012 at 1:56 am
Senthil Kumar Rajendran (10/11/2012)
its showing SQL server(MSSQLSERVER) but in stopped state.
why they are stopped ?
Senthil Kumar Rajendran (10/11/2012)
But i dont understand how it connecting to the exisiting named instance as default if the service is down.
you can try to stopped the named instance and then try to connect default another approach that "full stop" means DOT (.) also states that you are connec ting to default intances so instead of using instance name try with DOT
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
October 11, 2012 at 2:51 am
It's not allowing to install default instance as it is getting conflict with named instance... while at the time of installation of default instance it getting failed with permission issue mentioning that the accout doesnt have access privilege to start the service.
October 12, 2012 at 6:12 am
you sure you have two instance already?? Normally first installation will take the computer name and dont consider that as named instance.
October 12, 2012 at 8:08 am
Have you set static ports for your named instances?
The default instance will want to use 1433 unless you tell it to use a different port. But if a named instance is already running using 1433 you may have problems. Best practice is to always set static ports for named instances, and do not rely on dynamic port assignment.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply