Cannot remotely login to SQL Express since last windows update

Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.

The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP>\<instance>).

When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.

Does this have something to do with the windows updates, or is it just a coincedence?

Thanks in advance,

Remco RosThis is probably due to the update changed your setting. Just check your firewall on the server and put sqlbrowser.exe or UDP port 1434 to exception. Also make sure your sqlbrowser is running.|||we didn't install the updates on the server (yet) only on the client, so it must be a client thing.

Server:
Win 2003 / SQL Express 2005
Tcp/ip / named pipes: yes
sqlbrowser running
firewall exception on 1434udp 1433tcp.

tested on these client(s):
Local (without latest updates): CAN connect
XP Home with SQL Server Management studio (with lates windows updates): CANNOT connect
XP Pro with SQL Server Management studio Express (with lates windows updates): CANNOT connect
Win 2003 with SQL Server Management studio Express

(WITHOUT lates windows updates): CAN connect.

I see a pattern here...|||Are you sure your SQL Express listens on TCP port 1433 since your put 1433 in exception? What's the result if you run "telnet yourserver sql_tcp_port"? Can it connect? Could it be possible that IPSEC blocked the traffic between the problem machine if the IPSEC is on?

Cannot register server (LOCAL)

I'm trying to register the (LOCAL) database using SQL Server authentication.
However, I get the following message. I still can register other servers
using ip addresses though.
================================================== ===
Cannot connect to (LOCAL).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
================================================== ===
Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/library/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Yes, But no luck on that too.
test
"Tibor Karaszi" wrote:

> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
>
>
|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:

> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/library/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>
|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
test
"Tibor Karaszi" wrote:

> I suggest you first check what SQL Server related services you have installed. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>
|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name>)" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
test
"Tibor Karaszi" wrote:

> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>

Cannot register server (LOCAL)

