Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess

From: Brannon Jones (brannonjNOSPAM_at_gmail.com)
Date: 09/16/04

  • Next message: anya parker: "Re: > > > > this statement is made pending the issue of the official complaint against matt parker matt parker alias f quisinsky matt parker alias sam smith matt parker alias evanlint hout matt parker alias taniadchenka do physical material and moral" 
    Date: Thu, 16 Sep 2004 13:43:42 -0700

    Those version numbers should be fine. SQLOLEDB.DLL and SQLSRV32.DLL don't
    have any dependencies between each other (one is the OLEDB provider, the
    other is the ODBC driver).

    Check the Drivers tab in the ODBC administrator. Is it empty? Does it list
    "SQL Server"?

    Make sure that SQL Server is configured properly to accept off-the-box
    connections. The TCP/IP and Named Pipe protocols need to be enabled.

    I installed Small Business Server at home, and it will install MSDE. If I
    remember correctly, the MSDE instance is not configured for off-the-box
    connectivity. Maybe SBS setup configured your existing SQL Server to
    disable TCP/IP and Named Pipes. Use the Server Network Utility to check and
    configure this.

    Good luck,
     Brannon

    "Matt Emmott" <memmott@gmail.com> wrote in message
    news:212001c49a7d$f57e2150$a301280a@phx.gbl...
    > Hi all,
    > We recently upgraded our SQL 2000 server from Windows 2000
    > server to windows Server 2003 Small Business Edition.
    > After the upgrade, the existing server connections still
    > work (we're using it for Great Plains), but there's a
    > boatload of problems. In short:
    >
    > 1) No clients can connect to the server using ODBC
    > connections. All connectivity tests fail
    >
    > 2) From that server, I can't create any ODBC connections
    > at all. When I go to administrative tools -> Data sources,
    > and try to create a new connection, the box where the
    > different connections should be listed is empty, and my
    > only option is 'finish'
    >
    > 3) I can't upgrade the server to SQL SP3. It gets to the
    > point where it wants a password, but the password always
    > fails, saying it can't authenticate.
    >
    > I only want to get the connection up long enough to move
    > the data to a new SQL 2000 server. But since I can't
    > connect to the database with any of the SQL tools, I'm
    > kind of stuck.
    >
    > I ran the MS Component Checker against the box. All the
    > MDAC files are 2.8, but it looks like there may be an
    > inconsistency with the SQL DLL files. The SQLOLEDB.DLL
    > file is version 2000.85.1022.0, while the SQLSRV32.DLL
    > FILE is version 2000.85.1025.0. If the file version is the
    > problem, how do I go about fixing it?
    >
    > Thanks in advance.
    > -Matt

  • Next message: anya parker: "Re: > > > > this statement is made pending the issue of the official complaint against matt parker matt parker alias f quisinsky matt parker alias sam smith matt parker alias evanlint hout matt parker alias taniadchenka do physical material and moral"

    Relevant Pages

    • Re: SQL Server extremely slow
      ... terms of what is meant by a dis-connected ado recordset. ... table in a mdb file could be considered disconnected from the server ... Well, ok, but keep in mind the disk drive is on sql server! ... 10 reocrds from the server via odbc does not produce more ...
      (comp.databases.ms-access)
    • Re: VB app connect THROUGH proxy to a remote SQL database
      ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
      (microsoft.public.dotnet.languages.vb)
    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... If I cut the maximum number of connections to for ... SQL Server simply blocks any further try to open another table until I close ... This doesn't happen with the SQL Server 2000 but with SQL Server ... No, I think ms-sql-s means that SQL 2000 is using port 1433, which is ...
      (microsoft.public.sqlserver.connect)
    • Linked server to ODBC DSN
      ... Server, and want to create a linked server to this same ODBC DSN: ... Provider = "Microsoft OLE DB Provider for ODBC Driver" ... Then i connect to the SQL Server using QA, and try to run my query (that ...
      (microsoft.public.sqlserver.server)
    • Re: DAO vs ADO
      ... > to re-write it at least a little but can I do it in DAO? ... > tables were on a SQL Server! ... ODBC, one table could be on the corporate server, and the other ODBC might ...
      (microsoft.public.access.conversion)