RE: SQL Server... Still need help

From: DavidN (davidn_at_brokentrain.com)
Date: 08/26/04


Date: Thu, 26 Aug 2004 12:35:12 -0700

Sorry I forgot to update my email address on the previous
reply.
>-----Original Message-----
>I tried the bug fix you suggested, but it had no effect.
>I am creating a web app with database access using the
>MCAD/MASD self paced training kit. Visual Studio and
MSDE
>were fresh installs on a non-networked w2k pro machine
>(although I had to rig a temporary internet connection to
>regester software, it has been removed since this machine
>has no firewall, etc.) IIS simulates web access through
>virtual directories and has a virtual directory called
>Data that contains the database files, which are actually
>located at c:\Program Files\Microsoft SQL
>Server\MSSQL\Data. The book mentions giving permissions
>to the ASPNET user account and as I mentioned I have
>placed this user in the Admin group so it should have no
>restrictions. The SQL Server Service Manager reports
that
>the the server is running. In Server Explorer-Data
>Connections-BT01(my machine name).Contacts.dbo, if I
>select modify connection to see datalink properties,
>connection tab, line 1 - Select or enter a server name is
>blank (same as the example in the book), line 2 - Windows
>Integrated Security, line 3 - Select DB on server =
>Contacts, Then clicking "test connection" returns
>succeeded.
>
>However, when I try your suggestion of enabling the
TCP/IP
>server network library, "test connection" returns 'Test
>connection failed because of an error in initializing
>provider [DBNETLIB][Connection Open(Connect()).] SQL
>server does not exist or access denied. If I remove the
>TCP/IP server network library again, the test connection
>succeeds.
>
>I'm curious why line 1 on the Data Connections
>Properties/Connection tab is blank. I assume it is
because
>I chose modify an existing connection, and since the book
>shows that as normal, maybe it is. I'm starting to think
>that "SQL server does not exist or access denied" is the
>new 'Blue Screen Of Death' generic meaningless catch-all
>error message. 13 hours and counting trying to resolve
>this mess! Your help is more than appreciated, it has
>become essential!
>
>>-----Original Message-----
>>Are you creating a Web based application that is
>connecting to SQL or a
>>Standalone Console type application?
>>
>>Disabling the Network Protocols will only allow clients
>to use Shared
>>Memory.
>>Try enabling the other protocols Named Pipes and TCP to
>see if the problem
>>persists. Here's an article that walks
>>you thru the process.
>>
>>827204 BUG: You may not be able to connect to an
instance
>of Microsoft SQL
>>http://support.microsoft.com/?id=827204
>>
>>Thanks,
>>
>>Kevin McDonnell
>>Microsoft Corporation
>>
>>This posting is provided AS IS with no warranties, and
>confers no rights.
>>
>>
>>
>>.
>>
>.
>



Relevant Pages

  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... You will no longer need the database MDF file name in the connection string. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... as USER INSTANCE on existing SQL Server Express, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Performance of ODBC
    ... if you have a software firewall; forward 1433/1434 to your server ... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard. ... I originally set up my ODBC connection via ...
    (microsoft.public.access.adp.sqlserver)
  • SQL 2005 Express and VS .Net 2003 wizard error More options
    ... Open the server explorer panel ... Go to the Provider tab and select SQL NAtive Client (DON'T use oledb ... Go back to the Connection tab and carry on setting up the connection ... I have installed Visual Studio 2005 Professional and then Visual Studio ...
    (microsoft.public.sqlserver)
  • Re: Timeout problem with SS2K, VS03
    ... I noticed calls in sql profiler: ... This is the server side debug stored procedure. ... a timeout issue that I cannot identify the source of. ... transaction is committed and the connection is closed cleanly and all ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... listening on UDP 1434 using netstat -abn, ... And i double checked the connection string, and i did have it the right ... But I have another 2000 server that I can connect to fine, ... I am trying to connect from an XP SP2 machine remotely to a SQL Express ...
    (microsoft.public.sqlserver.connect)