I'm trying to register the (LOCAL) database using SQL Server authentication.
However, I get the following message. I still can register other servers
using ip addresses though.
===================================================== Cannot connect to (LOCAL).
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
=====================================================did you try localhost?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> I'm trying to register the (LOCAL) database using SQL Server authentication.
> However, I get the following message. I still can register other servers
> using ip addresses though.
> =====================================================> Cannot connect to (LOCAL).
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> =====================================================>|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/library/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Yes, But no luck on that too.
--
test
"Tibor Karaszi" wrote:
> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> > I'm trying to register the (LOCAL) database using SQL Server authentication.
> > However, I get the following message. I still can register other servers
> > using ip addresses though.
> >
> > =====================================================> > Cannot connect to (LOCAL).
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > An error has occurred while establishing a connection to the server. When
> > connecting to SQL Server 2005, this failure may be caused by the fact that
> > under the default settings SQL Server does not allow remote connections.
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> > =====================================================> >
>
>|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:
> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/library/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>|||I suggest you first check what SQL Server related services you have installed. From that we can see
how many instances of SQL Server you installed.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> Under the registered servers I see the following:
> 3tsd3b1
> 3tsd3b1\sqlexpress (which I can connect to successfully)
> Under the Server Group I see the following items:
> (LOCAL)
> 10.100.1.67 (which I can connect to successfully))
> 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> What should I do to create a database on my local machine.
> In other words, what is the equivalent of registering (LOCAL) server in SQL
> Server 2000?
>
>
> "Charles Wang[MSFT]" wrote:
>> Hi,
>> To let me better understand your issue, could you please let me know the
>> following questions:
>> 1. Did you mean registering server named (local) or a database?
>> 2. How did you perform the registration?
>> 3. Why would you like to register a (local) server (database?) ?
>> From the error message, it seemed that you were trying to register a
>> (local) server remotely. "(local)" is preserved keyword for the default
>> instance of local SQL Server. You can only use it to locally connect to
>> your default instance of your SQL Server not remotely. Generally it is no
>> need to register a (local) server, if you want to rename a SQL server
>> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> refer to:
>> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> 2005
>> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> Anyway I think that I have not totally understood your scenario. If there
>> is any misunderstanding, I appreciate your pointing and kindly making some
>> further explanation.
>> Thanks and have a nice day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> =====================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> ======================================================>>
>>|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
--
test
"Tibor Karaszi" wrote:
> I suggest you first check what SQL Server related services you have installed. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> > Under the registered servers I see the following:
> > 3tsd3b1
> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >
> > Under the Server Group I see the following items:
> > (LOCAL)
> > 10.100.1.67 (which I can connect to successfully))
> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >
> > What should I do to create a database on my local machine.
> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> > Server 2000?
> >
> >
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> >> Hi,
> >> To let me better understand your issue, could you please let me know the
> >> following questions:
> >> 1. Did you mean registering server named (local) or a database?
> >> 2. How did you perform the registration?
> >> 3. Why would you like to register a (local) server (database?) ?
> >>
> >> From the error message, it seemed that you were trying to register a
> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> instance of local SQL Server. You can only use it to locally connect to
> >> your default instance of your SQL Server not remotely. Generally it is no
> >> need to register a (local) server, if you want to rename a SQL server
> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> refer to:
> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> 2005
> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >>
> >> Anyway I think that I have not totally understood your scenario. If there
> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> further explanation.
> >>
> >> Thanks and have a nice day!
> >>
> >> Best regards,
> >> Charles Wang
> >> Microsoft Online Community Support
> >> =====================================================> >> When responding to posts, please "Reply to Group" via
> >> your newsreader so that others may learn and benefit
> >> from this issue.
> >> ======================================================> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> ======================================================> >>
> >>
> >>
> >>
> >>
>|||What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
service to me. I suggest you do Run and in there type : services.msc
This starts the "Services" windows applet. In there you look for services where the name starts with
SQL Server, such as :
SQL Server (MSSQLServer)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> The following services are started:
> Server Status (green)
> Report Server Virtual Directory (Red)
> Report Manager Virtual Directory (red)
> Windows Service Identity (Green)
> Database Setup (Red)
> Encryption Keys (Grey)
> Initialization (Grey)
> Email settings (Yellow)
> Execution Account (Yellow)
> --
> test
>
> "Tibor Karaszi" wrote:
>> I suggest you first check what SQL Server related services you have installed. From that we can
>> see
>> how many instances of SQL Server you installed.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> > Under the registered servers I see the following:
>> > 3tsd3b1
>> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >
>> > Under the Server Group I see the following items:
>> > (LOCAL)
>> > 10.100.1.67 (which I can connect to successfully))
>> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >
>> > What should I do to create a database on my local machine.
>> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> > Server 2000?
>> >
>> >
>> >
>> >
>> > "Charles Wang[MSFT]" wrote:
>> >
>> >> Hi,
>> >> To let me better understand your issue, could you please let me know the
>> >> following questions:
>> >> 1. Did you mean registering server named (local) or a database?
>> >> 2. How did you perform the registration?
>> >> 3. Why would you like to register a (local) server (database?) ?
>> >>
>> >> From the error message, it seemed that you were trying to register a
>> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> instance of local SQL Server. You can only use it to locally connect to
>> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> need to register a (local) server, if you want to rename a SQL server
>> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> refer to:
>> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> 2005
>> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >>
>> >> Anyway I think that I have not totally understood your scenario. If there
>> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> further explanation.
>> >>
>> >> Thanks and have a nice day!
>> >>
>> >> Best regards,
>> >> Charles Wang
>> >> Microsoft Online Community Support
>> >> =====================================================>> >> When responding to posts, please "Reply to Group" via
>> >> your newsreader so that others may learn and benefit
>> >> from this issue.
>> >> ======================================================>> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >> ======================================================>> >>
>> >>
>> >>
>> >>
>> >>|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name>)" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
--
test
"Tibor Karaszi" wrote:
> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> > The following services are started:
> >
> > Server Status (green)
> > Report Server Virtual Directory (Red)
> > Report Manager Virtual Directory (red)
> > Windows Service Identity (Green)
> > Database Setup (Red)
> > Encryption Keys (Grey)
> > Initialization (Grey)
> > Email settings (Yellow)
> > Execution Account (Yellow)
> >
> > --
> > test
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I suggest you first check what SQL Server related services you have installed. From that we can
> >> see
> >> how many instances of SQL Server you installed.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> >> > Under the registered servers I see the following:
> >> > 3tsd3b1
> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >> >
> >> > Under the Server Group I see the following items:
> >> > (LOCAL)
> >> > 10.100.1.67 (which I can connect to successfully))
> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >> >
> >> > What should I do to create a database on my local machine.
> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> >> > Server 2000?
> >> >
> >> >
> >> >
> >> >
> >> > "Charles Wang[MSFT]" wrote:
> >> >
> >> >> Hi,
> >> >> To let me better understand your issue, could you please let me know the
> >> >> following questions:
> >> >> 1. Did you mean registering server named (local) or a database?
> >> >> 2. How did you perform the registration?
> >> >> 3. Why would you like to register a (local) server (database?) ?
> >> >>
> >> >> From the error message, it seemed that you were trying to register a
> >> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> >> instance of local SQL Server. You can only use it to locally connect to
> >> >> your default instance of your SQL Server not remotely. Generally it is no
> >> >> need to register a (local) server, if you want to rename a SQL server
> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> >> refer to:
> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> >> 2005
> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >> >>
> >> >> Anyway I think that I have not totally understood your scenario. If there
> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> >> further explanation.
> >> >>
> >> >> Thanks and have a nice day!
> >> >>
> >> >> Best regards,
> >> >> Charles Wang
> >> >> Microsoft Online Community Support
> >> >> =====================================================> >> >> When responding to posts, please "Reply to Group" via
> >> >> your newsreader so that others may learn and benefit
> >> >> from this issue.
> >> >> ======================================================> >> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> >> ======================================================> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
>|||OK. It seems you have installed a named instance of SQL Server express database engine with the
instance name "SQLEXPRESS".
Also, you installed Analysis services and Reporting services as default instances.
So, I assume you want to connect to your express named instance (since that is the only database
engine instance). If you are local on the machine try:
localhost\SQLExpress
Or:
machinename\SQLEXPRESS
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:83688470-F1FB-4618-B743-D1F9B0B267E2@.microsoft.com...
> SQL Server (SQLEXPRESS)
> SQL Server Active Directory Helper
> SQL Server Analysis Services (MSSQLSERVER)
> SQL Server Browser
> SQL Server Integration Services
> SQL Server Reporting Services (MSSQLSERVER)
> SQL Server VSS Writer
> --
> test
>
> "Tibor Karaszi" wrote:
>> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
>> service to me. I suggest you do Run and in there type : services.msc
>> This starts the "Services" windows applet. In there you look for services where the name starts
>> with
>> SQL Server, such as :
>> SQL Server (MSSQLServer)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>> > The following services are started:
>> >
>> > Server Status (green)
>> > Report Server Virtual Directory (Red)
>> > Report Manager Virtual Directory (red)
>> > Windows Service Identity (Green)
>> > Database Setup (Red)
>> > Encryption Keys (Grey)
>> > Initialization (Grey)
>> > Email settings (Yellow)
>> > Execution Account (Yellow)
>> >
>> > --
>> > test
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> I suggest you first check what SQL Server related services you have installed. From that we
>> >> can
>> >> see
>> >> how many instances of SQL Server you installed.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> >> > Under the registered servers I see the following:
>> >> > 3tsd3b1
>> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >> >
>> >> > Under the Server Group I see the following items:
>> >> > (LOCAL)
>> >> > 10.100.1.67 (which I can connect to successfully))
>> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >> >
>> >> > What should I do to create a database on my local machine.
>> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> >> > Server 2000?
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Charles Wang[MSFT]" wrote:
>> >> >
>> >> >> Hi,
>> >> >> To let me better understand your issue, could you please let me know the
>> >> >> following questions:
>> >> >> 1. Did you mean registering server named (local) or a database?
>> >> >> 2. How did you perform the registration?
>> >> >> 3. Why would you like to register a (local) server (database?) ?
>> >> >>
>> >> >> From the error message, it seemed that you were trying to register a
>> >> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> >> instance of local SQL Server. You can only use it to locally connect to
>> >> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> >> need to register a (local) server, if you want to rename a SQL server
>> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> >> refer to:
>> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> >> 2005
>> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >> >>
>> >> >> Anyway I think that I have not totally understood your scenario. If there
>> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> >> further explanation.
>> >> >>
>> >> >> Thanks and have a nice day!
>> >> >>
>> >> >> Best regards,
>> >> >> Charles Wang
>> >> >> Microsoft Online Community Support
>> >> >> =====================================================>> >> >> When responding to posts, please "Reply to Group" via
>> >> >> your newsreader so that others may learn and benefit
>> >> >> from this issue.
>> >> >> ======================================================>> >> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >> >> ======================================================>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>>

