18456

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

From: Robob (Robob_at_discussions.microsoft.com)
Date: 11/03/04 

Date: Wed, 3 Nov 2004 12:00:03 -0800

Hello All,

We have started getting error 18456 when an Access (happens on two different
ones)accesses a SQL 2000 database. I read the knowledgebase articles and the
do not apply and the fixes don't work. As always, we are using the domain
(now AD) user login. Not sure when this broke, I am guessing some MS updates
broke it. Clients are XP SP2 and 2003 Terminal Server. Acess is 2k SP3.
Creating a SQL user does not help. Did the MDAC 2.8 reinstall and that is no
help.

Two oddities:

1. The ODBC test passes when using named pipes, we were able to use tcp/ip
in the past. We had to swich to named pipes for another app that talks to
the same SQL server. I believe the SQL is on SP3.
2. The Access front end does connect IF I login into the SQL server via RDP.

Please help,
Robert A. Ober

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)