Wednesday, March 7, 2012

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...
>
>

No comments:

Post a Comment