Cannot register server (LOCAL)

I'm trying to register the (LOCAL) database using SQL Server authentication
.
However, I get the following message. I still can register other servers
using ip addresses though.
========================================
=============
Cannot connect to (LOCAL).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
========================================
=============did you try localhost?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> I'm trying to register the (LOCAL) database using SQL Server authenticati
on.
> However, I get the following message. I still can register other servers
> using ip addresses though.
> ========================================
=============
> Cannot connect to (LOCAL).
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: TCP Provider, error: 0 - No connection could be made because th
e
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> ========================================
=============
>|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/...y/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Yes, But no luck on that too.
test
"Tibor Karaszi" wrote:

> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
>
>|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:

> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You ma
y
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/...y/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>|||I suggest you first check what SQL Server related services you have installe
d. From that we can see
how many instances of SQL Server you installed.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...[vbcol=seagreen]
> Under the registered servers I see the following:
> 3tsd3b1
> 3tsd3b1\sqlexpress (which I can connect to successfully)
> Under the Server Group I see the following items:
> (LOCAL)
> 10.100.1.67 (which I can connect to successfully))
> 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> What should I do to create a database on my local machine.
> In other words, what is the equivalent of registering (LOCAL) server in SQ
L
> Server 2000?
>
>
> "Charles Wang[MSFT]" wrote:
>|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
test
"Tibor Karaszi" wrote:

> I suggest you first check what SQL Server related services you have instal
led. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>|||What tool did you use to get that list? None of those looks like the name of
a SQL Server 2005
service to me. I suggest you do Run and in there type : services.msc
This starts the "Services" windows applet. In there you look for services wh
ere the name starts with
SQL Server, such as :
SQL Server (MSSQLServer)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...[vbcol=seagreen]
> The following services are started:
> Server Status (green)
> Report Server Virtual Directory (Red)
> Report Manager Virtual Directory (red)
> Windows Service Identity (Green)
> Database Setup (Red)
> Encryption Keys (Grey)
> Initialization (Grey)
> Email settings (Yellow)
> Execution Account (Yellow)
> --
> test
>
> "Tibor Karaszi" wrote:
>|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name> )" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
test
"Tibor Karaszi" wrote:

> What tool did you use to get that list? None of those looks like the name
of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services
where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>

Cannot Register Remote Server

Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AUHi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU|||Alex AU wrote:
> Dear all,
> I've installed SQL2005 on my local machine. And there is another
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols
> of shared memory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server?
It could be that SQL2000 is installed as a default instance (hence you
can connect to it just with the servername) and SQL2005 is installed as
a named instance so you need to use that instance name to connect.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Dear John,
I've already setup the remote connections to accept namepine and tcpip conne
ction in the surface area configuration tool.
I can use ODBC to establish connection from my workstation to the SERVER\SQL
2005 but just cannot register the server in the Management Studio on my work
station.
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:3238D38E-5324
-49BB-A188-43078C16F3A1@.microsoft.com...
Hi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
>
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
>
> How can I register and connect to the SERVER\SQL2005 server?
>
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
>
> The SERVER has installed SQL2000 first and then install SQL2005 server.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU|||Dear Steen,
The SQL2000 is the default instance and SQL2005 is a named instance. When I
register the SQL2005 on my workstation's Management Studio, I've already use
d the name instance to try connect but it failed.
I've already set the remote connection with namepipe and tcpip in the servic
e area configuration on the server. When I try to use ODBC on my workstation
to connect to the SERVER\SQL2005, I can successfully establish the connecti
on. I just cannot register the SERVER\SQL2005 on my workstation's management
studio.
Thanks
Regards,
Alex AU
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message news:u0NxbpJrGHA.
2256@.TK2MSFTNGP03.phx.gbl...
Alex AU wrote:
Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server? It
could be that SQL2000 is installed as a default instance (hence you can conn
ect to it just with the servername) and SQL2005 is installed as a named inst
ance so you need to use that instance name to connect.
--
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
> John
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Dear John,
I've tried sqlcmd, it also failed. The command I used and error as follow:
sqlcmd -S SERVER\SQL2005
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFF
FFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while est
abli
shing a connection to the server. When connecting to SQL Server 2005, this f
ailu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Thanks a lot.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:342A5195-A4E1
-4477-AFDF-F592B3809BDC@.microsoft.com...
Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
>
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
>
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
>
> Thanks.
>
>
>
> Regards,
>
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
>
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
>
> John
>
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
> I've tried sqlcmd, it also failed. The command I used and error as follow:
> sqlcmd -S SERVER\SQL2005
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> Thanks a lot.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
> And SQLCMD allows you to connect?
> John
> "Alex AU" wrote:
>
> Remote
>|||Thanks John,
I've used the tools on that SERVER and I've found that the port number for S
QL2005 using is 1025. (SQL2000 use 1433).
I finally figure out what causing the connection issue, it's the firewall se
ttings. I use a Windows XP with SP2 as a server and the firewall has turned
on. It only allow SQL connection from port 1433 and that's the reason why I
cannot connect with SQL Management Studio with port 1025 (SQL2005). When I s
hut down the firewall, it works.
Sorry for the chaos that I've made. But I really appreciate for your kindly
help.
I've got one more question related to this. I've tried to add exception rule
in the XP firewall settings for port 1025, but I still cannot connect. I ca
n only connect when the firewall is off. Can anyone help with this? (or shou
ld I post in other newsgroup for this issue?)
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:E4A5B93E-6A03
-4406-87B6-399E4A150D02@.microsoft.com...
Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
>
> I've tried sqlcmd, it also failed. The command I used and error as follow:
>
> sqlcmd -S SERVER\SQL2005
>
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
>
> And SQLCMD allows you to connect?
>
> John
>
> "Alex AU" wrote:
>
> Remote
>|||Hi
I don't know the intricacies of the XP firewall as I have always used a
third party one. The following describes what you should need to set up in
terms of rules, change this for the port you are using and it should be ok.
http://support.microsoft.com/kb/287932
John
"Alex AU" wrote:

