Re: SP3a won't install
From: Steve Thompson (SteveThompson_at_nomail.please)
Date: 04/27/04
- Next message: A. Cave: "Patching Named Instance"
- Previous message: Bobtcny: "SP3a won't install"
- In reply to: Bobtcny: "SP3a won't install"
- Next in thread: Bobtcny: "Re: SP3a won't install"
- Reply: Bobtcny: "Re: SP3a won't install"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Apr 2004 14:58:31 -0400
It's not clear to me whether you are using SQL or Windows Authentication?
Any error codes during setup?
Also, leaving your 'sa' password blank is a MAJOR security risk and asking
for trouble on any network that is used by more than one computer.
Steve
"Bobtcny" <rptNoSpam18@hotmail.com> wrote in message
news:507e01c42c7d$30509ca0$a001280a@phx.gbl...
> Full SQL Server 2000 installed on Windows 2000 with Named
> Pipes. SA password must be blank because the software ew
> install requires a blank password. MDAC is 2.7. SP3a
> installs on most machines with no problem. On some, SP3a
> will not install because it cannot verify user either in
> Windows Auth. or SQL Logon. Cannot log on using OSQL
> either. Enabling TCP/IP does not solve the problem. The
> software can connect to the database. Enterprise manager
> sees the database and we can set properties, such as
> authentication. Any ideas on why we cannot log on using
> either Windows Auth. or SA? Or how we can get SP3a to
> install?
- Next message: A. Cave: "Patching Named Instance"
- Previous message: Bobtcny: "SP3a won't install"
- In reply to: Bobtcny: "SP3a won't install"
- Next in thread: Bobtcny: "Re: SP3a won't install"
- Reply: Bobtcny: "Re: SP3a won't install"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
