RE: SQL server Login connection failed sqlstate 28000 sql server err 1

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

From: Michael Cheng [MSFT] (v-mingqc_at_online.microsoft.com)
Date: 01/11/05 

Date: Tue, 11 Jan 2005 11:15:42 GMT

Hi aleksg01,

>From your descriptions, I understood that your application remains working
fine until you try to save the version that was relinked. Have I understood
you? Correct me if I was wrong.

First of all, what's your SQL 7's version? Have you make sure to upgraide
the latest service pack, which should be SQL Server 7 SP3

SQL Server 7.0 Service Pack 3 for Intel Platforms
http://www.microsoft.com/downloads/details.aspx?FamilyID=9c71f91c-a88f-4d31-
9e8b-9fd63fbdbdcf&DisplayLang=en

Secondly, you are using mdb or adp file? I have noticed that if a new file
was made, everything was fine, right? Is it possible for you to use some
other SQL client tools to connect the SQL Server from this XP SP2?

If not, the following links in the Knowledge base article might help

How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/kb/841251

How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/kb/841249

Thirdly, please download Component Checker from the link below to make sure
the integrity of your MDAC

MDAC Utility: Component Checker
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-
bf53-14332ef092c9&DisplayLang=en

Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!

Sincerely yours,

Michael Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Get Secure! - http://www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)