×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

I'm not allowed to create an ODBC connection using the Data Sources Ut

I'm not allowed to create an ODBC connection using the Data Sources Ut

I'm not allowed to create an ODBC connection using the Data Sources Ut

(OP)
Hi,
I have Windows XP Home in my computer and I'm trying to connect to a SQL Server 7.0 database using the tool provided by the Administrative tools called "Data Sources (ODBC)" but whenever I type the server, the the username and password and click on next on the assistant, an error message stating that the server does  no exist (SQLState: '08001' and SQL Server Error: 17), therefore I cannot connect to the database located in the server i need to connect to.
I was wondering if maybe the fact that I have win Xp instead of Pro, could make this happen, since I cannot connect to the domain I need to be connected to.
Can anybody help me here please, I'm desperate and I need to connect to that database or my boss will kick me out.

Thanks

RE: I'm not allowed to create an ODBC connection using the Data Sources Ut

XP Home vs Pro should not make a difference.

What do you mean you cannot connect to the domain? You MUST be connected to the domain (network) on which the SQL server exists in order to create/use the connection

-- Jason
"It's Just Ones and Zeros"

RE: I'm not allowed to create an ODBC connection using the Data Sources Ut

(OP)
Ok, Thanks for the tip, that's all I needed to know, anyway, I managed to solve the problem. The problem was the pipe name that the system was using to reach the server, But I finally managed to fix it. Know I have another problem...
The ODBC conection is created, but whenever I try to map the server in the Microsoft's SQL Server 7.0 Enterprise Manager, I start getting the same message. On the other hand, if I use the Query Analyser, I can connect without any problem. Does anyone know what I could do to fix the problem in the Enterprise manager so I can see the database I need??

Thanks

Faeton13

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close