Re: AUTHENTICATION TO APPLY SP3

From: SQL Server Development Team [MSFT] (sqldev@microsoft.com)
Date: 02/03/03


From: "SQL Server Development Team [MSFT]" <sqldev@microsoft.com>
Date: Mon, 3 Feb 2003 10:38:15 -0800


You should probably call support and get an expert's opinion, but if it were
me, I'd probably try updating to MDAC 2.7 SP1 manually, rebooting the
computer, and trying to install SP3 again. :-) Sqlredis.exe does this and is
in the x86\other directory where you expanded the service pack download.

DSQUERY is indeed a string value.

Hope this helps!
Stephen Dybing, Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to the newsgroups only, thanks.

"Jim K" <jking@shumakerengineering.com> wrote in message
news:04b901c2cba1$22553d60$8ef82ecf@TK2MSFTNGXA04...
> I am receiving the same error.
>
> I went to apply the fix recommended below, but I do not
> have the value DSQUERY. Could that be my problem?
> Should I add this value (as a string I assume)?
>
> Additionally, When I apply the patch it asks me to choose
> an instance if SQL. I only have one instance of SQL
> installed, however it is named. When I get to this screen
> in the patch intall, I do not have the option to change
> it from default to my named instance. The option is
> greyed-out. Is this ok, or should I be able to change it?
>
> Thanks in advance.
>
>
>
>
> >-----Original Message-----
> >What's the error message that you're getting? If you're
> not getting any
> >error message at all, you're probably running MDAC 2.6
> and you need check
> >the following registry key:
> >
> >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\
> ConnectTo\DSQUERY
> >
> >Set it to DBNETLIB if it's currently set to anything
> else.
> >
> >If you're getting an error message about setup being
> unable to validate you,
> >try replacing the current dbmslpcn.dll file with the one
> from SP3 and try
> >running setup again. This is usually in the
> windows\system32 directory.
> >
> >Hope this helps!
> >Stephen Dybing
> >
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >Please reply to the newsgroups only, thanks.
> >
> >"Joe D" <jdanajovits@cabreraservices.com> wrote in
> message
> >news:08f701c2c932$5b0b2500$d3f82ecf@TK2MSFTNGXA10...
> >> Info Returned from SQLScan:
> >> SQL Server 2000 RTM Standard Edition
> >> ssnetlib.dll @version=2000.80.194.0
> >> sqlservr.exe @version=2000.80.194.0
> >>
> >> - Running the patch from server console
> >> - Logged on as administrator
> >>
> >>
> >>
> >> Problem:
> >> When I try to run the SP3, the process fails to
> >> authenticate with either the sa user or the current
> >> windows user.
> >>
> >> These accounts and passwords are good because I can get
> >> access to query analyzer using either account.
> >>
> >> Any help would be appreciated!
> >>
> >> Joe D.
> >>
> >>
> >
> >
> >.
> >



Relevant Pages

  • Re: SQL Server Express requires MDAC
    ... could you please post the error message in here. ... SQL ... Server 9.0 normally uses its own client library, ... with MDAC but this should be no prerequiste. ...
    (microsoft.public.sqlserver.setup)
  • MS02-61
    ... Upon running SP2 it failed at the MDAC screen. ... Went into SQL and it gave the same error message as after ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2005 Express Edition + Advanced Services SP3 (KB255706)
    ... How many instances of SQL Server Express do you now have? ... SP3 but that update is in the list probably ... if I do try to down load and install from, Vista Ultimate, Avalable Updates ... I contiually get the error message "SQL BPA command line has stopped working" ...
    (microsoft.public.sqlserver.setup)
  • SP4 Error
    ... Win 2000 server with SP4, SQL 2000 server without SP ... and then I tried to apply SP3 and got similar error message ...
    (microsoft.public.sqlserver.setup)
  • Apply SP4 problem
    ... Win 2000 server with SP4, SQL 2000 server without SP ... and then I tried to apply SP3 and got similar error message ...
    (microsoft.public.sqlserver.setup)