> Thanks John,
> I've used the tools on that SERVER and I've found that the port number for
> SQL2005 using is 1025. (SQL2000 use 1433).
> I finally figure out what causing the connection issue, it's the firewall
> settings. I use a Windows XP with SP2 as a server and the firewall has
> turned on. It only allow SQL connection from port 1433 and that's the
> reason why I cannot connect with SQL Management Studio with port 1025
> (SQL2005). When I shut down the firewall, it works.
> Sorry for the chaos that I've made. But I really appreciate for your
> kindly help.
> I've got one more question related to this. I've tried to add exception
> rule in the XP firewall settings for port 1025, but I still cannot
> connect. I can only connect when the firewall is off. Can anyone help with
> this? (or should I post in other newsgroup for this issue?)
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:E4A5B93E-6A03-4406-87B6-399E4A150D02@.microsoft.com...
> Hi Alex
> This is indicating that the remote connections setting are not set on
> the
> protocols. What does the SQLServer 2005 Configuration Manager tool say
> (i.e.
> not SAC!). Also make sure that you can resolve the server name
> correctly.
> You may also want to look at SQLPing to to see to search for servers
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> John
> "Alex AU" wrote:
>
> follow:
> while
> this
> Server
> tcpip
> Management
> tool.
> another
> local
> cannot
> of
> SQL2005
>

cannot register local SQL server

