SQL 2000 Developer - Login Failed using SQLOLEDB, QA and EM have no problem connecting

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: rw18 (razorwings18_at_hotmail.com)
Date: 04/19/04 

Date: 19 Apr 2004 15:37:51 -0700

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.

Relevant Pages

  • Re: Sql Server 2005 Dev. Ed. on Windows Server 2003
    ... Check out this KB which is about transferring Logins: http://support.microsoft.com/kb/246133 ... Also, since this is running on a newly installed Windows Server 2003, is ... them from your older SQL Server instance to the newer one. ...
    (microsoft.public.sqlserver.setup)
  • Re: New Windows Infrastructure
    ... vendor's application runs on windows with an SQL database and I will also need a web server for a separate module which will allow our customers to access account data online. ... I would think that if the app runs on windows, I do not need the citrix server. ... It makes sense to have separate DCs though, because let's say you want to upgrade your Active Directory in two weeks time, with separate DCs it's easy, but if you've got a bunch of apps installed it could be a nightmare. ...
    (microsoft.public.win2000.setup_deployment)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.sharepoint.portalserver.development)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.office.developer.web.components)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.inetserver.iis)