An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Friday, March 30, 2012
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:OGpfQVFYHHA.4368@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:OGpfQVFYHHA.4368@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Microsoft SQL Server 2005 SP2 Issue
An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>
Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installatio
Installing SQL 2005 install in progress sertup error :
"Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
corrupt and cannot be used"I get the same error. Anyone have any idea what causes this?
Thanks.
Marcus
"Diamondas" wrote:
> Installing SQL 2005 install in progress sertup error :
> "Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
> corrupt and cannot be used"
>
>sql
"Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
corrupt and cannot be used"I get the same error. Anyone have any idea what causes this?
Thanks.
Marcus
"Diamondas" wrote:
> Installing SQL 2005 install in progress sertup error :
> "Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
> corrupt and cannot be used"
>
>sql
Microsoft SQL Server 2005 Setup Problem
i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.
TITLE: Microsoft SQL Server 2005 Setup
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190
BUTTONS:
OK
Here are several references. Check the ones you haven't previously explored.
Remove -Error message when you install SQL Server 2005: "Beta components detected"
http://support.microsoft.com/?kbid=919394
Remove -How do I remove previous versions of SQL Server 2005 / Whidbey?
http://www.aspfaq.com/sql2005/show.asp?id=15
Remove -How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/?kbid=909967
Remove -How to Uninstall MSDE
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991
Remove -How to Uninstall SQL Server 2005 Beta
http://go.microsoft.com/?linkid=1396133
Remove -How to uninstall SQL Server Management Studio
http://support.microsoft.com/default.aspx?scid=kb;EN-US;909953
Remove -How to use the Add or Remove Programs item in Control Panel to add
or remove components for stand-alone installations and clustered
installations of SQL Server 2005 (KB: 922670)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922670
Remove -How to: Uninstall SQL Server Express
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
Remove -The error is: Fatal error during installation"
http://support.microsoft.com/?kbid=919945
Remove -Uninstall Applications NOT in Install/Remove Programs List
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx
Try the Windows Installer clean up tool first.
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe
THE INSTALLER WORKED FOR ME - -THANKS
Microsoft SQL Server 2005 Setup
i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.
TITLE: Microsoft SQL Server 2005 Setup
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190
BUTTONS:
OK
Here are several references. Check the ones you haven't previously explored.
Remove -Error message when you install SQL Server 2005: "Beta components detected"
http://support.microsoft.com/?kbid=919394
Remove -How do I remove previous versions of SQL Server 2005 / Whidbey?
http://www.aspfaq.com/sql2005/show.asp?id=15
Remove -How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/?kbid=909967
Remove -How to Uninstall MSDE
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991
Remove -How to Uninstall SQL Server 2005 Beta
http://go.microsoft.com/?linkid=1396133
Remove -How to uninstall SQL Server Management Studio
http://support.microsoft.com/default.aspx?scid=kb;EN-US;909953
Remove -How to use the Add or Remove Programs item in Control Panel to add
or remove components for stand-alone installations and clustered
installations of SQL Server 2005 (KB: 922670)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922670
Remove -How to: Uninstall SQL Server Express
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
Remove -The error is: Fatal error during installation"
http://support.microsoft.com/?kbid=919945
Remove -Uninstall Applications NOT in Install/Remove Programs List
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx
Try the Windows Installer clean up tool first.
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe
THE INSTALLER WORKED FOR ME - -THANKS
Subscribe to:
Posts (Atom)