Cannot find mdf files: message

Showing posts with label message. Show all posts

Thursday, March 29, 2012

cannot remove subscription from subscriber!

after deleting a publication from the publisher (which gave a message that
it would also delete all subscriptions to it) the subscription remains on
the subscriber. There is no reference to it on the publisher anymore. It
also looks strange on the subscriber, for example the name format listed in
the subscriptions container on the subscriber was something like
serverName:DatabaseName:PublicationName, and is now only
ServerName:DatabaseName, no publication name. I should also note the name of
the sql server alias used to register it with enterprise manager was change
from that of what it was during the original setup of this replication (was
snapshot, by the way). This was a fix I found for an earlier problem when
trying to setup a new merge replication topology... the alias had to be
changed to match the actual server netbios name. I believe I deleted the
publication from the publisher AFTER I edited the subscriber server's alias
name. Could this have something to do with it?
other info: I cannot delete the tables (articles) from the subscriber
because it thinks its still part of the replication (that was deleted). I
also cannot create the new merge replication, or at least I can create it
but it fails since I need to use the same tables which it thinks are
unavailable due to the previously deleted replication scheme.
any guidance is greatly appreciated. I'm in quite the bind here.
thanks.
answered in the post marked urgent problem
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"djc" <dcopenhaver@.megapathdsl.net> wrote in message
news:%23GZNEuaUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> after deleting a publication from the publisher (which gave a message that
> it would also delete all subscriptions to it) the subscription remains on
> the subscriber. There is no reference to it on the publisher anymore. It
> also looks strange on the subscriber, for example the name format listed
in
> the subscriptions container on the subscriber was something like
> serverName:DatabaseName:PublicationName, and is now only
> ServerName:DatabaseName, no publication name. I should also note the name
of
> the sql server alias used to register it with enterprise manager was
change
> from that of what it was during the original setup of this replication
(was
> snapshot, by the way). This was a fix I found for an earlier problem when
> trying to setup a new merge replication topology... the alias had to be
> changed to match the actual server netbios name. I believe I deleted the
> publication from the publisher AFTER I edited the subscriber server's
alias
> name. Could this have something to do with it?
> other info: I cannot delete the tables (articles) from the subscriber
> because it thinks its still part of the replication (that was deleted). I
> also cannot create the new merge replication, or at least I can create it
> but it fails since I need to use the same tables which it thinks are
> unavailable due to the previously deleted replication scheme.
> any guidance is greatly appreciated. I'm in quite the bind here.
> thanks.
>
|||Running sp_removedbreplication can be used to remove all(ish) traces of
replication in the subscriber database, but obviously must only be done if
this database is not also configured as a publisher. There is also a stored
procedure to tell SQL Server a table is no longer involved in replication
that might be useful: sp_MSunmarkreplinfo which takes the tablename as a
parameter.
Regards,
Paul Ibison
|||thank you! i'll check it out.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uNDdsubUEHA.1764@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> answered in the post marked urgent problem
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "djc" <dcopenhaver@.megapathdsl.net> wrote in message
> news:%23GZNEuaUEHA.1012@.TK2MSFTNGP09.phx.gbl...
that[vbcol=seagreen]
on[vbcol=seagreen]
> in
name[vbcol=seagreen]
> of
> change
> (was
when[vbcol=seagreen]
> alias
I[vbcol=seagreen]
it
>
|||great. thank you.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23TQbhNeUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> Running sp_removedbreplication can be used to remove all(ish) traces of
> replication in the subscriber database, but obviously must only be done if
> this database is not also configured as a publisher. There is also a
stored
> procedure to tell SQL Server a table is no longer involved in replication
> that might be useful: sp_MSunmarkreplinfo which takes the tablename as a
> parameter.
> Regards,
> Paul Ibison
>
sql

Tuesday, March 27, 2012

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)

Cannot Register Remote Server

This is a multi-part message in MIME format.
--=_NextPart_000_0038_01C6ACCB.8D05BD60
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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
--=_NextPart_000_0038_01C6ACCB.8D05BD60
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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
--=_NextPart_000_0038_01C6ACCB.8D05BD60--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 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|||This is a multi-part message in MIME format.
--000100040600010001030705
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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
--000100040600010001030705
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alex AU wrote:
<blockquote cite="mid%234kVSiIrGHA.3680@.TK2MSFTNGP02.phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<style></style>
<meta content="MSHTML 6.00.2900.2912" name="GENERATOR">
<div><font face="Times New Roman">Dear all,</font></div>
<div>Â </div>
<div><font face="Times New Roman">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.</font></div>
<div>Â </div>
<div><font face="Times New Roman">How can IÂ register and connect to
the SERVER\SQL2005 server? </font></div>
<div>Â </div>
<div><font face="Times New Roman">The SERVER\SQL2005 has been
configured toÂ enable the protocols ofÂ shared memory, namepipeÂ and tcpip
already.</font></div>
<div>Â </div>
<div><font face="Times New Roman">The SERVER has installed SQL2000
first and then install SQL2005 server.</font></div>
<div>Â </div>
<div><font face="Times New Roman">Thanks a lot.</font></div>
<div>Â </div>
<div>
<div>
<div>
<div>Â </div>
<div>Â </div>
<div><font face="Times New Roman">Regards,</font></div>
<div>Â </div>
<div><font face="Times New Roman">Alex AU</font></div>
</div>
</div>
</div>
</blockquote>
<font size="-1"><font face="Arial">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.</font></font><br>
<br>
<br>
-- <br>
Regards<br>
Steen SchlÃ¼ter Persson<br>
Databaseadministrator / Systemadministrator<br>
</body>
</html>
--000100040600010001030705--|||This is a multi-part message in MIME format.
--=_NextPart_000_002F_01C6ADE7.6B1D97F0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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:
> 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
--=_NextPart_000_002F_01C6ADE7.6B1D97F0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

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" wrote in message news:323=8D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...Hi AlexCan 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 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

