Answered SQL Database not getting connected!!!

  • 6. března 2012 9:54
     
     

    I have 2 vista machines, joined to the domain.

    • On One machine I have Installed SQL 2008 SP1 (version 10.0.2531).
    • On the other machine I have installed SQL 2008 R2 (version 10.50.1600)

    Problem:

    When I try to access the DB created on both the machines using the Management Studio of SQL 2008 R2 edition, I have no problems connecting the DB. But when I try to access both the DB using the Management Studio of SQL 2008 SP1, I could connect only to the DB created locally on SQL 2008 SP1 and could not connect to the DB created on SQL 2008 R2.

    Question:

    • Is this the default behaviour, as there is a version mismatch on both the SQL DB? 
    • The older version of SQL cannot access the DB created on the newer version of the SQL?

    Could anyone give me a technical details as to why this happens.

    Thanks and Regards,

    Pralhad

Všechny reakce

  • 6. března 2012 10:12
     
     

      The older version of SQL cannot access the DB created on the newer version of the SQL?
    Don't you think this would be obvious?

    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Jeff Wharton
    MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCSD, MCITP, MCDBA
    Blog: Mr. Wharty's Ramblings
    Twitter: @Mr_Wharty
    MC ID: Microsoft Transcript

  • 6. března 2012 11:25
     
     



    Hi,

    You can use Management Studio to connect to later versions of SQL Server - eg SSMS SQL 2005 can
    connect to SQL Server 2008 r2. You won't have the full range of features available to you.

    You cannot backup ad db
    from a later version and restore it to an earlier version.<o:p></o:p>

    Can you connect to any
    other servers from the 2008 sp1 box? is it possible that you have TCP?IP
    disabled on one of the boxes - or a firewall rule blocking access.

    Do you get an error message when you try to connect?

    Seth<o:p></o:p>



    http://lqqsql.wordpress.com

  • 6. března 2012 12:02
     
     

    You can access sql 2008 r2 from a management studio of sql 2008 it works perfectly fine for majority of the features and I have been doing that till last month.

    The reason that you cannot connect could be due to connectivity issues, authentication issues etc.

    Are you able to ping the sql 2008 r2 server from this server properly? Have you enabled the protocols correctly? Are you able to do a UDL test? Do you get any error message?


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • 7. března 2012 8:04
     
     

    Hi Lynch,

    I am not able to connect to the DB..I checked that my firewall is turned off and my TCP/IP is not disabled.

    Error Message:

    ===================================

    Cannot connect to GO-TESTING-PC05\SQLEXPRESS.

    ===================================

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)

    ------------------------------
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

    ------------------------------
    Error Number: -1
    Severity: 20
    State: 0


    ------------------------------
    Program Location:

       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

    Regards,

    Pralhad.


    Pralhad

  • 7. března 2012 8:08
     
     

    Hi Ashwin,

    I am able to connect to one DB on the server..but the other database is howing the error.

    I am able to ping the server properly. Could you let me know what protocols need to be enabled, as I am not sure about the same. Could you also provide me detials how to preform UDL test.

    I get the following error message when I try to connect.

    ===================================

    Cannot connect to GO-TESTING-PC05\SQLEXPRESS.

    ===================================

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)

    ------------------------------
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

    ------------------------------
    Error Number: -1
    Severity: 20
    State: 0


    ------------------------------
    Program Location:

       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser().

    Thanks for your help..

    Regards

    Pralhad


    Pralhad

  • 7. března 2012 8:42
     
     Odpovědět

    Hello Pralhad,

    Can you go through this article and make sure everything is correct as per this?

    http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx

    HTH


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com