I had SQL Server running locally on my pc and now I
suddenly can't connect. I deleted the registration and
tried re-registering it in EM. When I use Windows
authentication I get a msg saying "cannot open default
database, using master database instead"..but it doesn't
register.
When I use SQL authentication using the sa login, I get a
msg saying "login failed for sa, not associated with a
trusted SQL Server connection". (The SQL Server service
is still running OK on my pc).
Any ideas as to how to fix it, and why it went wrong in
the first place?
Thanks
DaveLooks like you:
1. Run in Windows authentication mode, no sa is permitted
2. you deleted the database (or sent it offline) you specified as defautl
database for the
Windows user you try to connect.
TO sign on as sa change the reg key use this manual:
---
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
HTH, Jens Süßmeyer.
"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||dave
>When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
Do you have a login like (DOMAIN\Dave) ?
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection".
You can change an authentication settings of the server
Right click on the server ,then Properties ,then under Security Tab change
Authentication to SQL and Windows.
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||> You can change an authentication settings of the server
> Right click on the server ,then Properties ,then under Security Tab change
> Authentication to SQL and Windows.
But if you can´t register you are really f.... :)
Jens Süßmeyer.|||An alternative to change login mode to mixed is to login using ISQL.EXE (it will let you in even if
your default database doesn't exist) and use sp_defaultdb to change the default database to an
existing database.
I do not recommend changing default database for sysadmins (for the very reason we see here).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||Thanks Jens
Changed the registry setting to 2 and it worked using SQL authentication.
>--Original Message--
>Looks like you:
>1. Run in Windows authentication mode, no sa is permitted
>2. you deleted the database (or sent it offline) you specified as defautl
>database for the
>Windows user you try to connect.
>TO sign on as sa change the reg key use this manual:
>----
--
>http://support.microsoft.com/default.aspx?scid=3Dkb;EN-
US;q285097
>----
--
>INF: How to Change the Default Login Authentication Mode to SQL While
>Installing SQL Server 2000 Desktop Engine by Using Windows Installer
>----
--
><snip>
>Another way to change the security mode after installation is to stop
>SQL Server and set the appropriate registry key for your installation:
>Default instance:
>HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
>Named instance:
>HKLM\Software\Microsoft\Microsoft SQL Server\Instance
>Name\MSSQLServer\LoginMode
>to 2 for mixed-mode or 1 for integrated. (Integrated is the default
>setup for the SQL Server 2000 Data Engine.)
></snip>
>HTH, Jens S=FC=DFmeyer.
>
>
>"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
>news:06d901c3b41f$68325220$a001280a@.phx.gbl...
>> I had SQL Server running locally on my pc and now I
>> suddenly can't connect. I deleted the registration and
>> tried re-registering it in EM. When I use Windows
>> authentication I get a msg saying "cannot open default
>> database, using master database instead"..but it doesn't
>> register.
>> When I use SQL authentication using the sa login, I get a
>> msg saying "login failed for sa, not associated with a
>> trusted SQL Server connection". (The SQL Server service
>> is still running OK on my pc).
>> Any ideas as to how to fix it, and why it went wrong in
>> the first place?
>> Thanks
>> Dave
>
>.
>|||just change the loginmode parameter in the register to sa..
It should work
--
Shaju Thomas
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave

Cannot register local sql server

I am having a problem registering my local SQL server.
When I try to use Windows authentication an error msg
appears saying "cannot open default db, using master db
instead" but it doesn't register. When I try using SQL
Server authentication (using the sa logon) a msg appears
saying "login failed for sa, not associated with a trusted
sql server connection".
I previously had the server registered ok and then it
suddenly stopped working so I deleted it and now it won't
reregister. I have no problem registering other SQL
Servers through EM on my pc. Any ideas how to fix this and
maybe what caused the problem in the first place?
Thanks
DaveTry changing your default database (which sounds like it has been dropped)
using osql e.g.
osql -E -Sservername -dmaster -Q"exec sp_defaultdb
'domain\username','master'"
replacing servername with the server you are trying to register and
domain\username with your nt login.Once this is done try registering the
server again. BTW you can also use Query Analyzer if that is more
comfortable by starting it from the command line and passing the database
e.g.
isqlw -E -dmaster -Sservername
and then run the command
exec sp_defaultdb 'domain\username','master'
again, you should now be able to register the server
The reason the sa login doesn't work is because the server you are
connecting to is set to Windows Authentication only.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:09d301c3b438$d482b550$a001280a@.phx.gbl...
I am having a problem registering my local SQL server.
When I try to use Windows authentication an error msg
appears saying "cannot open default db, using master db
instead" but it doesn't register. When I try using SQL
Server authentication (using the sa logon) a msg appears
saying "login failed for sa, not associated with a trusted
sql server connection".
I previously had the server registered ok and then it
suddenly stopped working so I deleted it and now it won't
reregister. I have no problem registering other SQL
Servers through EM on my pc. Any ideas how to fix this and
maybe what caused the problem in the first place?
Thanks
Dave|||just change the loginmode to 2 in the registry
--
Shaju Thomas
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:09d301c3b438$d482b550$a001280a@.phx.gbl...
> I am having a problem registering my local SQL server.
> When I try to use Windows authentication an error msg
> appears saying "cannot open default db, using master db
> instead" but it doesn't register. When I try using SQL
> Server authentication (using the sa logon) a msg appears
> saying "login failed for sa, not associated with a trusted
> sql server connection".
> I previously had the server registered ok and then it
> suddenly stopped working so I deleted it and now it won't
> reregister. I have no problem registering other SQL
> Servers through EM on my pc. Any ideas how to fix this and
> maybe what caused the problem in the first place?
> Thanks
> Dave

Cannot Register Any Instance of SQL Server 2000 to AD

