Showing posts with label sp3a. Show all posts
Showing posts with label sp3a. Show all posts

Thursday, March 22, 2012

April Security Patches and SQL Server

We are running SQL Server 2000/sp3a on a relatively new server sized to meet
our needs for the foreseeable future. The OS is Win2k/sp4. It has been
running very well since installed; the last reboot was over a month ago and
that was scheduled for security updates.
On Monday evening, we installed the April security patches:
Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
could permit code execution
Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook Express
Microsoft KB831167: Wininet retries POST requests with a blank header.
...via SUS. The server has been averaging three unscheduled reboots per day
since. If anyone has any ideas, I would be most grateful. We have had little
luck analyzing the dump file. My guess is that it has something to do with
the RPC/DCOM patch, since it is serving data for several third party web and
windows client applications.
Thanks,
John
I don't know how to solve your issue, but I would recommend you call
Microsoft Product Support Services (MS PSS).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> We are running SQL Server 2000/sp3a on a relatively new server sized to
meet
> our needs for the foreseeable future. The OS is Win2k/sp4. It has been
> running very well since installed; the last reboot was over a month ago
and
> that was scheduled for security updates.
> On Monday evening, we installed the April security patches:
> Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
> could permit code execution
> Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
> Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
Express
> Microsoft KB831167: Wininet retries POST requests with a blank header.
> ...via SUS. The server has been averaging three unscheduled reboots per
day
> since. If anyone has any ideas, I would be most grateful. We have had
little
> luck analyzing the dump file. My guess is that it has something to do with
> the RPC/DCOM patch, since it is serving data for several third party web
and
> windows client applications.
> Thanks,
> John
>
|||Mark,
Thanks, for the response. I guess it is time to use up one of our MSDN
support calls. This set of patches has significantly reduced the
availability of two servers that had been running with no problems for
months, and of course, since it includes the RPC/DCOM patch, we cannot
remove the patch since this is an exploit that requires no I/O (inadequate
operator) action.
Curious though that neither my original post or your response displayed in
the newsgroup. I only found your response, by searching the forum for the
subject line of my post. Is Microsoft taking editorial license?
Cheers,
John
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> I don't know how to solve your issue, but I would recommend you call
> Microsoft Product Support Services (MS PSS).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
>
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> meet
> and
Engine[vbcol=seagreen]
> Express
> day
> little
with
> and
>
|||Nope, Microsoft is not taking editorial license on this or any other post
that isn't spam, pornography, personal attacks, or something else nasty like
that.
I can see both your original post (Message-ID:
<esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl>) and Mark's followup (Message-ID:
<uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl>) on msnews.microsoft.com using
Outlook Express. I can also see them using our web newsreader at:
http://www.microsoft.com/sql/communi...glist=&ptlist=
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Mark,
> Thanks, for the response. I guess it is time to use up one of our MSDN
> support calls. This set of patches has significantly reduced the
> availability of two servers that had been running with no problems for
> months, and of course, since it includes the RPC/DCOM patch, we cannot
> remove the patch since this is an exploit that requires no I/O (inadequate
> operator) action.
> Curious though that neither my original post or your response displayed in
> the newsgroup. I only found your response, by searching the forum for the
> subject line of my post. Is Microsoft taking editorial license?
> Cheers,
> John
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
to[vbcol=seagreen]
been[vbcol=seagreen]
ago[vbcol=seagreen]
> Engine
per[vbcol=seagreen]
> with
web
>
|||Stephen,
Well, yesterday, both were not listed in my default reader, Outlook Express,
and searching only brought up the reply. Today, the search found Mark's
response, my followup and your followup. Looking down the list, I do not
find my original post of 4/22. Just reporting what I see.
Are there any known problems with this patch?
We immediately saw unscheduled reboots of our SQL Server (2000sp/3a running
on Win2k Server sp4). Typically these are network related, and I have not
seen anything untoward happening when running perfmon and sql profiler
against the server, but they began almost immediately after the sus push of
these patches to the server.
We also experienced problems with a third party web application trying to
access the database server. This application is running on a Windows
2000/sp4 server running IIS5.0 with SSL. The application reported numerous
connection failures to the database. SQL Profiler did show any failed login
attempts, so I have to assume that it was the applications data tier that
was having the problem; but again, the problem did not exist until the
patches were applied.
Removing the patches resolved the issue, but clearly this is not a situation
I want to maintain for any length of time.
Regards,
John
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
> Nope, Microsoft is not taking editorial license on this or any other post
> that isn't spam, pornography, personal attacks, or something else nasty
like
> that.
> I can see both your original post (Message-ID:
> <esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl>) and Mark's followup (Message-ID:
> <uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl>) on msnews.microsoft.com using
> Outlook Express. I can also see them using our web newsreader at:
>
http://www.microsoft.com/sql/communi...server&cat=&la
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
(inadequate[vbcol=seagreen]
in[vbcol=seagreen]
the[vbcol=seagreen]
> to
> been
> ago
RPC/DCOM[vbcol=seagreen]
header.[vbcol=seagreen]
> per
had[vbcol=seagreen]
do
> web
>
|||I'll just repeat what Mark said and suggest that you open up a case with PSS
to track down your problems with the patch. I'm sorry, but while I work in
PSS, I don't work on the support team and can't help you.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:ukKS0RGLEHA.808@.tk2msftngp13.phx.gbl...
> Stephen,
> Well, yesterday, both were not listed in my default reader, Outlook
Express,
> and searching only brought up the reply. Today, the search found Mark's
> response, my followup and your followup. Looking down the list, I do not
> find my original post of 4/22. Just reporting what I see.
> Are there any known problems with this patch?
> We immediately saw unscheduled reboots of our SQL Server (2000sp/3a
running
> on Win2k Server sp4). Typically these are network related, and I have not
> seen anything untoward happening when running perfmon and sql profiler
> against the server, but they began almost immediately after the sus push
of
> these patches to the server.
> We also experienced problems with a third party web application trying to
> access the database server. This application is running on a Windows
> 2000/sp4 server running IIS5.0 with SSL. The application reported numerous
> connection failures to the database. SQL Profiler did show any failed
login
> attempts, so I have to assume that it was the applications data tier that
> was having the problem; but again, the problem did not exist until the
> patches were applied.
> Removing the patches resolved the issue, but clearly this is not a
situation[vbcol=seagreen]
> I want to maintain for any length of time.
> Regards,
> John
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
post[vbcol=seagreen]
> like
(Message-ID:
>
http://www.microsoft.com/sql/communi...server&cat=&la
>
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=[vbcol=seagreen]
> rights.
> (inadequate
displayed[vbcol=seagreen]
> in
> the
sized[vbcol=seagreen]
month[vbcol=seagreen]
Database[vbcol=seagreen]
> RPC/DCOM
Outlook[vbcol=seagreen]
> header.
reboots[vbcol=seagreen]
> had
> do
party
>
|||We applied MS04-011 835732 and had 2 lockups/blue screens in 24 hours.
Last night we applied MS03-031 Cumulative Patch for Microsoft SQL Server (815495);
So far, it has been up 15 hours without re-booting.
Tim S

April Security Patches and SQL Server

We are running SQL Server 2000/sp3a on a relatively new server sized to meet
our needs for the foreseeable future. The OS is Win2k/sp4. It has been
running very well since installed; the last reboot was over a month ago and
that was scheduled for security updates.
On Monday evening, we installed the April security patches:
Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
could permit code execution
Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook Express
Microsoft KB831167: Wininet retries POST requests with a blank header.
...via SUS. The server has been averaging three unscheduled reboots per day
since. If anyone has any ideas, I would be most grateful. We have had little
luck analyzing the dump file. My guess is that it has something to do with
the RPC/DCOM patch, since it is serving data for several third party web and
windows client applications.
Thanks,
JohnI don't know how to solve your issue, but I would recommend you call
Microsoft Product Support Services (MS PSS).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> We are running SQL Server 2000/sp3a on a relatively new server sized to
meet
> our needs for the foreseeable future. The OS is Win2k/sp4. It has been
> running very well since installed; the last reboot was over a month ago
and
> that was scheduled for security updates.
> On Monday evening, we installed the April security patches:
> Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
> could permit code execution
> Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
> Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
Express
> Microsoft KB831167: Wininet retries POST requests with a blank header.
> ...via SUS. The server has been averaging three unscheduled reboots per
day
> since. If anyone has any ideas, I would be most grateful. We have had
little
> luck analyzing the dump file. My guess is that it has something to do with
> the RPC/DCOM patch, since it is serving data for several third party web
and
> windows client applications.
> Thanks,
> John
>|||Mark,
Thanks, for the response. I guess it is time to use up one of our MSDN
support calls. This set of patches has significantly reduced the
availability of two servers that had been running with no problems for
months, and of course, since it includes the RPC/DCOM patch, we cannot
remove the patch since this is an exploit that requires no I/O (inadequate
operator) action.
Curious though that neither my original post or your response displayed in
the newsgroup. I only found your response, by searching the forum for the
subject line of my post. Is Microsoft taking editorial license?
Cheers,
John
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
> I don't know how to solve your issue, but I would recommend you call
> Microsoft Product Support Services (MS PSS).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
>
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> meet
> and
Engine[vbcol=seagreen]
> Express
> day
> little
with[vbcol=seagreen]
> and
>|||Nope, Microsoft is not taking editorial license on this or any other post
that isn't spam, pornography, personal attacks, or something else nasty like
that.
I can see both your original post (Message-ID:
<esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl> ) and Mark's followup (Message-ID:
<uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl> ) on msnews.microsoft.com using
Outlook Express. I can also see them using our web newsreader at:
http://www.microsoft.com/sql/commun...dglist=&ptlist=
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
> Mark,
> Thanks, for the response. I guess it is time to use up one of our MSDN
> support calls. This set of patches has significantly reduced the
> availability of two servers that had been running with no problems for
> months, and of course, since it includes the RPC/DCOM patch, we cannot
> remove the patch since this is an exploit that requires no I/O (inadequate
> operator) action.
> Curious though that neither my original post or your response displayed in
> the newsgroup. I only found your response, by searching the forum for the
> subject line of my post. Is Microsoft taking editorial license?
> Cheers,
> John
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
to[vbcol=seagreen]
been[vbcol=seagreen]
ago[vbcol=seagreen]
> Engine
per[vbcol=seagreen]
> with
web[vbcol=seagreen]
>|||Stephen,
Well, yesterday, both were not listed in my default reader, Outlook Express,
and searching only brought up the reply. Today, the search found Mark's
response, my followup and your followup. Looking down the list, I do not
find my original post of 4/22. Just reporting what I see.
Are there any known problems with this patch?
We immediately saw unscheduled reboots of our SQL Server (2000sp/3a running
on Win2k Server sp4). Typically these are network related, and I have not
seen anything untoward happening when running perfmon and sql profiler
against the server, but they began almost immediately after the sus push of
these patches to the server.
We also experienced problems with a third party web application trying to
access the database server. This application is running on a Windows
2000/sp4 server running IIS5.0 with SSL. The application reported numerous
connection failures to the database. SQL Profiler did show any failed login
attempts, so I have to assume that it was the applications data tier that
was having the problem; but again, the problem did not exist until the
patches were applied.
Removing the patches resolved the issue, but clearly this is not a situation
I want to maintain for any length of time.
Regards,
John
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
> Nope, Microsoft is not taking editorial license on this or any other post
> that isn't spam, pornography, personal attacks, or something else nasty
like
> that.
> I can see both your original post (Message-ID:
> <esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl> ) and Mark's followup (Message-ID:
> <uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl> ) on msnews.microsoft.com using
> Outlook Express. I can also see them using our web newsreader at:
>
http://www.microsoft.com/sql/commun...server&cat=&la
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
(inadequate[vbcol=seagreen]
in[vbcol=seagreen]
the[vbcol=seagreen]
> to
> been
> ago
RPC/DCOM[vbcol=seagreen]
header.[vbcol=seagreen]
> per
had[vbcol=seagreen]
do[vbcol=seagreen]
> web
>|||I'll just repeat what Mark said and suggest that you open up a case with PSS
to track down your problems with the patch. I'm sorry, but while I work in
PSS, I don't work on the support team and can't help you.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:ukKS0RGLEHA.808@.tk2msftngp13.phx.gbl...
> Stephen,
> Well, yesterday, both were not listed in my default reader, Outlook
Express,
> and searching only brought up the reply. Today, the search found Mark's
> response, my followup and your followup. Looking down the list, I do not
> find my original post of 4/22. Just reporting what I see.
> Are there any known problems with this patch?
> We immediately saw unscheduled reboots of our SQL Server (2000sp/3a
running
> on Win2k Server sp4). Typically these are network related, and I have not
> seen anything untoward happening when running perfmon and sql profiler
> against the server, but they began almost immediately after the sus push
of
> these patches to the server.
> We also experienced problems with a third party web application trying to
> access the database server. This application is running on a Windows
> 2000/sp4 server running IIS5.0 with SSL. The application reported numerous
> connection failures to the database. SQL Profiler did show any failed
login
> attempts, so I have to assume that it was the applications data tier that
> was having the problem; but again, the problem did not exist until the
> patches were applied.
> Removing the patches resolved the issue, but clearly this is not a
situation
> I want to maintain for any length of time.
> Regards,
> John
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
post[vbcol=seagreen]
> like
(Message-ID:[vbcol=seagreen]
>
http://www.microsoft.com/sql/commun...server&cat=&la
>
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=
> rights.
> (inadequate
displayed[vbcol=seagreen]
> in
> the
sized[vbcol=seagreen]
month[vbcol=seagreen]
Database[vbcol=seagreen]
> RPC/DCOM
Outlook[vbcol=seagreen]
> header.
reboots[vbcol=seagreen]
> had
> do
party[vbcol=seagreen]
>|||We applied MS04-011 835732 and had 2 lockups/blue screens in 24 hours.
Last night we applied MS03-031 Cumulative Patch for Microsoft SQL Server (81
5495);
So far, it has been up 15 hours without re-booting.
Tim S

April Security Patches and SQL Server

We are running SQL Server 2000/sp3a on a relatively new server sized to meet
our needs for the foreseeable future. The OS is Win2k/sp4. It has been
running very well since installed; the last reboot was over a month ago and
that was scheduled for security updates.
On Monday evening, we installed the April security patches:
Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
could permit code execution
Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook Express
Microsoft KB831167: Wininet retries POST requests with a blank header.
...via SUS. The server has been averaging three unscheduled reboots per day
since. If anyone has any ideas, I would be most grateful. We have had little
luck analyzing the dump file. My guess is that it has something to do with
the RPC/DCOM patch, since it is serving data for several third party web and
windows client applications.
Thanks,
JohnI don't know how to solve your issue, but I would recommend you call
Microsoft Product Support Services (MS PSS).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> We are running SQL Server 2000/sp3a on a relatively new server sized to
meet
> our needs for the foreseeable future. The OS is Win2k/sp4. It has been
> running very well since installed; the last reboot was over a month ago
and
> that was scheduled for security updates.
> On Monday evening, we installed the April security patches:
> Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database Engine
> could permit code execution
> Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
> Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
Express
> Microsoft KB831167: Wininet retries POST requests with a blank header.
> ...via SUS. The server has been averaging three unscheduled reboots per
day
> since. If anyone has any ideas, I would be most grateful. We have had
little
> luck analyzing the dump file. My guess is that it has something to do with
> the RPC/DCOM patch, since it is serving data for several third party web
and
> windows client applications.
> Thanks,
> John
>|||Mark,
Thanks, for the response. I guess it is time to use up one of our MSDN
support calls. This set of patches has significantly reduced the
availability of two servers that had been running with no problems for
months, and of course, since it includes the RPC/DCOM patch, we cannot
remove the patch since this is an exploit that requires no I/O (inadequate
operator) action.
Curious though that neither my original post or your response displayed in
the newsgroup. I only found your response, by searching the forum for the
subject line of my post. Is Microsoft taking editorial license?
Cheers,
John
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
> I don't know how to solve your issue, but I would recommend you call
> Microsoft Product Support Services (MS PSS).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
>
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> > We are running SQL Server 2000/sp3a on a relatively new server sized to
> meet
> > our needs for the foreseeable future. The OS is Win2k/sp4. It has been
> > running very well since installed; the last reboot was over a month ago
> and
> > that was scheduled for security updates.
> >
> > On Monday evening, we installed the April security patches:
> >
> > Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database
Engine
> > could permit code execution
> > Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
> > Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> > Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
> Express
> > Microsoft KB831167: Wininet retries POST requests with a blank header.
> >
> > ...via SUS. The server has been averaging three unscheduled reboots per
> day
> > since. If anyone has any ideas, I would be most grateful. We have had
> little
> > luck analyzing the dump file. My guess is that it has something to do
with
> > the RPC/DCOM patch, since it is serving data for several third party web
> and
> > windows client applications.
> >
> > Thanks,
> > John
> >
> >
>|||Nope, Microsoft is not taking editorial license on this or any other post
that isn't spam, pornography, personal attacks, or something else nasty like
that.
I can see both your original post (Message-ID:
<esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl>) and Mark's followup (Message-ID:
<uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl>) on msnews.microsoft.com using
Outlook Express. I can also see them using our web newsreader at:
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?query=April+security+patches&dg=microsoft.public.sqlserver.server&cat=&lang=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
> Mark,
> Thanks, for the response. I guess it is time to use up one of our MSDN
> support calls. This set of patches has significantly reduced the
> availability of two servers that had been running with no problems for
> months, and of course, since it includes the RPC/DCOM patch, we cannot
> remove the patch since this is an exploit that requires no I/O (inadequate
> operator) action.
> Curious though that neither my original post or your response displayed in
> the newsgroup. I only found your response, by searching the forum for the
> subject line of my post. Is Microsoft taking editorial license?
> Cheers,
> John
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
> > I don't know how to solve your issue, but I would recommend you call
> > Microsoft Product Support Services (MS PSS).
> >
> > --
> > Mark Allison, SQL Server MVP
> > http://www.markallison.co.uk
> >
> >
> >
> >
> > "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> > news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> > > We are running SQL Server 2000/sp3a on a relatively new server sized
to
> > meet
> > > our needs for the foreseeable future. The OS is Win2k/sp4. It has
been
> > > running very well since installed; the last reboot was over a month
ago
> > and
> > > that was scheduled for security updates.
> > >
> > > On Monday evening, we installed the April security patches:
> > >
> > > Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database
> Engine
> > > could permit code execution
> > > Microsoft KB828741 MS04-012: Cumulative Update for Microsoft RPC/DCOM
> > > Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> > > Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
> > Express
> > > Microsoft KB831167: Wininet retries POST requests with a blank header.
> > >
> > > ...via SUS. The server has been averaging three unscheduled reboots
per
> > day
> > > since. If anyone has any ideas, I would be most grateful. We have had
> > little
> > > luck analyzing the dump file. My guess is that it has something to do
> with
> > > the RPC/DCOM patch, since it is serving data for several third party
web
> > and
> > > windows client applications.
> > >
> > > Thanks,
> > > John
> > >
> > >
> >
> >
>|||Stephen,
Well, yesterday, both were not listed in my default reader, Outlook Express,
and searching only brought up the reply. Today, the search found Mark's
response, my followup and your followup. Looking down the list, I do not
find my original post of 4/22. Just reporting what I see.
Are there any known problems with this patch?
We immediately saw unscheduled reboots of our SQL Server (2000sp/3a running
on Win2k Server sp4). Typically these are network related, and I have not
seen anything untoward happening when running perfmon and sql profiler
against the server, but they began almost immediately after the sus push of
these patches to the server.
We also experienced problems with a third party web application trying to
access the database server. This application is running on a Windows
2000/sp4 server running IIS5.0 with SSL. The application reported numerous
connection failures to the database. SQL Profiler did show any failed login
attempts, so I have to assume that it was the applications data tier that
was having the problem; but again, the problem did not exist until the
patches were applied.
Removing the patches resolved the issue, but clearly this is not a situation
I want to maintain for any length of time.
Regards,
John
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
> Nope, Microsoft is not taking editorial license on this or any other post
> that isn't spam, pornography, personal attacks, or something else nasty
like
> that.
> I can see both your original post (Message-ID:
> <esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl>) and Mark's followup (Message-ID:
> <uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl>) on msnews.microsoft.com using
> Outlook Express. I can also see them using our web newsreader at:
>
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?query=April+security+patches&dg=microsoft.public.sqlserver.server&cat=&la
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
> > Mark,
> >
> > Thanks, for the response. I guess it is time to use up one of our MSDN
> > support calls. This set of patches has significantly reduced the
> > availability of two servers that had been running with no problems for
> > months, and of course, since it includes the RPC/DCOM patch, we cannot
> > remove the patch since this is an exploit that requires no I/O
(inadequate
> > operator) action.
> >
> > Curious though that neither my original post or your response displayed
in
> > the newsgroup. I only found your response, by searching the forum for
the
> > subject line of my post. Is Microsoft taking editorial license?
> >
> > Cheers,
> > John
> >
> > "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> > news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
> > > I don't know how to solve your issue, but I would recommend you call
> > > Microsoft Product Support Services (MS PSS).
> > >
> > > --
> > > Mark Allison, SQL Server MVP
> > > http://www.markallison.co.uk
> > >
> > >
> > >
> > >
> > > "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> > > news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> > > > We are running SQL Server 2000/sp3a on a relatively new server sized
> to
> > > meet
> > > > our needs for the foreseeable future. The OS is Win2k/sp4. It has
> been
> > > > running very well since installed; the last reboot was over a month
> ago
> > > and
> > > > that was scheduled for security updates.
> > > >
> > > > On Monday evening, we installed the April security patches:
> > > >
> > > > Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet Database
> > Engine
> > > > could permit code execution
> > > > Microsoft KB828741 MS04-012: Cumulative Update for Microsoft
RPC/DCOM
> > > > Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> > > > Microsoft KB837009 MS04-013: Cumulative Security Update for Outlook
> > > Express
> > > > Microsoft KB831167: Wininet retries POST requests with a blank
header.
> > > >
> > > > ...via SUS. The server has been averaging three unscheduled reboots
> per
> > > day
> > > > since. If anyone has any ideas, I would be most grateful. We have
had
> > > little
> > > > luck analyzing the dump file. My guess is that it has something to
do
> > with
> > > > the RPC/DCOM patch, since it is serving data for several third party
> web
> > > and
> > > > windows client applications.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > >
> > >
> >
> >
>|||I'll just repeat what Mark said and suggest that you open up a case with PSS
to track down your problems with the patch. I'm sorry, but while I work in
PSS, I don't work on the support team and can't help you.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
news:ukKS0RGLEHA.808@.tk2msftngp13.phx.gbl...
> Stephen,
> Well, yesterday, both were not listed in my default reader, Outlook
Express,
> and searching only brought up the reply. Today, the search found Mark's
> response, my followup and your followup. Looking down the list, I do not
> find my original post of 4/22. Just reporting what I see.
> Are there any known problems with this patch?
> We immediately saw unscheduled reboots of our SQL Server (2000sp/3a
running
> on Win2k Server sp4). Typically these are network related, and I have not
> seen anything untoward happening when running perfmon and sql profiler
> against the server, but they began almost immediately after the sus push
of
> these patches to the server.
> We also experienced problems with a third party web application trying to
> access the database server. This application is running on a Windows
> 2000/sp4 server running IIS5.0 with SSL. The application reported numerous
> connection failures to the database. SQL Profiler did show any failed
login
> attempts, so I have to assume that it was the applications data tier that
> was having the problem; but again, the problem did not exist until the
> patches were applied.
> Removing the patches resolved the issue, but clearly this is not a
situation
> I want to maintain for any length of time.
> Regards,
> John
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:%23aUwOT7KEHA.3052@.TK2MSFTNGP12.phx.gbl...
> > Nope, Microsoft is not taking editorial license on this or any other
post
> > that isn't spam, pornography, personal attacks, or something else nasty
> like
> > that.
> >
> > I can see both your original post (Message-ID:
> > <esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl>) and Mark's followup
(Message-ID:
> > <uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl>) on msnews.microsoft.com using
> > Outlook Express. I can also see them using our web newsreader at:
> >
> >
>
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?query=April+security+patches&dg=microsoft.public.sqlserver.server&cat=&la
>
ng=en&cr=US&pt=&catlist=6C839803-6334-48D8-A2C3-72A1BEF0053D&dglist=&ptlist=> >
> > --
> > Sincerely,
> > Stephen Dybing
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> > news:Ow6KCQ5KEHA.240@.TK2MSFTNGP10.phx.gbl...
> > > Mark,
> > >
> > > Thanks, for the response. I guess it is time to use up one of our MSDN
> > > support calls. This set of patches has significantly reduced the
> > > availability of two servers that had been running with no problems for
> > > months, and of course, since it includes the RPC/DCOM patch, we cannot
> > > remove the patch since this is an exploit that requires no I/O
> (inadequate
> > > operator) action.
> > >
> > > Curious though that neither my original post or your response
displayed
> in
> > > the newsgroup. I only found your response, by searching the forum for
> the
> > > subject line of my post. Is Microsoft taking editorial license?
> > >
> > > Cheers,
> > > John
> > >
> > > "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> > > news:uigrjjQKEHA.3944@.tk2msftngp13.phx.gbl...
> > > > I don't know how to solve your issue, but I would recommend you call
> > > > Microsoft Product Support Services (MS PSS).
> > > >
> > > > --
> > > > Mark Allison, SQL Server MVP
> > > > http://www.markallison.co.uk
> > > >
> > > >
> > > >
> > > >
> > > > "John" <jkraeck@.NOprincetonSPAM.edu> wrote in message
> > > > news:esSncLKKEHA.2884@.TK2MSFTNGP12.phx.gbl...
> > > > > We are running SQL Server 2000/sp3a on a relatively new server
sized
> > to
> > > > meet
> > > > > our needs for the foreseeable future. The OS is Win2k/sp4. It has
> > been
> > > > > running very well since installed; the last reboot was over a
month
> > ago
> > > > and
> > > > > that was scheduled for security updates.
> > > > >
> > > > > On Monday evening, we installed the April security patches:
> > > > >
> > > > > Microsoft KB837001 MS04-014:Vulnerability in Microsoft Jet
Database
> > > Engine
> > > > > could permit code execution
> > > > > Microsoft KB828741 MS04-012: Cumulative Update for Microsoft
> RPC/DCOM
> > > > > Microsoft KB835732 MS04-011: Security Update for Microsoft Windows
> > > > > Microsoft KB837009 MS04-013: Cumulative Security Update for
Outlook
> > > > Express
> > > > > Microsoft KB831167: Wininet retries POST requests with a blank
> header.
> > > > >
> > > > > ...via SUS. The server has been averaging three unscheduled
reboots
> > per
> > > > day
> > > > > since. If anyone has any ideas, I would be most grateful. We have
> had
> > > > little
> > > > > luck analyzing the dump file. My guess is that it has something to
> do
> > > with
> > > > > the RPC/DCOM patch, since it is serving data for several third
party
> > web
> > > > and
> > > > > windows client applications.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||We applied MS04-011 835732 and had 2 lockups/blue screens in 24 hours.
Last night we applied MS03-031 Cumulative Patch for Microsoft SQL Server (815495);
So far, it has been up 15 hours without re-booting.
Tim Ssql

Tuesday, March 20, 2012

Applying SP4 on Replicated databases

Hi,
We have transactional replication with 30 subscribers. We are planning to
upgrade to sp4 from sp3a. Publisher and distributor are in the same server.
So is there any order(sequence) like first we have to upgrade publisher and
then subscriber...
Is there any known issues/impact on publisher or subscriber.
Thanks in advance for your help.
Thanks
Prabhu
The rule is
Local Distributor - upgrade the publisher/distributor first then the
subscribers
Remote Distributor - upgrade the distributor, then the publisher, and
finally the subscriber(s).
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
> Hi,
> We have transactional replication with 30 subscribers. We are planning to
> upgrade to sp4 from sp3a. Publisher and distributor are in the same
> server.
> So is there any order(sequence) like first we have to upgrade publisher
> and
> then subscriber...
> Is there any known issues/impact on publisher or subscriber.
> Thanks in advance for your help.
> Thanks
> Prabhu
>
|||Thanks cotter,
So we don't need to worry about the subscriber type, whether its read-only
or updatable subscriber. Am i right ? or is there any difference for these
types.
Thanks
Prabhu
"Hilary Cotter" wrote:

> The rule is
> Local Distributor - upgrade the publisher/distributor first then the
> subscribers
> Remote Distributor - upgrade the distributor, then the publisher, and
> finally the subscriber(s).
> "Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
> news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
>
>
|||Yes you don't have to worry about the subscribers. Just do them last.
I always shut down the SQL Server agents on the boxes before doing the
upgrades. You will need to notify your users that you are doing upgrades so
you can kick them off.
Hilary
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:EC578700-3B73-4C38-9255-4FA97C79A7B4@.microsoft.com...[vbcol=seagreen]
> Thanks cotter,
> So we don't need to worry about the subscriber type, whether its
> read-only
> or updatable subscriber. Am i right ? or is there any difference for these
> types.
> Thanks
> Prabhu
>
>
> "Hilary Cotter" wrote:

Monday, March 19, 2012

Applying SP3a to SQL 2000 cluster - Problem

I have added two new nodes to the cluster and successfully installed SQL 2000
on both. I am trying to apply SP3a to both and am getting the message
"18:01:30 One or more errors occurred while running remote setup on the
clustered machines.
18:01:35 Setup failed to perform required operations on the cluster nodes."
Active/passive cluster. active node is up and working. But I have only a 1
node cluster at the moment.
Additonal from sqlsp.log:
17:55:49 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=1
Server.1=GSOSVSQLCLS1D
[Server.1]
NumRemoteServices=1
1.app="\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\ x86\setup\setupsql.exe"
1.server=GSOSVSQLCLS1D
1.script=\\GSOSVSQLCLS1A\admin$\GSOSVSQLCLS1D_MSSQ LSERVER.iss
1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
"\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\x86\se tup\setup.ins" -f1 %s -f2
"\\GSOSVSQLCLS1D\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
1.user=GILBARCO\skipper
1.name=SQLSetup1
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
17:55:49 Setup is performing required operations on cluster nodes. This may
take a few minutes...
17:55:49 "C:\DOCUME~1\hall\LOCALS~1\Temp\SqlSetup\Bin\remse tup.exe"
C:\WINNT\remsetup.ini
18:01:30 Process Exit Code: (-12)
18:01:30 Begin Action : GetRemsetupRetCode
18:01:30 Installation return status on GSOSVSQLCLS1D : -12
18:01:30 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 05/26/07 17:55:49 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x84] created for execution.
CThread::Process [0x84]
CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=0
Script file copied to '\\GSOSVSQLCLS1D\ADMIN$\GSOSVSQLCLS1D_MSSQLSERVER. iss'
successfully.
Installing remote service (GSOSVSQLCLS1D)...
CRemoteProcess::RunUntilComplete [0x84] exit code: -12
Remote process exit code was '-12' (GSOSVSQLCLS1D).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
Thread [0x84] exit code: [0xfffffff4]
CThreadPool::RunUntilComplete returned -12
CThreadPool::RunUntilComplete execution level=1, need execution: 0
One or more errors occurred while running the remote/unattended setups.
Disconnecting from remote machine (GSOSVSQLCLS1D)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 05/26/07 18:01:30 ####
18:01:30 End Action : Run setup on cluster nodes
18:01:30 One or more errors occurred while running remote setup on the
clustered machines.
18:01:35 Setup failed to perform required operations on the cluster nodes.
18:01:35 Begin Action : ClusterErrorCleanup
18:01:35 End Action : ClusterErrorCleanup
18:01:35 End Action : ClusterSetupHelper
18:01:35 Begin Action : LogEvent
18:01:35 End Action : LogEvent
18:01:35 Begin Action : CloseEventLog
18:01:35 End Action : CloseEventLog
Pat is there anything in the cluster log, application log or the system log.
Need more information so troubleshoot.
Thanks
John Vandervliet
"Pat Hall" wrote:

> I have added two new nodes to the cluster and successfully installed SQL 2000
> on both. I am trying to apply SP3a to both and am getting the message
> "18:01:30 One or more errors occurred while running remote setup on the
> clustered machines.
> 18:01:35 Setup failed to perform required operations on the cluster nodes."
> Active/passive cluster. active node is up and working. But I have only a 1
> node cluster at the moment.
> Additonal from sqlsp.log:
> 17:55:49 Begin Action : Run setup on cluster nodes
> [args]
> NumRemoteServers=1
> Server.1=GSOSVSQLCLS1D
> [Server.1]
> NumRemoteServices=1
> 1.app="\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\ x86\setup\setupsql.exe"
> 1.server=GSOSVSQLCLS1D
> 1.script=\\GSOSVSQLCLS1A\admin$\GSOSVSQLCLS1D_MSSQ LSERVER.iss
> 1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
> "\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\x86\se tup\setup.ins" -f1 %s -f2
> "\\GSOSVSQLCLS1D\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
> 1.user=GILBARCO\skipper
> 1.name=SQLSetup1
> 1.sqlsetup=Y
> 1.copyexe=cnvsvc1.exe
> 17:55:49 Setup is performing required operations on cluster nodes. This may
> take a few minutes...
> 17:55:49 "C:\DOCUME~1\hall\LOCALS~1\Temp\SqlSetup\Bin\remse tup.exe"
> C:\WINNT\remsetup.ini
> 18:01:30 Process Exit Code: (-12)
> 18:01:30 Begin Action : GetRemsetupRetCode
> 18:01:30 Installation return status on GSOSVSQLCLS1D : -12
> 18:01:30 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 05/26/07 17:55:49 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x84] created for execution.
> CThread::Process [0x84]
> CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=0
> Script file copied to '\\GSOSVSQLCLS1D\ADMIN$\GSOSVSQLCLS1D_MSSQLSERVER. iss'
> successfully.
> Installing remote service (GSOSVSQLCLS1D)...
> CRemoteProcess::RunUntilComplete [0x84] exit code: -12
> Remote process exit code was '-12' (GSOSVSQLCLS1D).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
> Thread [0x84] exit code: [0xfffffff4]
> CThreadPool::RunUntilComplete returned -12
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> One or more errors occurred while running the remote/unattended setups.
> Disconnecting from remote machine (GSOSVSQLCLS1D)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 05/26/07 18:01:30 ####
>
>
>
>
>
>
>
> 18:01:30 End Action : Run setup on cluster nodes
> 18:01:30 One or more errors occurred while running remote setup on the
> clustered machines.
> 18:01:35 Setup failed to perform required operations on the cluster nodes.
> 18:01:35 Begin Action : ClusterErrorCleanup
> 18:01:35 End Action : ClusterErrorCleanup
> 18:01:35 End Action : ClusterSetupHelper
> 18:01:35 Begin Action : LogEvent
> 18:01:35 End Action : LogEvent
> 18:01:35 Begin Action : CloseEventLog
> 18:01:35 End Action : CloseEventLog
>
|||Found the problem, a bug in the SP3a install that will not let youi apply
SP3a to 2 new nodes at the same time. See KB318672.
Got SP3a applied and will be failing over tonight.
"John Vandervliet" wrote:
[vbcol=seagreen]
> Pat is there anything in the cluster log, application log or the system log.
> Need more information so troubleshoot.
> Thanks
> John Vandervliet
> "Pat Hall" wrote:

