Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess
From: Matt Emmott (matt_at_jerkychew.com)
Date: 09/21/04
- Next message: Gideon Rashkes: "Re: detecting a dead connection"
- Previous message: john: "Re: Getting tables list in 64 bit platform"
- In reply to: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Next in thread: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Reply: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Messages sorted by: [ date ] [ thread ]
Date: 21 Sep 2004 09:40:27 -0700
Matt Emmott here, posting from google instead of Microsoft's
newsreader. Anyways,
TCP/IP and named pipes are both enabled, according to the server
network utility. Any other ideas?
"Brannon Jones" <brannonjNOSPAM@gmail.com> wrote in message news:<uc0rY5CnEHA.2680@TK2MSFTNGP15.phx.gbl>...
> 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: Gideon Rashkes: "Re: detecting a dead connection"
- Previous message: john: "Re: Getting tables list in 64 bit platform"
- In reply to: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Next in thread: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Reply: Brannon Jones: "Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