Hello; I keep getting this message, 'SQL Enterprise Manager could not add
server '(local)' to AD. Error: 14303: Stored procedure
'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
have the sufficient permissions to register any instance to AD, right? I even
installed SP4, but that didn't work. I"m a student of sql server services and
I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
DominickAre you a local administrator on the machine? The error is telling you
that EM can't access the system registry. You also need the rights on
AD to publish the instance, sorry - I don't recall off hand the exact
permission.
Dominick D. wrote:
> Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> server '(local)' to AD. Error: 14303: Stored procedure
> 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> have the sufficient permissions to register any instance to AD, right? I even
> installed SP4, but that didn't work. I"m a student of sql server services and
> I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> Dominick|||Yes, I am a local administrator on the machine where AD is located; I have
enterprise/domain admin rights. I don't understand why EM is not accessing
the registry. Can you dig a little deeper? Get some assistance?
Unfortunately, your response has not helped me.
"PSPDBA" wrote:
> Are you a local administrator on the machine? The error is telling you
> that EM can't access the system registry. You also need the rights on
> AD to publish the instance, sorry - I don't recall off hand the exact
> permission.
>
> Dominick D. wrote:
> > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > server '(local)' to AD. Error: 14303: Stored procedure
> > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > have the sufficient permissions to register any instance to AD, right? I even
> > installed SP4, but that didn't work. I"m a student of sql server services and
> > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> >
> > Dominick
>|||Based on some reading, try change the SQL Service account to your
domain admin account, and use your domain admin to run the stored proc.
I would guess that the SQL Service account doesn't have the privileges
to read/edit the registy on the server.
Dominick D. wrote:
> Yes, I am a local administrator on the machine where AD is located; I have
> enterprise/domain admin rights. I don't understand why EM is not accessing
> the registry. Can you dig a little deeper? Get some assistance?
> Unfortunately, your response has not helped me.
> "PSPDBA" wrote:
> > Are you a local administrator on the machine? The error is telling you
> > that EM can't access the system registry. You also need the rights on
> > AD to publish the instance, sorry - I don't recall off hand the exact
> > permission.
> >
> >
> > Dominick D. wrote:
> > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > server '(local)' to AD. Error: 14303: Stored procedure
> > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > have the sufficient permissions to register any instance to AD, right? I even
> > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > >
> > > Dominick
> >
> >|||OK, I placed the SQLService domain user account into the domain admins group
and I was able to register another instance to the AD, so your advice worked;
however, I was not able to register the default instance to the AD :(. I
don't get that. Any other clue for that reason? Thanks for your help.
"PSPDBA" wrote:
> Based on some reading, try change the SQL Service account to your
> domain admin account, and use your domain admin to run the stored proc.
> I would guess that the SQL Service account doesn't have the privileges
> to read/edit the registy on the server.
>
> Dominick D. wrote:
> > Yes, I am a local administrator on the machine where AD is located; I have
> > enterprise/domain admin rights. I don't understand why EM is not accessing
> > the registry. Can you dig a little deeper? Get some assistance?
> > Unfortunately, your response has not helped me.
> >
> > "PSPDBA" wrote:
> >
> > > Are you a local administrator on the machine? The error is telling you
> > > that EM can't access the system registry. You also need the rights on
> > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > permission.
> > >
> > >
> > > Dominick D. wrote:
> > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > >
> > > > Dominick
> > >
> > >
>|||Ok, we're getting further. I did a little more reading - check the
MSSQLServerADHelper service and set it to use the domain admin account
too.
Dominick D. wrote:
> OK, I placed the SQLService domain user account into the domain admins group
> and I was able to register another instance to the AD, so your advice worked;
> however, I was not able to register the default instance to the AD :(. I
> don't get that. Any other clue for that reason? Thanks for your help.
> "PSPDBA" wrote:
> > Based on some reading, try change the SQL Service account to your
> > domain admin account, and use your domain admin to run the stored proc.
> >
> > I would guess that the SQL Service account doesn't have the privileges
> > to read/edit the registy on the server.
> >
> >
> > Dominick D. wrote:
> > > Yes, I am a local administrator on the machine where AD is located; I have
> > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > the registry. Can you dig a little deeper? Get some assistance?
> > > Unfortunately, your response has not helped me.
> > >
> > > "PSPDBA" wrote:
> > >
> > > > Are you a local administrator on the machine? The error is telling you
> > > > that EM can't access the system registry. You also need the rights on
> > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > permission.
> > > >
> > > >
> > > > Dominick D. wrote:
> > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > >
> > > > > Dominick
> > > >
> > > >
> >
> >|||OK, I can do that, but, I noticed that there is no such user/group called
MSSQLServerADHelper. Do I have to create it or is it already created?
"PSPDBA" wrote:
> Ok, we're getting further. I did a little more reading - check the
> MSSQLServerADHelper service and set it to use the domain admin account
> too.
>
> Dominick D. wrote:
> > OK, I placed the SQLService domain user account into the domain admins group
> > and I was able to register another instance to the AD, so your advice worked;
> > however, I was not able to register the default instance to the AD :(. I
> > don't get that. Any other clue for that reason? Thanks for your help.
> >
> > "PSPDBA" wrote:
> >
> > > Based on some reading, try change the SQL Service account to your
> > > domain admin account, and use your domain admin to run the stored proc.
> > >
> > > I would guess that the SQL Service account doesn't have the privileges
> > > to read/edit the registy on the server.
> > >
> > >
> > > Dominick D. wrote:
> > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > Unfortunately, your response has not helped me.
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > Are you a local administrator on the machine? The error is telling you
> > > > > that EM can't access the system registry. You also need the rights on
> > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > permission.
> > > > >
> > > > >
> > > > > Dominick D. wrote:
> > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > >
> > > > > > Dominick
> > > > >
> > > > >
> > >
> > >
>|||Thats a service on the server, not a group/user.
Dominick D. wrote:
> OK, I can do that, but, I noticed that there is no such user/group called
> MSSQLServerADHelper. Do I have to create it or is it already created?
> "PSPDBA" wrote:
> > Ok, we're getting further. I did a little more reading - check the
> > MSSQLServerADHelper service and set it to use the domain admin account
> > too.
> >
> >
> > Dominick D. wrote:
> > > OK, I placed the SQLService domain user account into the domain admins group
> > > and I was able to register another instance to the AD, so your advice worked;
> > > however, I was not able to register the default instance to the AD :(. I
> > > don't get that. Any other clue for that reason? Thanks for your help.
> > >
> > > "PSPDBA" wrote:
> > >
> > > > Based on some reading, try change the SQL Service account to your
> > > > domain admin account, and use your domain admin to run the stored proc.
> > > >
> > > > I would guess that the SQL Service account doesn't have the privileges
> > > > to read/edit the registy on the server.
> > > >
> > > >
> > > > Dominick D. wrote:
> > > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > > Unfortunately, your response has not helped me.
> > > > >
> > > > > "PSPDBA" wrote:
> > > > >
> > > > > > Are you a local administrator on the machine? The error is telling you
> > > > > > that EM can't access the system registry. You also need the rights on
> > > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > > permission.
> > > > > >
> > > > > >
> > > > > > Dominick D. wrote:
> > > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > > >
> > > > > > > Dominick
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >|||OK, how do I access it and by putting the sa into the domain admins group, I
was able to register both the default and named instance on the AD, so your
advice helped. Thanks.
"PSPDBA" wrote:
> Thats a service on the server, not a group/user.
>
> Dominick D. wrote:
> > OK, I can do that, but, I noticed that there is no such user/group called
> > MSSQLServerADHelper. Do I have to create it or is it already created?
> >
> > "PSPDBA" wrote:
> >
> > > Ok, we're getting further. I did a little more reading - check the
> > > MSSQLServerADHelper service and set it to use the domain admin account
> > > too.
> > >
> > >
> > > Dominick D. wrote:
> > > > OK, I placed the SQLService domain user account into the domain admins group
> > > > and I was able to register another instance to the AD, so your advice worked;
> > > > however, I was not able to register the default instance to the AD :(. I
> > > > don't get that. Any other clue for that reason? Thanks for your help.
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > Based on some reading, try change the SQL Service account to your
> > > > > domain admin account, and use your domain admin to run the stored proc.
> > > > >
> > > > > I would guess that the SQL Service account doesn't have the privileges
> > > > > to read/edit the registy on the server.
> > > > >
> > > > >
> > > > > Dominick D. wrote:
> > > > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > > > Unfortunately, your response has not helped me.
> > > > > >
> > > > > > "PSPDBA" wrote:
> > > > > >
> > > > > > > Are you a local administrator on the machine? The error is telling you
> > > > > > > that EM can't access the system registry. You also need the rights on
> > > > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > > > permission.
> > > > > > >
> > > > > > >
> > > > > > > Dominick D. wrote:
> > > > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > > > >
> > > > > > > > Dominick
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>