Applying SP3A to a new node

Hi,
I need to install sp3a in a recently added node, but I added this second
node after I had installed SP3A in the active node, so, when I installed
SP3a in the first and active node, it was not installed in other servers. I
have the following scenario
1st node (active) : Win 2K3, SP1, SQL2K, SP3a
2dn node (pasive) : Win 2K3, SP1, SQL2K.
The 1st node currently owns all the groups.
I read some information in BOL and some support docs, but I'n not sure what
to do.
Thanks in advance.
Patrick.
Hi
The reademe for SP3a tell you how to do it. You run the SP on node 2, with
node 1 owning all the resources.
If you are lucky, the SP will just install updated the binaries on node 2.
In some cases, it requires node 2 to be the node running the resources. In
this case, fail it over to node 2 and run the SP. Then reboot all nodes.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Patrick Mac Kay" <pmackay_at_hotmail.com> wrote in message
news:ubaNSrTZFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I need to install sp3a in a recently added node, but I added this
> second
> node after I had installed SP3A in the active node, so, when I installed
> SP3a in the first and active node, it was not installed in other servers.
> I
> have the following scenario
> 1st node (active) : Win 2K3, SP1, SQL2K, SP3a
> 2dn node (pasive) : Win 2K3, SP1, SQL2K.
> The 1st node currently owns all the groups.
> I read some information in BOL and some support docs, but I'n not sure
> what
> to do.
> Thanks in advance.
> Patrick.
>
|||Mike,
thanks, I read it before I wrote the first post, but it fails because it
cannot find the shared resources (obvious). So, I didn't know how to
continue. Now, I'll try the second option you said.
Just one more question. Is there any risk installing SP3a over node without
it, but the databases in the shared resource (master, etc) having it applied
(because I applied it in the first node)? In that case, if I apply again the
SP3a in the first node, it would be applied over the 2nd node automatically?
Thanks again.
Patrick.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> escribi en el mensaje
news:eX$#GXUZFHA.3780@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi
> The reademe for SP3a tell you how to do it. You run the SP on node 2, with
> node 1 owning all the resources.
> If you are lucky, the SP will just install updated the binaries on node 2.
> In some cases, it requires node 2 to be the node running the resources. In
> this case, fail it over to node 2 and run the SP. Then reboot all nodes.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Patrick Mac Kay" <pmackay_at_hotmail.com> wrote in message
> news:ubaNSrTZFHA.1384@.TK2MSFTNGP09.phx.gbl...
servers.
>
|||Hi
I have never tried it again on the 1st node. I could possibly work. The SP
is clever enough not to mess up the databases as it can tell at what version
a DB is.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Patrick Mac Kay" <pmackay_at_hotmail.com> wrote in message
news:eXtxbiUZFHA.4008@.tk2msftngp13.phx.gbl...
> Mike,
> thanks, I read it before I wrote the first post, but it fails because
> it
> cannot find the shared resources (obvious). So, I didn't know how to
> continue. Now, I'll try the second option you said.
> Just one more question. Is there any risk installing SP3a over node
> without
> it, but the databases in the shared resource (master, etc) having it
> applied
> (because I applied it in the first node)? In that case, if I apply again
> the
> SP3a in the first node, it would be applied over the 2nd node
> automatically?
> Thanks again.
> Patrick.
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> escribi en el mensaje
> news:eX$#GXUZFHA.3780@.tk2msftngp13.phx.gbl...
> servers.
>
|||Ok, Thanks again.
I hope it'll be clever enough.
Patrick.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> escribi en el mensaje
news:uiHdimUZFHA.4088@.TK2MSFTNGP15.phx.gbl...
> Hi
> I have never tried it again on the 1st node. I could possibly work. The SP
> is clever enough not to mess up the databases as it can tell at what
version[vbcol=seagreen]
> a DB is.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Patrick Mac Kay" <pmackay_at_hotmail.com> wrote in message
> news:eXtxbiUZFHA.4008@.tk2msftngp13.phx.gbl...
nodes.[vbcol=seagreen]
sure
>
|||I have run a Service Pack in just this situation. Yes, the installer is
smart enough. YOu will not harm anything by reapplying a service pack to a
clustered node.
Geoff N. Hiten
Microsoft SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiHdimUZFHA.4088@.TK2MSFTNGP15.phx.gbl...
> Hi
> I have never tried it again on the 1st node. I could possibly work. The SP
> is clever enough not to mess up the databases as it can tell at what
> version a DB is.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Patrick Mac Kay" <pmackay_at_hotmail.com> wrote in message
> news:eXtxbiUZFHA.4008@.tk2msftngp13.phx.gbl...
>
|||Thanks to everyone. It worked great.
Patrick.
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> escribi en el mensaje
news:O61VPzdZFHA.4088@.TK2MSFTNGP15.phx.gbl...
> I have run a Service Pack in just this situation. Yes, the installer is
> smart enough. YOu will not harm anything by reapplying a service pack to
a[vbcol=seagreen]
> clustered node.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiHdimUZFHA.4088@.TK2MSFTNGP15.phx.gbl...
SP[vbcol=seagreen]
because[vbcol=seagreen]
again[vbcol=seagreen]
node[vbcol=seagreen]
resources.[vbcol=seagreen]
nodes.[vbcol=seagreen]
sure
>

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Sunday, March 11, 2012

Apply Service Pack Question

I have a couple of servers that are running SQL Server 2000 with no service
packs applied. I would like to apply SP3a to both of them. Are there any
possible/known problems that I should be aware of before attempting this.
This will be my first time doing this type of thing...
Thanks
EricMake sure you really read the documentation and readme etc that comes with the service pack! :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:uB95tpeZDHA.2236@.TK2MSFTNGP10.phx.gbl...
> I have a couple of servers that are running SQL Server 2000 with no service
> packs applied. I would like to apply SP3a to both of them. Are there any
> possible/known problems that I should be aware of before attempting this.
> This will be my first time doing this type of thing...
> Thanks
> Eric
>

apply server pack 3a to new instances?

How do I apply sp3a to a new instance of sql2000? The original is already upgraded. I added three new instances.Each instance will require the service pack.
When you start the service pack setup program you can select the instance
name from a drop down list.
HTH
Ryan Waight, MCDBA, MCSE
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:69DE0125-4A5C-4015-BE8A-BD15FFA75B1B@.microsoft.com...
> How do I apply sp3a to a new instance of sql2000? The original is already
upgraded. I added three new instances.