Do you know that SQL Server is in fact installed on the machine in question? If so, can you connect to it? If you can't see it as a service and you can't connect to it, maybe it's not installed.
answered Sep 29 '10 at 04:27 AM
Grant Fritchey ♦♦
Did you install a named instance rather than a default one?
answered Sep 29 '10 at 05:21 AM
We had that issue last time when sys admins decided to "lock down" certain security accesses to the server. It was resolved once the DBA Group (or the DBA username if if fits your case) was added to the local Administrators Groups.
answered Sep 29 '10 at 09:06 AM
A few thoughts:
Are you sure it's installed? Is the software in the appropriate place? Do the registry settings for SQL Server lead you to the right place?
is the home for the registry for SQL Server. Below that you should find a registry key called "Instance Names" which will guide you further.
What about the Services database within the registry? Did you look in there?
In there, you'll find various services named "MSSQL" something.And what about the files on your hard disk? If there's nothing there called "sqlservr.exe", then SQL Server isn't installed...
answered Sep 29 '10 at 12:10 PM