--=_NextPart_000_002F_01C6ADE7.6B1D97F0--|||This is a multi-part message in MIME format.
--=_NextPart_000_0041_01C6ADE7.D964CB70
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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 used the name instance to try connect but it failed.
I've already set the remote connection with namepipe and tcpip in the =service 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 connection. 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 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=C3=BCter Persson
Databaseadministrator / Systemadministrator
--=_NextPart_000_0041_01C6ADE7.D964CB70
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

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 used the name instance to try connect =but it failed.
I've already set the remote =connection with namepipe and tcpip in the service 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 connection. I just cannot register the =SERVER\SQL2005 on my workstation's management studio.
Thanks
Regards,
Alex AU
"Steen Persson (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 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 AUAre 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.-- RegardsSteen =Schl=C3=BCter PerssonDatabaseadministrator / Systemadministrator

--=_NextPart_000_0041_01C6ADE7.D964CB70--|||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:
> > 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
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0103_01C6AF00.EB2418B0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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:
> 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:
> > > 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
>
--=_NextPart_000_0103_01C6AF00.EB2418B0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

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 =1SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].Sqlcmd: Error: Microsoft SQL Native Client : 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..Sqlcmd: Error: Microsoft SQL Native Client : Login =timeout expired.
Thanks a lot.
Regards,
Alex AU
"John Bell" wrote in message news:342=A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...Hi AlexAnd 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" = wrote in message> news:323=8D38E-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 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>

--=_NextPart_000_0103_01C6AF00.EB2418B0--|||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/FreeTools/tabid/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:
> > 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:
> >
> > > 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
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0017_01C6AF40.AEAD7990
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/FreeTools/tabid/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:
> > > 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:
> >
> > > 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
> >
>
--=_NextPart_000_0017_01C6AF40.AEAD7990
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

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" wrote in message news:E4A=5B93E-6A03-4406-87B6-399E4A150D02@.microsoft.com...Hi AlexThis 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/FreeTools/tabid/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" wrote in message> news:342=A5195-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" wrote in message> > news:323=8D38E-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 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> >>

--=_NextPart_000_0017_01C6AF40.AEAD7990--|||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/FreeTools/tabid/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:
> >
> > > 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:
> > >
> > > > 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
> > >
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_000F_01C6AF97.8BFAF4C0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Dear John,
Thanks for your great help. With your information, I found another =article that detailed the settings needed for XP firewall settings for =SQL2005 and would like to share here.
http://support.microsoft.com/kb/914277/en-us
Now I can connect to the SQL2005 instance on the XP workstation.
Thanks again.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message =news:844977CE-C5D2-4A3A-A29D-5DA1613C476C@.microsoft.com...
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/FreeTools/tabid/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:
> >
> > > 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:
> > >
> > > > 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
> > >
> >
>
--=_NextPart_000_000F_01C6AF97.8BFAF4C0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Dear John,
Thanks for your great help. With =your information, I found another article that =detailed the settings needed for XP firewall settings for SQL2005 and would like =to share here.
http://support.microsoft.com/kb/914277/en-us">http://support.micr=osoft.com/kb/914277/en-us
Now I can connect to the SQL2005 =instance on the XP workstation.
Thanks again.
Regards,
Alex AU
"John Bell" wrote in message news:844=977CE-C5D2-4A3A-A29D-5DA1613C476C@.microsoft.com...HiI 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">http://support.microsoft.=com/kb/287932John"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" wrote in message> news:E4A=5B93E-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/FreeTools/tabid/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" wrote in message> > news:342=A5195-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" wrote in message> > > news:323=8D38E-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 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> > >> >>

--=_NextPart_000_000F_01C6AF97.8BFAF4C0--|||Here is another one: http://www.sqlserver2005.de > Screencasts > Enable
Remote Connections.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi Jens
You may want to add a new screen cast for enabling the XP firewall to allow
SQL Server traffic as described in the lower half of the link Alex provided!
John
"Jens" wrote:
> Here is another one: http://www.sqlserver2005.de > Screencasts > Enable
> Remote Connections.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>

Thursday, March 29, 2012

cannot remove subscription from subscriber!

Tuesday, March 27, 2012

Cannot register server (LOCAL)

Cannot register server (LOCAL)

Cannot register server (LOCAL)

Cannot Register Remote Server

Cannot find mdf files

Blog Archive

About Me