SQL 2005 SP3 x64

New install
Server 2008 R2 x64

Trying to install SQL server 2005 Enterprise x64

after installation it does not find the local server

No database Engine, all services are running

Even did an un install , reinstall no luck
PetielAsked:
Who is Participating?
 
lojkConnect With a Mentor .Net and Infrastructure ConsultantCommented:
and if you just type '.' (no quotes) into the instance name box (the top one)?

by 'does not find it' - what is the actual error? If it is 'can't find or denied' have you tried logging in with the SA username and password (or a user with the full administrative privilieges to the installation - not just a local machine administrator unless you added 'builtin\adminstrator' during installation).

Have you just tried a reboot of the server?
0
 
lojk.Net and Infrastructure ConsultantCommented:
how are you checking that it doesn't exist? Does the specifc instance name appear suffixed to the service name in services.msc?

If you are using SSMS to check are you specifying the correct instance name?
try "machinename", "machinename\mssql",  "." or whatever you called the instance

(If there is more than one instance of SQL installed), ensure that the SQLBrowser Service is running and any firewalls have exceptions for the SQLBrowserService executable and the 1433 tcp port.
0
 
PetielAuthor Commented:
I log into Studio management and it does not find it
not even when I browse for a database server

firewall is off
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
PetielAuthor Commented:
the"."
did the trick
0
 
lojk.Net and Infrastructure ConsultantCommented:
yep,win!

Also in sql land '.' just means localhost (works like a HOSTS file entry) - that probably would have worked too.
0
 
lojk.Net and Infrastructure ConsultantCommented:
Just as a quick follow up to this and in case you havent already worked it out.

Unless you specify in SQL Server Surface Area Configuration that the service instance can permit remote connections (usually on the TCP/IP protocols) the only thing that will work is '.' or localhost as they are on the loopback network adapter and are implicity non-remote.

This behaviour is by design and is for security (i.e. if that server is on a public facing IP and/or inadvertandly becomes exposed without your knowledge/intent).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.