Apply monthly Windows 2008 r2 updates within SQL Server 2008 cluster

Hello is applying Windows updates within 2 node SQL Server 2008 cluster (active-passive) as simple as download/install the windows update on the passive node, then failover, then apply on other node, and then fail back over ?...or are there other needed/recommended
steps ? Thanks in advance.

Thanks for your reply Shanky_621 much appreciated.
In your link provided http://support.microsoft.com/kb/174799 it looks like the steps order is slightly different from this link of
http://technet.microsoft.com/en-us/library/cc731291.aspx which mentions...
"...where the recommended sequence is to move all services and applications off of the node, pause the node, then apply software updates to the node."
...does it matter which is done first ('Pause' or 'move Services/Application') or can I simply go to the Passive node (say 'B' where there are no Services or Applications currently on it), 'Pause' it, apply the Windows updates, then 'Resume' it, &
reboot ?

Similar Messages

Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008

Hi,
I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
SQL server 2008.
The specific error is The error is Attempted to perform an unauthorized operation."
at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
Can someone comment on how to resolve this issue. I also tried NT
AUTHORITY\SYSTEM but getting the same error.
Any help would be appreciated.

Hello,
Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
http://support.microsoft.com/kb/955392
If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
may help you locate those files on disk::
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Security Update for SQL Server 2008 R2 Service Pack 2 (KB2977320)

So i have been trying to install this update on one of our servers since it is showing up on our MBSA scans but it has been failing on one of our machines with the error code: 0x80070643
I downloaded the update and tired to install it manually. The installer returned: There are no SQL Server instances or shared features that can be updated on this computer. If that was true then why is SCCM still pushing the update to the machine and why
is the MBSA showing that it needs the update? Any advice would be helpful. Thanks!

