Re: MSDE 2000 SP3a on a Windows 2003 server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jim Young (thorium48_at_hotmail.com)
Date: 02/20/04 

Date: Fri, 20 Feb 2004 09:48:00 -0800

Are you sure you installed MSDE 2000 SP3a? Versions previous to SP3 will
install on 2003 but you will get a warning in the event log that the
Ynetwork ports to the application are blocked with a directive to upgrade.
Tou could do a netstat -a to show what ports the server is listening on.
Also look in the log for SQL Server and see whether it is loading any
network protocols when starting up.

Jim

"Kaz" <ganthi753@yahoo.com> wrote in message
news:1394501c3f7b8$cd4bb5c0$a001280a@phx.gbl...
> I have installed MSDE 2000 SP3a on both Standard and
> Enterprise Windows Server 2003 with the same problem. I
> can login to OSQL or Enterprise Manager from the local
> machine with any valid account, but when I attempt to
> login with the same accounts from another computer in the
> network I am unable to connect. I recieve the following
> error:
>
> SQL Server does not exist or access is denied.
> ConnectionOpen(Connect())..
>
> If I install MSDE the same way on Windows 2000 or XP I
> have no connection problems.

Relevant Pages

  • Re: catalog is empty after populating
    ... SQL Server is installed as the "Microsoft Search" service cannot write it's ... Tools -> Event Viewer and review the Application event log. ... >is only 1 MB and the catalog doesn't contain any items. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: How Do I Prevent SQL 2000 From Posting This Message To The Event Viewer - Application Log
    ... situation (event log overload from transaction replication on 40+ DBs). ... Go to the SQL Server Properties via Enterprise Manager (i.e. right ... Erland Sommarskog wrote: ... TRACEOFF turns off the trace flag! ...
    (comp.databases.ms-sqlserver)
  • Full Text Indexing Error
    ... I see a lot of these in my Event log on the SQL Server for my Windows ... These documents will not be passed to MSSearch for indexing, ... therefore this failure will not be reflected in the end of crawl summary ...
    (microsoft.public.sqlserver.fulltext)
  • Re: 18456 Login failed for user NT AUTHORITYSYSTEM
    ... Associated with this is event id 17055 from MSSQLSERVER w/description 18456: Login failed for user NT ... These messages occur in bursts of of over 100 messages every 5 minutes and just flood the application event log w/entries I think what's going on is the Alert Engine is a service running under local system and is unable to connect to SQL server. ...
    (microsoft.public.sqlserver.server)
  • Re: error message not being logged to windows event log
    ... Anon restarted SQL Server after making the changes which ... Logging to the Windows event log is enabled by default for ... log and the Windows Application event log if you haven't ... I thought the login audit logging only went to file ...
    (microsoft.public.sqlserver.connect)