New SQL Server Registration

I have two (Server A & Server B)SQL Servers located in a
different site and they are connected via DSL internet. I
want to add the other server B to server A using New SQL
Server Registration in server A. How should I do it? Both
sides is using Firewall.
Thanks a lot in advance!Hi
You may want to check out:
http://support.microsoft.com/?id=287932
John
"sim" <anonymous@.discussions.microsoft.com> wrote in message
news:008b01c3ac00$c5230550$a001280a@.phx.gbl...
> I have two (Server A & Server B)SQL Servers located in a
> different site and they are connected via DSL internet. I
> want to add the other server B to server A using New SQL
> Server Registration in server A. How should I do it? Both
> sides is using Firewall.
> Thanks a lot in advance!sql

New MS SQL User cannot display DBs via Enterprise Manager

I have a SQL Server 2000 instance running sp3 (in a cluster).
When I create a NEW SQL user, and give that user access to ONE database (pub
lic and DBO) I cannot list ANY databases from Enterprise Manager when I logi
n with that user. If I refresh the Enterprise Manager Databases View, eventu
ally it will display the Da
tabases - but only after about 10 minutes and I get access violation errors
in my SQL and NT logs. Even if I create a 'dummy SQL login' and give it acce
ss to Northwind, the same results - I cannot list databases in Enterprise Ma
nager. I tried changing the
users default DB to Master - but I got the same results. It does not seem t
o matter what I make the default DB for this user - I still get the errors.
I tried to recreate this problem on another Clustered SQL Server 2000 Instan
ce - this one running sp3a, and I am NOT able to recreate this problem.
I can't imagine that this is a Service Pack issue. Does anyone have any sugg
estions?Previous post "If I refresh the Enterprise Manager Databases View,
eventually it will display the Databases - but only after about 10 minutes
and I get access violation errors in my SQL and NT logs. "
I'd recommend opening up a support case with a SQL Engineer to review teh
Access Violation errors. All bets are off until you resolve this first.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Found the following KB article
http://support.microsoft.com/defaul...15523&Product=s
ql2k
and I checked this out by doing a select * from sysusers on each of my
Databases and 'some' of them had the guest account deleted directly from
their sysusers table!!!
To test the script in the article, I took a 'healthy' DEV Instance,
turned ON the switch in the server setttings that allows modifications
to be made directly to system catalogs, then I deleted the guest account
in one of my user databases. This 'broke' it and i could no longer get
a list of DBs in EM without sysadmin priviledges. I ran the script
which checked each DB and adds the guest account make in if it find it
missing and then disables the "allow modifications to be made directly
to system catalogs" switch. AND THIS WORKED!!!!
Thought I would pass this on. Thank you everyone for your input.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

New Installation can't connect to default database

I installed SQL Server 2005. Connected to an external dB on a different
server just fine. Now am trying to connect (via SQL Server Management Studio
)
to the default local dB. I get the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 23
3.
any ideas what's wrong?Run the SQL Server Configuration Manager and click on the Protocols for that
instance. Check to make sure that you enable Shared Memory.
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>I installed SQL Server 2005. Connected to an external dB on a different
> server just fine. Now am trying to connect (via SQL Server Management
> Studio)
> to the default local dB. I get the following error:
> Cannot connect to <server name in here>
> A connection was successfully established with the server, but then an
> error
> occurred during the login process (provider shared memory provider error
> 0 -
> no process is on the other end of the pipe). Microsoft SQL Server error
> 233.
> any ideas what's wrong?|||Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
that. VIA remains disabled. I can't start the SQL Serveer Agent, either. It
is set to Manual and if I try to start it, I get a message that it started
and stopped again.
"Andrew J. Kelly" wrote:

> Run the SQL Server Configuration Manager and click on the Protocols for th
at
> instance. Check to make sure that you enable Shared Memory.
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>
>|||What do the error and Agent logs say?
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...[vbcol=seagreen]
> Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
> that. VIA remains disabled. I can't start the SQL Serveer Agent, either.
> It
> is set to Manual and if I try to start it, I get a message that it started
> and stopped again.
> "Andrew J. Kelly" wrote:
>|||There was an application event (MSSQLSERVER) that said that the max number o
f
2 user connections had been reached and the connection was closed
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>|||I re-installed SQL and opened the default db first and now it seems to be
working. Very weird.
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>

New Installation can't connect to default database

I installed SQL Server 2005. Connected to an external dB on a different
server just fine. Now am trying to connect (via SQL Server Management Studio)
to the default local dB. I get the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
any ideas what's wrong?
Run the SQL Server Configuration Manager and click on the Protocols for that
instance. Check to make sure that you enable Shared Memory.
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>I installed SQL Server 2005. Connected to an external dB on a different
> server just fine. Now am trying to connect (via SQL Server Management
> Studio)
> to the default local dB. I get the following error:
> Cannot connect to <server name in here>
> A connection was successfully established with the server, but then an
> error
> occurred during the login process (provider shared memory provider error
> 0 -
> no process is on the other end of the pipe). Microsoft SQL Server error
> 233.
> any ideas what's wrong?
|||Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
that. VIA remains disabled. I can't start the SQL Serveer Agent, either. It
is set to Manual and if I try to start it, I get a message that it started
and stopped again.
"Andrew J. Kelly" wrote:

> Run the SQL Server Configuration Manager and click on the Protocols for that
> instance. Check to make sure that you enable Shared Memory.
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>
>
|||What do the error and Agent logs say?
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...[vbcol=seagreen]
> Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
> that. VIA remains disabled. I can't start the SQL Serveer Agent, either.
> It
> is set to Manual and if I try to start it, I get a message that it started
> and stopped again.
> "Andrew J. Kelly" wrote:
|||There was an application event (MSSQLSERVER) that said that the max number of
2 user connections had been reached and the connection was closed
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>
|||I re-installed SQL and opened the default db first and now it seems to be
working. Very weird.
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>