none
SQL Server error '80004005'

    Question

  • Estoy desarrollando una web en asp clásico, utilizando por primera vez una bd sql server. Mis pruebas en local funcionan perfectamente.

    Ahora, he subido a un servidor Windows la bd versus.mdf (en el directorio /App_Data/) y unos archivos de prueba, y me arroja el siguiente error:

    -------------------------------------------------------------------------------------------------------------------------------

    Microsoft OLE DB Provider for SQL Server error '80004005'

    [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    -------------------------------------------------------------------------------------------------------------------------------

    La conexión que realicé es la siguiente:

    <%

    Dim MM_connPortada_STRING

    MM_connPortada_STRING = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=daugusta;Data Source=.\SQLEXPRESS;Initial File Name=" & Server.MapPath("/App_Data/Versus.mdf")

    %>


    Wednesday, December 30, 2009 8:21 PM

Answers

  • Hola!

    El error 80004005 puede representar muchas causas.

    Creo que el siguiente enlace sea de gran utilidad para usted:

    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver][DBNMPNTW] ConnectionOpen(CreateFile()). 
     
    or 
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SQL Server does not exist or access denied. 
     
    or 
     
    Microsoft OLE DB Provider for SQL Server error '80004005'  
    [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied.  
     
    or 
     
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'  
    [Microsoft][ODBC SQL Server Driver][Named Pipes] Specified SQL server not found.  
     
    or 
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver] Client unable to establish connection.
     
    While the first error message is definitely more cryptic than the others, they all mean the same thing. The first simply uses DBNMPNTW, which is the protocol name for named pipes. What the error means is that the SQL Server you defined in your connection string is invalid - either because it is currently down, you named it wrong (either by hostname, DNS/domain or IP address), or you don't have permission to connect. 
     
    If you are expecting to connect by IP address, make sure you override named pipes (see  Article #2082 ).  
     
    If you are using SQL Server authentication, make sure both ends are set up for it (see  Article #2138 ).  
     
    If the error is 'SQL Server does not exist or access denied', see  KB #328306 , which has a large variety of possible causes and solutions. Also see  KB #888228   if you are trying to connect to a named instance within a SQL Server 2000 cluster. 
     
    If the ASP page and SQL Server are on the same machine, then it may be a loopback problem - try using 127.0.0.1, LOCALHOST, (local), or just a period (instead of the external IP or network name) in the connection string.



    http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html


    Saludos!
    Rafael Fagundes - Marque la respuesta como correcta si te ha sido de utilidad!
    • Marked as answer by daugusta Monday, January 18, 2010 7:21 AM
    Wednesday, January 06, 2010 1:06 PM

All replies

  • Hola.

    Ese servidor al que has subido el .mdf de la base de datos, debe ser un servidor de bases de datos (valga la redundancia), en tu caso SQL Server Express, con una instancia que se llame SQLEXPRESS además, de acuerdo a la cadena de conexión que expones. Y has de adjuntar la base de datos también o configurar tu cadena de conexión para que lo haga al conectar:

    Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Data Source=.\SQLExpress;AttachDbFilename=c:\MiCarpeta\App_Data\Versus.mdf; Database=Versus;User ID=daugusta;Password=MiPwd;

    Si una vez hayas revisado y/o configurado todo esto sigues sin poder conectar, nos dices.



    Alberto López Grande (Visita mi blog en http://qwalgrande.blogspot.es/)
    Thursday, December 31, 2009 9:53 AM
  • Bueno, consulté con el soporte del servidor y me respondieron que debo crear la base de datos directamente en el servidor para conectar desde la página web!
    Hasta allí no llego. Es primera vez que trabajo con este tipo de bd, y la estoy manejando como si fuera una Access.

    De pronto es mejor sustituirla por una de Access, por ahora, mientras aprendo.
    Friday, January 01, 2010 10:01 PM
  • Hola!

    El error 80004005 puede representar muchas causas.

    Creo que el siguiente enlace sea de gran utilidad para usted:

    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver][DBNMPNTW] ConnectionOpen(CreateFile()). 
     
    or 
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SQL Server does not exist or access denied. 
     
    or 
     
    Microsoft OLE DB Provider for SQL Server error '80004005'  
    [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied.  
     
    or 
     
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'  
    [Microsoft][ODBC SQL Server Driver][Named Pipes] Specified SQL server not found.  
     
    or 
     
    Microsoft OLE DB Provider for ODBC Drivers error '80004005' 
    [Microsoft][ODBC SQL Server Driver] Client unable to establish connection.
     
    While the first error message is definitely more cryptic than the others, they all mean the same thing. The first simply uses DBNMPNTW, which is the protocol name for named pipes. What the error means is that the SQL Server you defined in your connection string is invalid - either because it is currently down, you named it wrong (either by hostname, DNS/domain or IP address), or you don't have permission to connect. 
     
    If you are expecting to connect by IP address, make sure you override named pipes (see  Article #2082 ).  
     
    If you are using SQL Server authentication, make sure both ends are set up for it (see  Article #2138 ).  
     
    If the error is 'SQL Server does not exist or access denied', see  KB #328306 , which has a large variety of possible causes and solutions. Also see  KB #888228   if you are trying to connect to a named instance within a SQL Server 2000 cluster. 
     
    If the ASP page and SQL Server are on the same machine, then it may be a loopback problem - try using 127.0.0.1, LOCALHOST, (local), or just a period (instead of the external IP or network name) in the connection string.



    http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html


    Saludos!
    Rafael Fagundes - Marque la respuesta como correcta si te ha sido de utilidad!
    • Marked as answer by daugusta Monday, January 18, 2010 7:21 AM
    Wednesday, January 06, 2010 1:06 PM