Re: Connecting to new SQL Server - database engine no local server

Under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance
Names\SQL" I have an entry of type Name "MSSQLSERVER and data "MSSQL.1 ( a string value with the name MSSQLServer and value MSSQL.1)

I have the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1

Can this be related to a user right problem under Windows 2008?

/A



"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:E5D9A4E3-2C87-4F5D-BCE1-3C3F950D21F9@xxxxxxxxxxxxxxxx
This is not normal at all.

The installed instance names of SQL Server is saved under the following registry key: (The list which shows up when you click "Browse for more..." and then "Browse for Servers" window pops up and you expand the "Database Engine" node in the "Local Servers" tab.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL

Will you check this list to find out if your MSSQLSERVER (Default Instance) is listed under that node or not?

And can you tell me if you have the following key existed?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1

It's supposed to be MSSQL.1 if this is the first time you install a SQL Server instance and your SQL Server Instance's records should be under this key. You can stroll under this key to find out information about your installed SQL Server instance.

If you are sure that MSSQL.1 is the key which contains the information about your installed instance and if you don't have a created String Value for this instance of SQL Server then you may want to try to create a String Value under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL". This String Value' s name is supposed to be "MSSQLSERVER" (as your SQL Server instance is a Default Instance) and its value should be "MSSQL.1" (if your scenario matches what I told above)

You can elaborate if you do not want to move on by yourself.

--
Ekrem Önsoy



"A." <andy.i@xxxxxxxxxxxxxxx> wrote in message news:e5uFNuSzIHA.2360@xxxxxxxxxxxxxxxxxxxxxxx
The engine must be installed, since under Network Servers I see the server name, and can connecto to that, I'm also able to connect to "localhost" "Server_Name" and "." from the server name field

The services that are installed are:

SQL Server Integration Serives
SQl Server Fulltext Search (MSSQLSERVER)
SQL Server(MSSQLSERVER)
SQL Server Analysis Services(MSSQLSErver)
SQWL Reporting serives (MSSQLSERVER)
SQL Server Browser
SQL Server Agent (MSSQLSERVER)

"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:16D17413-FCDF-4011-B23F-94A229ECB7D4@xxxxxxxxxxxxxxxx
Hello Andy,

SQL Server Database Engine may not be installed during SQL Server Setup. To ensure if this is true or false, you must open SQL Server Configuration Manager and check out "SQL Server 2005 Services" node to see installed SQL Server services.

Tell us what SQL Server services are installed. If you can see the Database Engine (which looks like "SQL Server (MSSQLSERVER)" if it's a Default Instance or "SQL Server (<Instance_name>)" in case it's a Named Instance).

--
Ekrem Önsoy



"A." <andy.i@xxxxxxxxxxxxxxx> wrote in message news:eIAMj2gyIHA.2184@xxxxxxxxxxxxxxxxxxxxxxx
Hi

Just installed a new SQL Server 2005 server. And have some questions related to the connection window in Management Studio.
When I Launch Management Studio I choose the server I will connect to in the server box. In this there is no name, so I choose "Browse for more.."
Here I can select the server to connect to. Under "local Servers" I have en entry saying "database Engine" but no servers are listed. I have to choose "Network servers", and browse down to I find the server in Questions. Does this sound right when I'm launching Management Studio from the local server where the database engine is installed?
In the SQL Server 2005 Surface Area configuration tool the server is configured for Remote Connections. I've chosen "local and Remote connections." and enabled both TCP/IP and names pipes. The only option that I can connect to under "local servers" are Integration services".

/A.





.

Relevant Pages

  • Re: Trying to Move Group - SQL Instance Wont Start
    ... You can do a maintenance install and add the new nodes. ... "maintaining a failover cluster" for recovery from failure scenario 1. ... Senior SQL Infrastructure Consultant ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... While attempting to install SP4, it comes up immediately after I ... to be on one of the nodes that can bring SQL Server online and apply SP3a, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Any help here???
    ... Well, for starters, I believe MDAC is unnecessary for .NET applications - as ... ADO.NET has its own SQL Server provider for data access. ... > trust me - all that's been done here was to install SP2 or upgrade of XP ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
Loading