Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Cannot Connect To Database?

Cannot Connect To Database?

Scheduled Pinned Locked Moved Database
questiondatabasec++sql-serversysadmin
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    Dominick Marciano
    wrote on last edited by
    #1

    My company is currently running SQL Server 2005 and we have out main project database set up on it. Everyone in the company can connect to it through Access using a linked table. This was setup a little while back by another company. However my company has now asked me to create a small database on the server. So I logged into the server, created the database, added the needed columns and the data we have already accumulated that need to be in the database. However when I try to link it through Access it won't let me; the connection fails. I can't do it through the ODBC Data Source Administrator either. I did notice though that when I try and create a new data source through the ODBC Admin that regardless of whether I select SQL Server or SQL Server Native Client 10.0 our main project database comes up (it is set up though to use SQL Server not the Native Client), however the new database only comes up if I select SQL Server Native Client 10.0. I'm thinking, and hoping, this is why I can't connect to the database from my laptop but I'm not sure. Why does the new database only come up under the SQL Native, but the main project database comes up under both, and how can I make the new database come up under the SQL Server option? I've compared both database properties and everything seems to be exactly the same. I'm pretty new to SQL Server but the company has put this on me and given me a week to get it up. Any help would be greatly appreciated. Thanks. Dominick

    D J 2 Replies Last reply
    0
    • D Dominick Marciano

      My company is currently running SQL Server 2005 and we have out main project database set up on it. Everyone in the company can connect to it through Access using a linked table. This was setup a little while back by another company. However my company has now asked me to create a small database on the server. So I logged into the server, created the database, added the needed columns and the data we have already accumulated that need to be in the database. However when I try to link it through Access it won't let me; the connection fails. I can't do it through the ODBC Data Source Administrator either. I did notice though that when I try and create a new data source through the ODBC Admin that regardless of whether I select SQL Server or SQL Server Native Client 10.0 our main project database comes up (it is set up though to use SQL Server not the Native Client), however the new database only comes up if I select SQL Server Native Client 10.0. I'm thinking, and hoping, this is why I can't connect to the database from my laptop but I'm not sure. Why does the new database only come up under the SQL Native, but the main project database comes up under both, and how can I make the new database come up under the SQL Server option? I've compared both database properties and everything seems to be exactly the same. I'm pretty new to SQL Server but the company has put this on me and given me a week to get it up. Any help would be greatly appreciated. Thanks. Dominick

      D Offline
      D Offline
      David Mujica
      wrote on last edited by
      #2

      First test is to see if you can "ping" the server. This will test that the network connection from your machine to the server is running. Open a command prompt and type "ping yourservername", (no quotes and substitue your server name for the first parameter. Start with the simple stuff. :)

      1 Reply Last reply
      0
      • D Dominick Marciano

        My company is currently running SQL Server 2005 and we have out main project database set up on it. Everyone in the company can connect to it through Access using a linked table. This was setup a little while back by another company. However my company has now asked me to create a small database on the server. So I logged into the server, created the database, added the needed columns and the data we have already accumulated that need to be in the database. However when I try to link it through Access it won't let me; the connection fails. I can't do it through the ODBC Data Source Administrator either. I did notice though that when I try and create a new data source through the ODBC Admin that regardless of whether I select SQL Server or SQL Server Native Client 10.0 our main project database comes up (it is set up though to use SQL Server not the Native Client), however the new database only comes up if I select SQL Server Native Client 10.0. I'm thinking, and hoping, this is why I can't connect to the database from my laptop but I'm not sure. Why does the new database only come up under the SQL Native, but the main project database comes up under both, and how can I make the new database come up under the SQL Server option? I've compared both database properties and everything seems to be exactly the same. I'm pretty new to SQL Server but the company has put this on me and given me a week to get it up. Any help would be greatly appreciated. Thanks. Dominick

        J Offline
        J Offline
        jschell
        wrote on last edited by
        #3

        So a summary of the problem is as follows. There is ONE database server - one physical box. On that server there is database A. On that server you created database B. On your client box you CAN do the following with A (NOT B.) - Create an ODBC connection and validate it. - Via a NEW Access database, create a linked table to it And with Database B you CANNOT do the above. Given that we know for sure that is NOT a connection problem (per the other response.) And the driver shouldn't have anything to do with it. What it would suggest to me is that it is one of the following 1. User permissions on the database B. This is most likely. 2. Some odd firewall rules. This is hypothetical but I don't consider it impossible. Such a rule would need to be more than just a standard connection rule.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups