Re: SP3 Hangs on install - authentication
From: SQL Server Development Team [MSFT] (sqldev@microsoft.com)
Date: 01/28/03
- Next message: Barclay: "Re: SP3 Invalid instance name"
- Previous message: SQL Server Development Team [MSFT]: "Re: SP3 Hangs on install - authentication"
- In reply to: Tony: "Re: SP3 Hangs on install - authentication"
- Next in thread: Harald Ums: "Re: SP3 Hangs on install - authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "SQL Server Development Team [MSFT]" <sqldev@microsoft.com> Date: Tue, 28 Jan 2003 14:56:52 -0800
Hi, Tony,
What was the current version of MDAC when you tried to install SP3?
This is a known issue if you have an MDAC 2.6 Client or earlier. The current
work around is to change the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQuery
to "DBNETLIB". After the setup is complete, you can change the value back.
Thanks.
Yi Mao
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. "Tony" <tony@abc.com> wrote in message news:OCWyC8vxCHA.1580@TK2MSFTNGP09... > A couple of months ago when we were updating the production servers, three > instances couldn't be upgraded using windows security, and had to obtain the > sa info for them. It was no big deal on two of them but on the third the DBA > was off-site and the info couldn't be obtained during the upgrade. We just > changed it with EM but had to listen to him cry the next week. Why it would > not upgrade with win security is beyond me, and again it was only on 3 > instances of about 30. > > Tony > > > "Richard Waymire [MS]" <rwaymi@online.microsoft.com> wrote in message > news:O93gXwvxCHA.616@TK2MSFTNGP11... > > On the second part you can always connect with windows security and > > therefore there shouldn't be any password issues. Can you go into more > > detail on this? > > > > -- > > Richard Waymire, MCSE, MCDBA > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > "Tony" <tony@abc.com> wrote in message > news:u0huLpvxCHA.2916@TK2MSFTNGP09... > > > I gave up, we're at SP2 with all the fixes on the staging box. Our other > > > machines were already current so I'm not going to jump to SP3 on the > > > production machines until MS gets the kinks worked out. Why can't a > hotfix > > > take care of all the instances in one shot? This is a real pain in the > > ass. > > > > > > Another peeve. Who cares what the DB password is, I'm logged in as an > > ADMIN, > > > the ADMIN should be able to apply critical updates to a server > regardless > > of > > > the DB's password. > > > > > > Tony > > > > > > > > > > > > > > > "SQL Server Development Team [MSFT]" <sqldev@microsoft.com> wrote in > > message > > > news:eZsl$OvxCHA.2288@TK2MSFTNGP09... > > > > Well, two incomplete/fake/nospam email address so I can't follow up > > > > directly. If you could please reply back to the group with your > > sqlsp.log > > > > files attached from the c:\windows directory, I'll try to take a look > > and > > > > assist based on that input. > > > > > > > > Thanks, > > > > Tom. > > > > > > > > -- > > > > > > > > > > > >
- Next message: Barclay: "Re: SP3 Invalid instance name"
- Previous message: SQL Server Development Team [MSFT]: "Re: SP3 Hangs on install - authentication"
- In reply to: Tony: "Re: SP3 Hangs on install - authentication"
- Next in thread: Harald Ums: "Re: SP3 Hangs on install - authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|