Hi David,
Based on my understanding, the error code: 0x80070643 was thrown out when you install KB2977320 with MBSA. And installation also failed when you download and install update manually.
Regarding the error code: 0x80070643, it can be caused if the MSI software update registration has become corrupted, or if the .NET Framework installation on the computer has become corrupted. To fix this issue, we can follow these methods:
Fix MSI software update registration corruption issues
Repair the .Net Framework
Uninstall and reinstall the .Net Framework
For more information, please refer to this link:
http://support.microsoft.com/kb/976982.
Besides, the security update is released for SQL Server 2008 R2 Service Pack 2, please check the version of SQL Server you are using. About how to check the SQL Server version, please refer to this article: How to tell what SQL Server version you are running
(http://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/). Then please download the Security Update for SQL
Server 2008 R2 Service Pack 2 from this link (http://www.microsoft.com/en-us/download/details.aspx?id=43957), and retry install it manually.
Best regards,
Qiuyun Yu

WSUS service pack updates for SQL Server 2008 R2

Hello, how do we configure WSUS for SQL Server Service Packs? One problem we have is that we do not see SQL server 2008 R2 SP2 available as a download from our WSUS server and this is when SQL SP1 is installed. Now I can apply these service packs manually
but when we have 100's of virtual machines with different versions and editions of SQL this task can be quite daunting. Suggestions please?
RFDZ12

from memory, SQL service packs and CUs are not released via WSUS.
This article is a good reference for (products other than Windows) for what has been released via WSUS:
http://technet.microsoft.com/en-us/windowsserver/bb456965
The equivalent article for Windows releases, is
http://support.microsoft.com/kb/894199
Or, you can check the MU catalog (which doesn't necessarily mean the update is available via WSUS, but if the update you seek in is the MU catalog, you can usually import it into your WSUS)
http://catalog.update.microsoft.com/
some updates for products are not able to be released via WSUS, for various reasons, and so in those cases, you need a different deployment solution.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         G:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

Crystal Reports XI connection problems - after updating to SQL Server 2008

Hello!
We have some ASP.NET 2.0 Applications that call some CR XI report files with parameters to generate PDF Files. After upgrading from SQL Server 2005 to 2008 the apps hang when trying to generate the PDFs. Some research with Fiddler showed that ever time a 401 Error is raised. Calling the reports directly from CR Designer with the same connection values and Parameter shows the appropriate data that means the log-in data iare functioning.
I already tried switching the data source driver from OLE DB to SQL Native - no effect!
Can it be that CR XI does not work with SQL Server 2008? Or is there an update for CR XI and SQL Server 2008?
Because we are in a hurry I hope somebody can solve my problem(s) ...?!
Thanks in advance,
Frank

Hi Frank,
No CR XI is not supported nor is any version completely at this time. What we've found issues in so far are the Time(7) time is returned as a string value and Stored Procedure Data/time parameter SQL creation. The Time(7) field is an OLE DB driver issue with Microsoft but the Date/time SP issue is our issue and it's currently tracked and escalated. It will be fixed for CR 2008 with SP3 I believe. And I've asked that the same fix be rolled back to CR XI R2 but waiting on the reply from R&D if it can be done.
What you need to do is download the trial version of CR XI R2 ( Release 2 ) and then use your XI Keycode to install it and it will work. Then update to the latest SP 5 Service Pack. XI is past it's end of life support which means there will be no updates or bug fixes any more.
Next, MS SQL Server 2008 does not work with the MDAC version of the Native drivers, you must install the MS SQL Server Client. You'll see the driver name is "MS SQL Server Native client 10". This is the one you need to use.
Another work around is to use ODBC, it seems to resolve all issues, but the client must be installed.
Thank you
Don

How to resolve a windows authenticated orphaned user in Sql Server 2008 R2?

Hi,
We have some orphaned windows authenticated users(domain) in the database while it had been
migrated from Sql Server 2005 to Sql Server 2008 R2, because there are no corresponding
logins for the users. Will just adding the logins would be sufficient or after adding the
logins should we also run sp_change_users_login @Action='update_one' to resolve any sid
conflict. Thanking you in advance,
With regards
Binny Mathew

Binny
You have issue with orphaned users if you use Mixed Authentication. If you use Windows and move the db to the new server the Windows Login should be exist on the new server already.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Compatability: CR 2008, VS 2005 and SQL Server 2008 on WINDOWS 7

Crystal Reports 2008, Visual Studio 2005 and SQL Server 2008 all play nice together on a VISTA or XP box. But we cannot get a connection when we switch the OS to WIN 7. I tried to get a connection via the report designer. Is this combination of technologies currently supported?
Thanks.

Hi, Jeff;
See the [Platforms|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/00225757-ab5c-2c10-c1a8-fb9f9f0f4ac2] document for CR 2008. You need Service Pack 2 to run on Windows 7.
If you already have SP 2, then what happens when you try to make a connection?
Regards,
Jonathan
Follow us on Twitter u2013 http://twitter.com/SAPCRNetSup

Side By Side Configuration Error Windows 7 64 bit and SQL SERVER 2008 R2

Hi,
I keep getting the side by side error... I tried installing the patches, and service packs i reinstalled sql server 2008 r2 like 10 times. It won't go away. I tried the registry edit a few people say works. This has been killing me for a week now,
I cannot run my sql server on my machine its crazy..???
Please help
thanks, NIck
Activation context generation failed for "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe". Dependent Assembly Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
could not be found. Please use sxstrace.exe for detailed diagnosis.
Log Name:      Application
Source:        SideBySide
Date:          2/16/2014 10:36:55 PM
Event ID:      33
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Nick-PC
Description:
Activation context generation failed for "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe". Dependent Assembly Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
could not be found. Please use sxstrace.exe for detailed diagnosis.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SideBySide" />
    <EventID Qualifiers="49409">33</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-17T03:36:55.000000000Z" />
    <EventRecordID>505191</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Nick-PC</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

Hi NickDeNora,
According to your description, we need to verify if you install
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) and
correct the manifest file. The manifest file is readable (although empty), but we cannot edit it (even if you are an administrator). Only SYSTEM has access to the file. So to be able to edit it, you must first take ownership of
it and grant ACLs. After saving the file, then run the setup again.
For more information , see:
http://blogical.se/blogs/johan/archive/2012/06/23/sql-server-vc-installation-voes.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Resore SQL server 2008 SP3 database to SQL server 2008 R2 SP1

I have a dump from a SQL server 2008 SP3 server and I'm trying to restore it to SQL server 2008 R2 SP1 server but getting the error:
Msg 3241, Level 16, State 0, Line 2
The media family on device 'E:\Work\backup.bak0' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 2
RESTORE FILELIST is terminating abnormally.
Are these versions incompatible or is it just a problem with the file? If they are incompatible, I could upgrade my target server to SQL server 2008 R2 SP2, would this help?
The exact version info is as follows:
Source server: Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Target Server: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (X64) Apr 22 2011 19:23:43 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Thanks in advance for your help.

SQL server 2008 SP3 is technically a lower version than 2008 R2 SP1
but it was released after it.
The service packs release date don't matter, only the major+minor build versions are important; restore should work in your constellation.
During FTP transfer the file could be damaged, that's possible. The backup file could be also "blocked" by OS because it was download from a different server; then you have to unblock it like every other download file.
Olaf Helper
[ Blog] [ Xing] [ MVP]

How do I return two values from a stored procedure into an "Execute SQL Task" within SQL Server 2008 R2

Hi,
How do I return two values from a
stored procedure into an "Execute SQL Task" please? Each of these two values need to be populated into an SSIS variable for later processing, e.g. StartDate and EndDate.
Thinking about stored procedure output parameters for example. Is there anything special I need to bear in mind to ensure that the SSIS variables are populated with the updated stored procedure output parameter values?
Something like ?
CREATE PROCEDURE [etl].[ConvertPeriodToStartAndEndDate]
@intPeriod INT,
@strPeriod_Length NVARCHAR(1),
@dtStart NVARCHAR(8) OUTPUT,
@dtEnd NVARCHAR(8) OUTPUT
AS
then within the SSIS component; -
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Below execute statement should work along the parameter mapping which you have provided. Also try specifying the parameter size property as default.
Exec [etl].[ConvertPeriodToStartAndEndDate] ?,?,? output, ? output
Add a script task to check ssis variables values using,
Msgbox(Dts.Variables("User::strExtractStartDate").Value)
Do not forget to add the property "readOnlyVariables" as strExtractStartDate variable to check for only one variable.
Regards, RSingh

MS14-044 for SQL Server 2008 Standard on Windows Server 2003?

MS14-044 was recently released and states that it applied to MS SQL Server 2008 SP3, yet the patches available for this security bulletin do not list Windows Server 2003 in the supported operating systems. Does MS14-044 not apply to SQL Server running
on Windows Server 2003? If it does apply, why isn't there an update available to run on Windows Server 2003?

Hi Chasg76,
According to your description, the patches available for MS14-044 do not list Windows Server 2003 in the supported operating systems and you want to know whether MS14-044 applies to SQL Server running on Windows Server
2003.
Based on my test, KB2977321 applies to SQL Server 2008 Service Pack 3 product and it does apply to SQL Server 2008 SP3 running on Windows Server 2003.
I installed SQL Server 2008 Service Pack 3 in Windows Server 2003 SP2 x86. After the service pack 3 installation completed, KB2977321 was offered in the Automatic Update.
Besides, you can manually install the update by downloading the update form the Download Center web site as well.
I also tried the manually installation and I downloaded the Security Update for SQL Server 2008 Service Pack 3 (KB2977321) from this web: Security Update for SQL Server 2008 Service Pack 3 (KB2977321) (https://technet.microsoft.com/library/security/MS14-044),
it was installed successfully.
After installed security upgrade, I checked the file attributes and compared to this article: MS14-044: Description of the security update for SQL Server 2008 SP3 (GDR): August 12, 2014(http://support.microsoft.com/kb/2977321/en-us).
The result is the same.
According to my test, MS14-044 applies to SQL Server running on Windows Server 2003 even though Windows Server 2003 is not listed in the supported operating systems.
Best regards,
Qiuyun Yu

Has mssql2008r2 got "Cumulative Update Package 6 for SQL Server 2008 Service Pack 1"

hi,
I have
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) Apr 2 2010 15:53:02 Copyright (c) Microsoft Corporation Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
, i wanted to know has it got
"Cumulative Update Package 6 for SQL Server 2008 Service Pack 1"
so that i do not have to install or i have to install
yours sincerley

Thank u, please tel me can i instal sp3.
I have noticed the link of sp2 (http://www.microsoft.com/en-in/download/details.aspx?id=30437)
has listed
(SQL Server 2008 R2 Express Edition)
SQL Server 2008 R2 Service Pack 2 (SP2) is now available for download. SQL Server 2008 R2 service packs are cumulative and can be used to upgrade all releases of SQL Server 2008 R2 to Service Pack 2. SQL Server 2008 R2 Service Pack 2 contains Cumulative Update
1 to 5 from SQL Server 2008 R2 SP1. The package can be used to upgrade the following SQL Server 2008 R2 editions:
SQL Server 2008 R2 Parallel Computing Edition
SQL Server 2008 R2 Datacenter Edition
SQL Server 2008 R2 Enterprise Edition and Developer Edition
SQL Server 2008 R2 Standard Edition
SQL Server 2008 R2 Web Edition
SQL Server 2008 R2 Workgroup Edition
SQL Server 2008 R2 Express Edition
where as link of sp3(http://www.microsoft.com/en-us/download/details.aspx?id=44271)
has not listed express edition but written in general.
SQL Server 2008 R2 Service Pack 3 (SP3) is now available for download. SQL Server 2008 R2 service packs are cumulative and can be used to upgrade all releases of SQL Server 2008 R2 to Service Pack 3. SQL Server 2008 R2 Service Pack 3 contains
Cumulative Update 1 to 13 from SQL Server 2008 R2 SP2. The package can be used to upgrade the following SQL Server 2008 R2 editions:
SQL Server 2008 R2 Parallel Computing Edition
SQL Server 2008 R2 Datacenter Edition
SQL Server 2008 R2 Enterprise Edition and Developer Edition
SQL Server 2008 R2 Standard Edition
SQL Server 2008 R2 Web Edition
SQL Server 2008 R2 Workgroup Edition
yours sincerley

SQL Server 2008 R2 on Windows 2012 R2

It appears I cannot install SS2008 R2 on WS2012 R2. I get the following:
'Your version of Microsoft SQL Server (2008 and 2008 R2) isn't compatible with this version of Windows.'
Can someone please confirm this and when this issue might be resolved?

Hello,
Please try a slipstream installation of SQL Server 2008 R2 + SP2 using the following article:
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801

Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801

Apply monthly Windows 2008 r2 updates within SQL Server 2008 cluster

Similar Messages

Maybe you are looking for