Connection failed:

Hi Guys,

I encountered an error while opening my third SQL Connection in Enterprise Manager

--------
Microsoft SQL Server Login
--------
Connection failed:
SQLState: '01000'
SQL Server Error: 232
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (WrapperWrite()).
Connection failed:
SQLState: '08S01'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

--------
OK
--------

I am using the following
SQL Server 2000 Enterprise Edition (SP4)
Windows 2000 Professional (SP4)

first two connections are with Query Analyzer, the third attempt is when opening a table inside Enterprise Manager

anyone experienced this?Sounds like you have to enable the shared memory protocol for the instance in cliconfg.exe.|||hi MCrowley

yeah, but the problem is, I can't remember what I did (gosh, too much for making experiments :) )

Is there a way on how to reverse this effect?

Thanks|||Is the Shared Memory protocol enabled in Cliconfg.exe?|||Is the Shared Memory protocol enabled in Cliconfg.exe? ;)|||The first thing I would do if I were in your position would be to check the setting of Shared Memory Protocol in cliconfg.exe and make sure it is enabled.

Just my .02 :)|||gosh,

sorry for the very late reply

yes, its enabled, what does this option do by the way?

thanks|||Shared memory is a protocol that can be used by applications running on the same box as SQL Server. Now that it is enabled, do you still get the same error?

Connection denied. Please help

Hello, everyone. I'm new in Reporting Services 2005. I encountered a confused connection problem. I'm running a named instance (called 'sql05') of SQL Server 2005 Standard Edition(a SQL Server 2000 instance as my default) on my Windows XP Professional machine. I log in Windows XP as a member of Administrators group. When I came into SQL Server Management Studio and connect to my local reporting server using Windows Authentication, the report server denied my connection request 'actively'. The service is running but it denied my connection. But when I use the same method to connect to my database engine and Analysis Services in Management Studio, no problem has happened. Does anyone have similar experiences? I appreciate for any help. Thank you!Ha, I found the solution. I mistakely altered the settings in Reporting Services Configuation Manager. On the 'Database Setup' page, I mistakely changed the 'Credential Type' from 'Service Credentials' to 'Windows Credentials' and input my WindowsXP username and password. This seems error-prone. When I changes back to 'Service Credentials' and apply it, the problem above solved. Can you help me distinguish between these Credential Types? Which type is suitable?