1. remember that Multiprotocol can not connecdt to a named instance.. and 2. I know this is stupid, but make sure the instance is running and 3. the proper ports are open if you have the serve machine locked down...
1. remember that Multiprotocol can not connecdt to a named instance.. and 2. I know this is stupid, but make sure the instance is running and 3. the proper ports are open if you have the serve machine locked down...
On Tue, 2 Sep 2003 08:00:53 -0400, "Wayne Snyder" OK, let me start over... I'm connecting via TCP/IP. TCP/IP is the only library defined in client/server network utilities. The named instance is running...I can connect to it with Query Analyzer. All the relevant ports are open (behind a firewall <g>) Also, after trying to "register" the server from the remote computer in EM, the registration is successful but I can't connect. Then, when I try to right-click the registration to delete it, there's a 30-second pause before the options menu pops up, and it closes immediately before I can select "delete". Is it safe to delete the registration from the registry (assuming I close EM first)?
1.Not able to connect EM & QA...
hi, I am not able to connect my SQL Server 2000 Machine, from client, EM & QA both are giving following error. A connection could not be established to [Server Name] Reason: Data source name not found an dno default driver specified. I am not able to understand before few minutes I was connected from same client and now it's giving error plz help .
2.Please HELP: SQL 2000 SP3a & EM: Can't register a Server
Here's the setup Win XP SP1 With SQL Server 2000 Enterprise Edition with SP3a installed. It worked on the desktop prior to the application of SP3. SP3a was in an attempt to fix it. On my laptop I CAN register a server just fine using sql authentication, on the desktop, I get A connection could not be established to XXXXXXXX Server does not exist or access denied I can't say config are identical anymore becuase I've tried reading and doing everything suggested to solve this, and I'm sure I know have MDAC 2.8 on the deskop and MDAC 2.7 sp1 on the laptop. I've been at this for 3 days with no luck.
3.SQL 2000 Developer - Login Failed using SQLOLEDB, QA and EM have no problem connecting
Hi all, SETUP ----- I've installed the following on my staging server (pretty fresh installs): - Windows XP SP1 - SQL 2000 Developer Edition - Server MYSERVER - Uses TCP/IP in standard port and Named Pipes in standard folder. Security is set to: - Service account: System Account - Authentication: SQL Server and Windows - SA has a password assigned I created the following database, with no tables (other than system, of course) for login testing purposes: - Database: MYDATABASE Misc. info: - Server has two IPs assigned, 192.168.0.2 and 192.168.0.11. One of them runs a proxy, the other a mail server. PROBLEM ------- - Trying to connect to the database from within my ASP and VB applications returns "Login failed for user 'sa'.". - Connection string is as follows: "Provider=sqloledb; Data Source=192.168.0.2; Network Library=DBMSSOCN; Initial Catalog=MYDATABASE; User ID=sa; Password=mypassword;" FACTS ----- - I can connect with no problems with both Query Analyzer and Enterprise Manager using MYSERVER as data source. - That very same connection string works perfectly when connecting to the production server (running SQL 7.0 on XP) on another IP. - SQL Server 7.0 was working just fine on this very same machine prior to a complete format and reinstall. Failed workarounds: - I've also tried using 192.168.0.11 and MYSERVER as Data Source. - I've created a new user and login with ownership over MYDATABASE. Same problem arises. - I've updated to MDAC 2.8. LIMITATIONS ----------- - Server must be running under XP. - SQL Server must use it's own login (Windows Authentication is not acceptable). I'll apreciate any help you can provide on solving the problem. Hope you like the report-style format. Thanks in advance.
4.Can't connect to remote sql server from asp.net buk ok from Enterprise Manager
Remove now aspnet user from admin group! (no matter is a test server, is a bad practique). You server is win2003? I don't can connect to Sql Server using NT authentication but with Sql Server authentication is fine. Create user group with the rigth permision on the database, create a user (like WebUser) with strong password and connect with it...
I suddenly can't work with my Enterprise Manager. It tells me that log in failed - Can't access user's default database. What can I do about it? I really need to fix it fast. Thanks a lot Shimon.
Users browsing this forum: No registered users and 90 guest