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



  • 1. Error 1222 Lock request
    I received the Error 1222 lock request time out period when trying to open SQL Server Current Activity folder under the Management folder to display locks. This was caused by several locks. This made it very difficult to resolve the locks without the GUI. What would cause the SQL Server GUI to be unable to display the locks? Thank You, Mickey Autry XXXX@XXXXX.COM
  • 2. DBCC INDEXDEFRAG - Interleaved on the disks
    DBCC INDEXDEFRAG will not help if two indexes are interleaved on the disk. I see this everyone, but what does "interleaved on the disk" mean? Is that a composite index? Please send replies to: XXXX@XXXXX.COM
  • 3. What should I do with my Veritas SQL license?
    I apologize if this isn't exactly on topic here.....I just didn't know where else to go! My situation is this: My software company told me that to backup my SQL database I would need to purchase a SQL agent for our Veritas software. After I purchased the agent they told me...."oops!...By the way our database is an MSDE database!". The only way you can back up a MSDE SQL database is if you happen to have the SQL Enterprise Manager (due to some files that Veritas needs to access). And the only way to get that manager is to buy the full blown version of SQL which is fairly expensive! This makes my SQL agent useless to me unless I purchase the Enterprise Manager. So now I am stuck with a Veritas SQL Agent for Veritas Backup Exec. What can I do with it? My vendor won't let me return it because it is opened, however, it is a fully legitimate license and could be of good use to the right person. I purchased it wholesale and am not looking to make a profit on it....I am just looking to get rid of it for the wholesale price I paid for it! Please help! I do not want to have to explain to my boss why our department has an un-justified expense! Thank you! XXXX@XXXXX.COM
  • 4. Schema Modifcation Lock (Sch-M)
    Hello all, this is a 2 part question: 1. Is a Schema lock (Sch-M Lock) imposed on a table when an index is created, dropped or modified ? 2. Does a Schema Lock completely lock the table (including read access) I would expect both anwers are yes but it would be great to get a confirmation from someone who actually knows. Thanks Daniel

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

Postby razorwings18 » Wed, 21 Apr 2004 07:37:51 GMT

Hi all,

I've installed the following on my staging server (pretty fresh
- Windows XP SP1
- SQL 2000 Developer Edition
- 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, and One of
them runs a proxy, the other a mail server.


- 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=; Network
Library=DBMSSOCN; Initial Catalog=MYDATABASE; User ID=sa;


- 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 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.


- Server must be running under XP.
- SQL Server must use it's own login (Windows Authentication is not

I'll apreciate any help you can provide on solving the problem. Hope
you like the report-style format.

Thanks in advance.

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

Postby Wayne Snyder » Wed, 21 Apr 2004 08:56:14 GMT

When you connect using QA are you using the stand SQL login sa with your
password , or using a trusted connection... because it looks like the error
is simply telling you that the sa password is incorrect...

Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), C{*filter*}te, NC
(Please respond only to the newsgroups.)

I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.

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

Postby razorwings18 » Thu, 22 Apr 2004 05:36:37 GMT

I use sa, and can connect with every other user I create for the
database as well (from QA, that is). Actually, I figure the trusted
connection shouldn't even work as the server is configured right now.

Thank you for your interest.

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

Postby razorwings18 » Thu, 22 Apr 2004 06:31:34 GMT

Update: The line "Network Library=DBMSSOCN" was causing the problem.
What I've got to figure out now is a) Why it worked with the previous
XP installation - SQL7 and not with this one, and b) Why the
connection works with the production server and not with the local
staging server. That's an issue that belongs to some other group

Similar Threads:

1.EM vs QA login

This morning I have a (2000) server that continually 
times out when I try to connect via Ent. Manager.  It is 
registred through an sa Sql Server login that has not 
changed in months.  Also, I upped the login timeout in EM 
to 10 seconds and it still timed out.
The odd thin is this:  I can connect instantly through 
Query Analyzer through this same sa login and the server 
looks very quiet in Perf Mon.  
Is there something different about how Sql Server logins 
through Enterprise Manager?  Any ideas what would cause 

2.Direct Login To EM/QA


Is it possible to create a user which can connect to a SQL Server 2000 
database and can select, insert and update tables in a database through 
software (made in VB 6) but cannot login directly on Query Analyzer or 
Enterprise Manager Console?

Muhammad Bilal  

3.Not able to connect EM & QA...

 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 .

4.Connecting to a 2005 database using 2000 EM

What are the steps to be able to add a 2005 server to a server group in the 
2000 enterprise manager?

Thanks for any help,

5.Having Problem in using JDBC Driver for SQL Server 2000 SP3

I'm using jdk 1.5.0 and SQL Server PE,

when i user the driver, it returns

Socket Establishing Failure ...

anyone can help what's the problem is..

6. Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

7. EM does not display table created using QA

8. Login failed for user '(null)' - new laptop can't connect, using mixed mode



Who is online

Users browsing this forum: No registered users and 69 guest