Re: SQL SLAMMER

From: Kelly (kelly@nomail.com)
Date: 01/28/03


From: "Kelly" <kelly@nomail.com>
Date: Tue, 28 Jan 2003 13:37:41 -0800


It was MDAC 2.6 (to the best of my knowledge..)

I was at SQL 2000 SP2 on that box..

Thanks for the replies..
-Kelly Barutt

>-----Original Message-----
>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 as described
below. After the
>setup is complete, you can change the value back.
>
>Thanks
>Rajesh George
>
>--
>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.
>"Kelly" <kelly@nomail.com> wrote in message
>news:041c01c2c712$404508c0$d2f82ecf@TK2MSFTNGXA09...
>> It was DBNMPNTW.. (If you can elaborate on what that
>> means that would be great, I'm assuming named pipes.. Is
>> this the order they are in in the client network
utility)
>>
>> Thanks...
>>
>> >-----Original Message-----
>> >what was the previous value in the reg key? This just
>> says the default sql
>> >server connection should use the DBNETLIB library
(which
>> is the default SQL
>> >Server 2000 network library).
>> >
>> >--
>> >Richard Waymire, MCSE, MCDBA
>> >
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >"Kelly" <kelly@nomail.com> wrote in message
>> >news:084301c2c70e$c417d140$8ef82ecf@TK2MSFTNGXA04...
>> >> This worked for me... But anyone know why?? (Teach
me
>> to
>> >> fish!!)
>> >>
>> >> Thanks...
>> >>
>> >> >-----Original Message-----
>> >> >I had the same issue, and another post suggested the
>> >> >following. It worked for me.
>> >> >
>> >> >To fix this issue we had to change the "DSQuery"
value
>> >> >under
>> >>
>>
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\C
>> >> o
>> >> >nnectTo\DSQuery to "DBNETLIB".
>> >> >
>> >> >
>> >> >>-----Original Message-----
>> >> >>Hello All,
>> >> >>
>> >> >>I was attacked by the SQL Slammer virus... I
>> downloaded
>> >> >>the SP3 from the site and tried to install.
>> >> >>
>> >> >>But the installtion stops at "Validating a User"
and
>> >> >>gives me an error saying password incorrect.
>> >> >>
>> >> >>I re-typed my sa password also kept blank but
still it
>> >> >>does not work.
>> >> >>
>> >> >>Can anybody help me... or Does anyone have the
similar
>> >> >>problem...
>> >> >>
>> >> >>Regards
>> >> >>Nitesh
>> >> >>.
>> >> >>
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>>
>
>
>.
>



Relevant Pages

  • Re: SQL SLAMMER
    ... 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. ... >>server connection should use the DBNETLIB library (which ... > is the default SQL ...
    (microsoft.public.sqlserver.security)
  • Re: SQL SLAMMER
    ... >What was the current version of MDAC when you tried to ... >> this the order they are in in the client network ... >>>server connection should use the DBNETLIB library ... >> is the default SQL ...
    (microsoft.public.sqlserver.security)
  • Re: Any help here???
    ... Well, for starters, I believe MDAC is unnecessary for .NET applications - as ... ADO.NET has its own SQL Server provider for data access. ... > trust me - all that's been done here was to install SP2 or upgrade of XP ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: update query ODBC--call failed
    ... I have done a search for the latest version of MDAC, which appears to be 2.8 back from 2003. ... Ultimately I want to post this small application on my server, as a runtime to do some import and updates on some tables on the local server SQL database. ... I am a little unclear about why the "ODBC Driver Manager" is reporting the error rather than the "ODbc Driver For SQL Server". ...
    (microsoft.public.access.queries)
  • Re: different mdac, different sql server behaviour
    ... MDAC Component Checker ... did you set up the link to SQL Server in the first place? ... > In my development environment I am running Access 97 on Windows 98. ...
    (microsoft.public.sqlserver.server)

Quantcast