Bug ?->Can not make a new connection to SQL Server 2005 X64

Can not make a new connection to SQL Server 2005 X64 until the SQL Server
service is restarted.
OS is Windows 2003 X64 Enterprise Edition all updates are applied.
This repeats every few hours. Server protocols enabled are TCP IP and Named
Pipes
Client protocols are Named Piped only.
The following error is thrown MSg 17
"SQL Server does not exist or access is denied"
Since I am not finding solution this problem on many forums I assume this is
a bug.
Thanks
Kiran"SQL Server does not exist or access is denied" could indicate a problem
resolving the name of the instance. Is this a default instance listening on
the default named pipe, or a named instance? The second would require the
SQL Server Browser Service or require connecting to a specific pipe name. So
is the SQL Server Browser Service running?
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Kiran" <Kiran@.discussions.microsoft.com> wrote in message
news:9CED6B9C-9643-43C5-9961-8BD1E00BFA8A@.microsoft.com...
> Can not make a new connection to SQL Server 2005 X64 until the SQL Server
> service is restarted.
> OS is Windows 2003 X64 Enterprise Edition all updates are applied.
> This repeats every few hours. Server protocols enabled are TCP IP and
> Named
> Pipes
> Client protocols are Named Piped only.
> The following error is thrown MSg 17
> "SQL Server does not exist or access is denied"
> Since I am not finding solution this problem on many forums I assume this
> is
> a bug.
> Thanks
> Kiran
>

Bug ?->Can not make a new connection to SQL Server 2005 X64

Can not make a new connection to SQL Server 2005 X64 until the SQL Server
service is restarted.
OS is Windows 2003 X64 Enterprise Edition all updates are applied.
This repeats every few hours. Server protocols enabled are TCP IP and Named
Pipes
Client protocols are Named Piped only.
The following error is thrown MSg 17
"SQL Server does not exist or access is denied"
Since I am not finding solution this problem on many forums I assume this is
a bug.
Thanks
Kiran
"SQL Server does not exist or access is denied" could indicate a problem
resolving the name of the instance. Is this a default instance listening on
the default named pipe, or a named instance? The second would require the
SQL Server Browser Service or require connecting to a specific pipe name. So
is the SQL Server Browser Service running?
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Kiran" <Kiran@.discussions.microsoft.com> wrote in message
news:9CED6B9C-9643-43C5-9961-8BD1E00BFA8A@.microsoft.com...
> Can not make a new connection to SQL Server 2005 X64 until the SQL Server
> service is restarted.
> OS is Windows 2003 X64 Enterprise Edition all updates are applied.
> This repeats every few hours. Server protocols enabled are TCP IP and
> Named
> Pipes
> Client protocols are Named Piped only.
> The following error is thrown MSg 17
> "SQL Server does not exist or access is denied"
> Since I am not finding solution this problem on many forums I assume this
> is
> a bug.
> Thanks
> Kiran
>

Bug (?) in SQL2005 x64 SP1 CTP

We're testing the same DB (~ 5GB, ~ 500 tables) with
Server32 (Win2003 Standard 32 bit, SQL2005 Developer 32 bit SP1 CTP, 1gb Memory) and with
Server64 (Win2003 x64 Standard 64 bit, SQL2005 Developer 64 bit SP1 CTP, 6gb Memory).

exec sp_MSforeachtable @.command1="SET QUOTED_IDENTIFIER ON DBCC DBREINDEX ('?', '', 90)"

On Server32 the SQL above runs without errors. On Server64 there comes the following error message:
Msg 8621, Level 17, State 1, Line 1
The query processor ran out of stack space during query optimization. Please simplify the query.

A 64bit server with 6gb memory has less stack space than a 32bit server with 1gb memory?

Regards
Peter

PS: I know sp_MSforeachtable is not an official stored procedure, but I don't thinkt there's the problem. I got the same error on Server64, when I run the following cursor:
DECLARE tablename CURSOR
READ_ONLY
FOR select [name] from sys.tables where type = 'U'

DECLARE @.name varchar(80)
OPEN tablename

FETCH NEXT FROM tablename INTO @.name
WHILE (@.@.fetch_status <> -1)
BEGIN
IF (@.@.fetch_status <> -2)
BEGIN
DECLARE @.message varchar(800)
SELECT @.message = 'SET QUOTED_IDENTIFIER ON DBCC DBREINDEX (''' + @.name + ''', '''', 90)'
EXEC (@.message)
END
FETCH NEXT FROM tablename INTO @.name
END

CLOSE tablename
DEALLOCATE tablename
GO
Please file a bug using the MSDN Product Feedback Center. And mention the OS platform, server versions, number of tables in the database etc.|||Bug report created

Thanks
Peter