Re: SP3 and SQL Server Tools Installation

From: Giacomo (anonymous_at_msnewsgroups.com)
Date: 07/16/04 

Date: Thu, 15 Jul 2004 20:30:55 -0400

Kevin,
This doesn't help. I have run the patch but the instance does not show up
in the patch's combo box, only the default instance. On my home computer,
the instance does show. I presume it is the way security has been
configured on my local machine. I expect that if the patch can't find the
instance, probably no one else will either. I truly doubt anyone will get
past the firewall anyhow.
By the way, thank you for responding and for doing so quickly. It is a
quality that I very much appreciate.
Finally, I was unclear in my initial post. If you don't mind, may I restate
my question?
We have, under the direction of the Macola ERP (SQL Server / Exact),
installed the tools on all the machines that must run Macola locally. Our
network guy did not install SP3 (I refer NOT to msde [sp3a] for desktop, but
the sp3 for the SQL Server) on any of these machines. I am wondering if
there are any items in the tools which require SP3? Most if not all of
these machine never see sp3a as there is no need to put the Desktop Engine
on those machines. I am certain this won't show on my own machine since I
patch constantly (an obsession of mine). If I had administrative access to
those machines, I could run the MBSA remotely against the machine, but I
don't have those priveleges. So, the question is strictly rhetorical.
Jamie
"Kevin McDonnell [MSFT]" <kevmc@online.microsoft.com> wrote in message
news:AqHwPUraEHA.228@cpmsftngxa06.phx.gbl...
> You have a Named Instance Called "Valco" that is unpatched. This is not
> the SQL tools. This is a complete installation
> of SQL.
>
> File version is less than expected.
> [C:\Program Files\Microsoft SQL
> Server\MSSQL$VALCO\binn\sqlservr.exe, 2000.80.194.0
>
> This named Instance need to be updated to SQL sp3a and then patched with
> MS03-031
>
> 821277 MS03-031:Security Patch for SQL Server 2000 Service Pack 3
> http://support.microsoft.com/?id=821277
>
>
> Thanks,
>
> Kevin McDonnell
> Microsoft Corporation
>
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
>

Relevant Pages

  • Re: File Protection
    ... As far as I've been able to determine, I have been installing SP3a. ... "Distinguishing Between SP3 and SP3a ... "Named instance: C:\Program Files\Microsoft SQL ...
    (microsoft.public.sqlserver.setup)
  • SQL SP3 problems fixed with SP3a
    ... I was running SBS2K with SQL SP3 ... there's no need to apply SP3a. ... SQL would use up all my available memory. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Version # and Service Patch
    ... SERVERPROPERTYa product level of SP3 ... Distinguishing Between SP3 and SP3a ... Named instance: C:\Program Files\Microsoft SQL ...
    (microsoft.public.sqlserver.server)
  • Re: Do I have sp3a o sp3 installed on my SQL 2000?
    ... installation of the default instance; that's a mistake in the SP3a readme ... SQL Server MVP ... > To determine whether you have SP3 or SP3a installed, ...
    (microsoft.public.sqlserver.setup)
  • RE: Increasing ICMP Echo Requests
    ... SQL servers fall under the purview of security-related staff who subscribe ... Alright, if the patch works, there are no foulups, there is nothing else to ... > Well no I don't expect Joe shmoe to know this, ... > technical IT security event. ...
    (Incidents)