| Author |
Topic |
|
charlietritran
Starting Member
5 Posts |
 Posted - 2004-08-25 : 13:45:57
|
| Hi ALl,I am new to SQL serer 2000 database. I would like to know if you can help me out for accessing to the SQL server 2000 database remotely in a network enviroment. I have upsized an Access database to an SQL server 2000 database situated in a WIN 2003 Server PC. Actually, I moved only the tables of Access database to SQL and keep all othe objects in Access 2000. I created a shared directory in that machine that hold the access database front-end. When I open the access database, I am able to open the all tables that linked to SQL database due to upsizing. I am even be able to update those table from Access database. Now, I go to another PC in the network and map a driver to that shared directory of the SLQ server machine and be able to open the Access database. But I can not open the linked table. It hang up for a while and display the folowings:=========Connection: failed:SQLState: '01000'SQL Server Error: 53[MIcrosoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()).Connection: failed:SQLState: '08001'SQL Server Error: 17[MIcrosoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.=========I do not know waht is the problem? The client machine have Win Pro2000, and access 2000. Do I need to install more softwares, components? Do I have to reconfigure the SQL server machine? Does anyone have any idea to help me? I need your help?Thank you in advance,CHARLIE |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-25 : 13:51:29
|
| That error typically either means that the MSSQLSERVER service is stopped or you need to setup an alias on the client to specify how to connect to the database server. Verify the service is started (Control Panel, Admin Tools, Services). If it is, are you using the default SQL port? If not, you'll need an alias. Can the client ping the database server by its server name? By its IP address?Tara |
 |
|
|
charlietritran
Starting Member
5 Posts |
Posted - 2004-08-25 : 14:04:01
|
quote:
Originally posted by tduggan
That error typically either means that the MSSQLSERVER service is stopped or you need to setup an alias on the client to specify how to connect to the database server. Verify the service is started (Control Panel, Admin Tools, Services). If it is, are you using the default SQL port? If not, you'll need an alias. Can the client ping the database server by its server name? By its IP address?Tara
Hi Tara,Thank you for responding to my request. The MSSQLSERVER service starts all the time. According to you, I may need to create an alias. Can you tell me how to do it? I just install the SQL Server 2000 on hte server machine and let everything went by default. I do not know if I need more configurations done manually or not, even for the WINDOW 2003 server. When I created an .ASP page in the SQL Server 2000 PC and using IIS to run it with the same machine, it is working fine. But when I run that .ASP page from the other machine like http://164.117.32.23/aspTest/Test.asp, it said that no permission....with errorDo you have any idea?thank you,Charlie |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-25 : 14:06:48
|
| Do you have the SQL client tools installed on the client machine? If so, you can create the alias with Client Network Utility. Otherwise, you'll need to write to the registry.But can you ping the database server by its name from the client machine? If so, then you don't need an alias as you are using the default port.Tara |
|
|
|
charlietritran
Starting Member
5 Posts |
Posted - 2004-08-25 : 16:28:51
|
| Hi Tara,I can only ping the IP of the SQLSERVER PC: ping 164.117.34.43. When I tried ping DATABASE_NAME and it failed. Should I need Client Network Utility installed on the client PC while I do not directly access the SQL Server DB but through an access front-end db in the SQL Server PC's shared directory?Thanks,Charlie |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-25 : 16:37:06
|
| You will need to add the alias via the registry. This will be done on the client machine. I would do a forum search using my username and the word dbmssocn. I have described to others a few times what needs to happen. If you don't want to do the alias, you could find out why the DNS server isn't resolving the hostname to an IP address. You could also hard code the information in the client's hosts file.Tara |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2004-08-25 : 16:46:44
|
| When you say mapped a driver...does that mean you created a new ODBC connection on the client?If so did you test the connection?Go to Control panel and look at ODBC data sources and see if you see the connection there...If they're on the same network it shouldn't be a problemEach client needs an odbc connection...not a drive mapping...Brett8-) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-25 : 16:48:43
|
| I was confused by that too:"map a driver to that shared directory"What shared directory? You don't connect to directories.Tara |
|
|
|
charlietritran
Starting Member
5 Posts |
Posted - 2004-08-25 : 17:02:31
|
| Hi Tara,Thank you. I will try it and let you know tomorrow.Thanks,Charlie |
|
|
|
charlietritran
Starting Member
5 Posts |
Posted - 2004-08-25 : 17:17:36
|
| Hi Tara & Brett,I am sorry to confuse you guys. Let me restate the question:I have a machine A having Win Server 2003 and SQL Server 2000 ENT. I create a shared drive D on the machine A and having an access database in it. I , then upsize the access database to move all tables to SQL server database. The new SQL server db is created: ACCESS_DBSQL. This database will hold all the tables of the access database. When I open the tables from the access database located in the D drive, I can see the data. Of course, these tables have become linked tables. But when I use another machine say C, and open window explore, go to tool -> map network drive -> and map a drive say X to the shared drive D of machine A. That will allow me to open the access database of machine A. But I will get hung up when I try to open the linked tables of the database. It seems not having enough permission or I need more configurations. I do not know for now.That is the problem. I would know if you guy can help me?Thanks,Charlie |
|
|
|
wlynnsargent
Starting Member
6 Posts |
Posted - 2004-08-25 : 19:08:38
|
Charlie,I'm assuming that you used a DSN/ODBC connection to perform the upsizing process. When the linked tables are created in the Access DB, they are tied to the SQL tables through that same DSN definition. (Same as if you linked the tables yourself through "Get External Data...")If the DSN was set up to connect to SQL using a saved SQL login and password, that data should be retained in the Access MSysObjects table, thus allowing you to run it (more or less) on any networked machine. If, however, another authentication method was used, or the UID/password was not explicitly saved as part of the upsizing, it is possible that you might need to set up a copy of the original DSN on every PC that is to run the Access database.One other alternative might be to delete the linked tables from the Access database (be sure to make a backup of your .MDB first) and relink them, making sure to tick the 'Save Password' checkbox on the table selection dialog.Not sure if this helps, but having been through this myself about a year ago, I figured it couldn't hurt...  -Lynn S.Gee, it would sure be nice if it did that...maybe in the next revision...or not... |
|
|
|
j4ydh
Starting Member
18 Posts |
Posted - 2004-09-09 : 10:18:13
|
| HiThis may or may not help someone.I am running Visual Studio.net, Dreamweaver MX2004, sql server 2000 and my work station is WIN XP pro. I am writing code in VB.net with sql page code and stored procedures.I have found that when using OLE or SQL connections to databases using the above in any combination the following error occurs:DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.The user rights are correct on both forms of db authentication.The overriding problem seems to be that when I call localhost, sqlserver name as localhost or anything other than an IP number the problem occurs.I can connect fine through a VPN and IP conversion online but I can't preview the contents locally through explorer. But I can access in both Dreamweaver and VS.net the Dbase data to work with.I am not sure if MDAC 2.8 is the problem or potentially XP. If you really want connection problems and a wasted weekend download XP service pack 2.Good luck |
|
|
|
budgy2
Starting Member
2 Posts |
Posted - 2004-09-25 : 06:22:13
|
| I am having a simular problem. Has anyone found a fix? |
|
|
|
budgy2
Starting Member
2 Posts |
Posted - 2004-09-25 : 06:22:14
|
| I am having a simular problem. Has anyone found a fix? |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-26 : 23:28:32
|
| if you're trying to access a server across a network, do not use localhost, register the instance with a unique name which it can be readily identified. I had this problem few months back and resolved it by checking if the network name is equivalent to the sql server name, if you rename a server computer then rename the sql server also with the same name.hi charlie, we had a similar problem on our Informix server and found out that after the upgrade, the odbc version is not compatible with mdac.hope this helps... |
|
|
|
nigel@csimedia.net
Starting Member
1 Post |
Posted - 2004-10-05 : 07:19:13
|
I too am having a similar problem to this. I have a Windows 2003 machine connecting to a separate SQL Server 2000 machine via ASP (classic) using the IP address and port number.I only get the problem occasionally. Can anyone help with this?ThanksNigel |
|
|
|
|
trouble accessing sql server 2000 database remotel