SQL Server 2008 R2 SP3 compatibility with TFS 2012?

Hi all,
I have a client who is planning on upgrading from SQL Server 2008 R2 SP2 to SQL Server 2008 R2 SP3 but wants to make sure that their installed Team Foundation Server 2012 databases will be ok?
I have found a Microsoft article saying that TFS 2012 support SQL Server 2008 R2 SP2 but nothing about SP3.
Thanks for your help!
Martyn

Hi Martyn,
According to this
article, Team Foundation Server 2012 (TFS 2012) requires SQL Server 2008 R2 SP1 or SQL Server 2012. From my point of view, it means that we need to run at least SQL Server 2008 R2 SP1 when using TFS 2012, and TFS 2012 can work with SQL Server 2008
R2 SP1 later version (contains SQL Server 2008 R2 SP2 and SQL Server 2008 R2 SP3).
In addition, we recommend you install the latest released service pack for your SQL Server, as service pack includes a number of important fixes that TFS could benefit from.
For TFS issues, for quick and accurate response, I would like to recommend that you ask the question in the Visual Studio Team Foundation Server forums at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=vstfs . It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

Similar Messages

SQL Server 2008 R2 Standard - Compatibility issues with Windows Server 2012 R2

Hello,
We used as a test a box on which we installed Windows Server 2012 R2 and SQL Server 2008 R2 Standard Edition. No Service pack was installed. It worked perfect.
Now we try to do it on another box and all of the sudden there is compatibility issue when we try to instal SQL Server. We can still install SQL Server by clicking "Continue without getting help".
Where can this come from? If it is hardware related what are the thing I should look at?
Thanks all

Hello,
Adding to Shanky suggestion, you can perform a slipstream installation of SQL Server 2008 R2 + SP3 to make SQL Server
2008 R2 compatible with the newer operating system, as explained on the following post.
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
https://support.microsoft.com/en-us/kb/955392/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Missing MSI files SQL Server 2008 R2 SP3

I have hit an issue while installing Service Pack 3 for SQL Server 2008 R2. The existing version is
10.50.4295.0 (SP2+CU9)
When running the SP3 file the following error occurs
SQL Server Setup has encountered the following error:
The cached MSI file 'C:\Windows\Installer\91a4f43.msi' is missing.
Its original file is 'sql_engine_core_inst.msi' and it was installed for product 'SQL Server 2008 R2 SP2 Database Engine Services' from '\\ServerName\Share$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\', version '10.52.4000.0', language 'ENU'.
To resolve this problem, recover the missing file from the installation media and start setup again.
For more information about how to resolve this problem, see 'Steps to restore the missing Windows Installer cache files' (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge Base.
Error code 0x84B20002.
The next I tried to remove CU9 before applying SP3. The following error occurred when CU 9 was attempted to be removed.
The cached patch file 'C:Windows\Installer\483c7040.msp' is missing.

Hello Alberto,
I tried this link
http://support.microsoft.com/kb/969052
Using the VB script FindSQLInstall I tried getting some details about the missing MSI files. Just sharing the details incase you may have some details or better insight on what it says.
!!!! C:\Windows\Installer\91a4f43.msi DOES NOT exist in the Installer cache. !!!!
      Action needed, recreate or re-establish path to the directory:
\\Servername\Sharename$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\then rerun this script to update installer cache and results
     The path on the line above must exist at the root location to resolve
     this problem with your msi/msp file not being found or corrupted,
     In some cases you may need to manually copy the missing file or manually
     replace the problem file overwriting it is exist:
      Copy "\\Servername\ShareName$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi" C:\Windows\Installer\91a4f43.msi
It points to a location that doesn’t exist in the central server (servername) from where usually the installation media is present. The folder structures were re-arranged and the path mentioned (\\Servername\ShareName$\SQL\SQL105\ENT\x64\setup\sql_engine_core_inst_msi)
is no longer there.
Now from where do I copy this particular .MSI file? I've tried using search option but I'm unable to find it.
One more update is that I was successfully able to do the SP3 upgrade on another server which was SQL Server 2008R2 SP2 (No CU on it)
Hi Jayakrishna,
After your above steps, please put the SQL Server setup media on the same path
\\Servername\Sharename$\SQL, then run the VB script again and it will recreate the MSI file on the path C:\Windows\Installer with the name “91a4f43.msi“.
If the error still occurs, then you can manually restore the missing MSI file following the steps of Procedure 2 in this article:
http://support.microsoft.com/kb/969052 .
In addition, we recommend you use local copy of media to install SQL Server 2008 R2 SP3.
Thanks,
Lydia Zhang

SQL Server 2008 R2 SP3 install error - caspol.exe Fatal error

When I attempt to install sql server 2008 r2 sp3 I get caspol.exe - Fatal error. Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt. Please check or rerun setup. Then after I click ok I get the Microsoft Windows
popup that says Microsoft .NET Framework CAS Policy Manager has stopped working. This is on a Windows 2008 Enterprise Server, service pack 2. I am wondering if my .NET Framework had become corrupt on the server. Any ideas? This has
been on a stable production sql server that has been running fine for many years.
Thanks for reading my post.
Joe Sitver

Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt. Please check or rerun setup.
Hi Joe,
Mscorjit.dll (Microsoft .NET Runtime Just-In-Time Compiler) is a component of Web developing applications and the most prominent program that makes use of this file is the Microsoft.NET Framework.
The most common reason of the above error is that there is an improper installation/update of your .NET framework. Please
use this
tool to repair .NET framework. If the issue persists, you might need to uninstall and reinstall your
.NET framework.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

JTDS not connecting with SQL Server 2008 R2 SP2 + SSL with Java 6 U34-35

Environment:
Windows 7 Pro 32-bit
SQL Server 2008 R2 SP2 (Forced Encryption = Yes, No Certificate provided to server)
Java 6 Update 27-35 and Java 7 Update 2-7
jTDS 1.2.2 and 1.2.6
Under the following setup, our Java application is able to connect to the SQL Server database:
- SQL Server 2008 R2 SP2
- Java 6 Update 27-33 or Java 7 Update 2-5
just switching the JVM to the following would cause the application to be unable to connect to the database:
- Java 6 Update 34 or 35, or Java 7 Update 6 or 7
Browsing through the Java 6 Update 34 release notes, it looks like nothing big was changed, so I'm wondering what has changed with Java 6 U34 and Java 7 U6. I was also looking through a packet sniffer, and indeed the behavior of Java 6 Update 33 and lower was different from Java 6 Update 34 (although I couldn't understand the messages being passed, the number of connections and messages were different).
* This is different from the issue with Java 6 Update 29-30 and Java 7 wherein they were patched for the BEAST SSL vulnerability. That was fixed with the SP2 patch for SQL Server 2008 R2, and for SQL Server 2008 you'd need a hotfix aside from SP3. After patching the server with those updates, Java 6 Update 29-33 and Java 7 U1-5 should be able to connect to the database.
* If I do switch off Force Encryption, all Java versions are able to connect to the database.
Edited by: user1357749 on Oct 12, 2012 1:20 AM

Hi,
It's four months later, but my colleague and I have reproduced the same behavior in both our commercial product, and a very simple example class. It's exactly as you describe it, where the latest versions of both Java 6 and 7 (and several previous versions) hang during the first jTDS SQL query to the DB (immediately after the SSL and handshake). It also happens with the Microsoft JDBC driver.
If you disable the BEAST SSL fix (-Djsse.enableCBCProtection=false), then the connections work without any problems. So, while this is different from the original BEAST SSL problem and subsequent fix, it really seems like some additional changes were made to the fix in a later Java release that broke things.
My colleague has filed a bug with Oracle, and is awaiting a response. We also filed a bug at the jTDS project (#690 - http://sourceforge.net/p/jtds/bugs/690/) that has simple reproduction steps. A contributer at the jTDS project agrees that this seems to be a problem with the JRE, and is not specific to jTDS.
I hope that Oracle will address this issue soon. We need to periodically update the JRE due to vulnerabilities, and we need to have SSL for our JDBC connections for security reasons. This bug puts us and others in a difficult position.

SQL Server 2008 Express -- Process exited with code -2068643839

When installing SQL Server 2008 Express, I continue to get the following info in the install log. I notice that I only get this issue with 64-bit PC's (win 7 & win 8.1). Ideas?
Thanks.
The following components failed to install:
- SQL Server 2008 Express
See the setup log file located at 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\install.log' for more information.
The following properties have been set:
Property: [AdminUser] = true {boolean}
Property: [InstallMode] = SameSite {string}
Property: [ProcessorArchitecture] = AMD64 {string}
Property: [VersionNT] = 6.1.0 {version}
Running checks for package 'Windows Installer 3.1', phase BuildList
The following properties have been set for package 'Windows Installer 3.1':
Running checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1': true
Result of checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
'Windows Installer 3.1' RunCheck result: No Install Needed
Running checks for package 'SyncSDK', phase BuildList
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Install Needed
Running checks for package 'Windows Installer 4.5', phase BuildList
Looking up path for special folder 'WindowsFolder'
Running check with folder 'C:\Windows\System32' and file 'msi.dll'
Attempting to find file 'C:\Windows\System32\msi.dll'
File version is '5.0.7601.18637'
Setting value '5.0.7601.18637 {version}' for property 'VersionMsiDll'
The following properties have been set for package 'Windows Installer 4.5':
Property: [VersionMsiDll] = 5.0.7601.18637 {version}
Running checks for command 'WindowsInstaller4_5\WindowsXP-KB942288-v3-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsXP-KB942288-v3-x86.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsXP-KB958655-v2-x86-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsXP-KB958655-v2-x86-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x86.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB958655-v2-x86-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB958655-v2-x86-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x64.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x64.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003.WindowsXP-KB958655-v2-x64-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003.WindowsXP-KB958655-v2-x64-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x86.MSU'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22308': true
Result of checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x86.MSU' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x64.MSU'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22308': true
Result of checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x64.MSU' is 'Bypass'
'Windows Installer 4.5' RunCheck result: No Install Needed
Running checks for package 'Microsoft .NET Framework 4 (x86 and x64)', phase BuildList
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full'
Read string value '4.5.50938'
Setting value '4.5.50938 {string}' for property 'DotNet40Full_TargetVersion'
The following properties have been set for package 'Microsoft .NET Framework 4 (x86 and x64)':
Property: [DotNet40Full_TargetVersion] = 4.5.50938 {string}
Running checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe'
Result of running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'DotNet40Full_TargetVersion' and value '4.0.30129': true
Result of checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe' is 'Bypass'
Running checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe'
Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': true
Result of checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe' is 'Bypass'
'Microsoft .NET Framework 4 (x86 and x64)' RunCheck result: No Install Needed
Running checks for package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)', phase BuildList
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client'
Read string value '4.5.50938'
Setting value '4.5.50938 {string}' for property 'DotNet40Client_TargetVersion'
The following properties have been set for package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)':
Property: [DotNet40Client_TargetVersion] = 4.5.50938 {string}
Running checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe'
Result of running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'DotNet40Client_TargetVersion' and value '4.0.30129': true
Result of checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe' is 'Bypass'
Running checks for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': true
Result of checks for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Bypass'
'Microsoft .NET Framework 4 Client Profile (x86 and x64)' RunCheck result: No Install Needed
Running checks for package 'SQL Server 2008 Express', phase BuildList
Running external check with command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SqlExpressChk.exe' and parameters '10.0.1600 1033'
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressChk'
The following properties have been set for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 1 {int}
Running checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator 'ValueNotExists' on property 'VersionNT': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0': false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-1': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-2': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-3': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-4': false
Result of running operator 'ValueLessThan' on property 'SQLExpressChk' and value '-4': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': true
Result of checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': true
Result of checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '1': false
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Install'
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '2': true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Bypass'
'SQL Server 2008 Express' RunCheck result: Install Needed
EULA for components 'SQL Server 2008 Express' was accepted.
Installation of components 'SyncSDK' was accepted.
Copying files to temporary directory "C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\"
Copying from 'C:\Installs\NewMBA\SynSDK\syncsdk-v2.1-x86-enu.msi' to 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi'
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi
WinVerifyTrust returned 0
File trusted
Copying from 'C:\Installs\NewMBA\SqlExpress2008\SQLEXPR_x64_ENU.EXE' to 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE
WinVerifyTrust returned 0
File trusted
Running checks for package 'SyncSDK', phase BeforePackage
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Install Needed
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi
WinVerifyTrust returned 0
File trusted
Installing using command 'C:\Windows\SysWOW64\msiexec.exe' and parameters ' -I "C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi" -q '
Will attempt to elevate process.
Process exited with code 0
Running checks for package 'SyncSDK', phase AfterPackage
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Unknown
Running checks for package 'SQL Server 2008 Express', phase BeforePackage
Running external check with command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SqlExpressChk.exe' and parameters '10.0.1600 1033'
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressChk'
The following properties have been set for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 1 {int}
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '1': false
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Install'
'SQL Server 2008 Express' RunCheck result: Install Needed
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE
WinVerifyTrust returned 0
File trusted
Installing using command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE' and parameters '/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network
Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck'
Process exited with code -2068643839
Status of package 'SyncSDK' after install is 'InstallUnknown'
Status of package 'SQL Server 2008 Express' after install is 'InstallFailed'

The SP3 patch installed ok.
When I ran my software installer, it failed again w/ the error 1001.
Here is the summary.txt.
Overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:26:40
End time:                      2015-01-20 19:37:08
Requested action:              Patch
Instance MSSQLSERVER overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:31:48
End time:                      2015-01-20 19:34:52
Requested action:              Patch
Instance MBA overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:34:57
End time:                      2015-01-20 19:36:17
Requested action:              Patch
Instance MBANEW overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:36:21
End time:                      2015-01-20 19:37:01
Requested action:              Patch
Machine Properties:
Machine name:                  JOHN
Machine processor count:       4
OS version:                    Windows Vista
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
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                 Express Edition      10.3.5500.0     No
Sql Server 2008      MBA                  MSSQL10.MBA
Database Engine Services                 1033                 Express Edition
10.3.5500.0     No
Sql Server 2008      MBANEW               MSSQL10.MBANEW                 Database
Engine Services                 1033                 Express Edition
10.3.5500.0     No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       3
KBArticle:                     KB2977321
KBArticleHyperlink:
PatchType:                     GDR
AssociatedHotfixBuild:         5869
Platform:                      x64
PatchLevel:                    10.3.5520.0
ProductVersion:                10.3.5500.00
GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0
PackageName:                   SQLServer2008-KB2977321-x64.exe
Installation location:         c:\adcd5df38e670a98a9f2aafcc70e\x64\setup\
Updated product edition:
Instance             Edition
MSSQLSERVER          EXPRESS
MBA                  EXPRESS
MBANEW               EXPRESS
User Input Settings:
ACTION:                        Patch
ALLINSTANCES:                  False
CLUSTERPASSIVE:                False
CONFIGURATIONFILE:
HELP:                          False
INDICATEPROGRESS:              False
INSTANCENAME:                  <empty>
QUIET:                         False
QUIETSIMPLE:                   False
X86:                           False
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150120_192631\SystemConfigurationCheck_Report.htm

Sql server 2008 r2 backward compatibility to 2005

I've been told to get the backward compatibility patch from sql server 2008 r2 to 2005. I can't determine where to get the patch. Additionally, I 've been told that it must be done in a particular order but I can't seem to find any information
on the procedure to follow either.

Hello,
You will find it on the following URL. Click on detail and look for SQLServer2005_BC.msi.
http://www.microsoft.com/en-us/download/details.aspx?id=27596
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sql server 2008 r2 reportserver integration with sharepoint 2010 datasource credential

hello,
I am using sharepoint 2010 and sql server 2008 r2 and integrated in sharepoint integration mode and i am using windows authentication ,not keberos ,so i deletd negotiate in authentication tag in rssharepoint.config file,but when i tried to create data source
i am getting credential error and when windows credential is used it is getting connected.
please help.
thanks

Hi Krishnakumar_DeV,
Based on the current description, I understand that you should use the Windows NTLM authentication and delete the Negotiatein in authentication tag from RSReportServer.config which is located in the folder “C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\XX\WebServices\Reporting”. You can use a local account or domain account to connect report server, while there is credential error message when creating data source, right?
To narrow down the issue, I want to confirm some information below:
1. To connect to remote data source, we can specify the following credentials’ ways:
•Prompt the user for credentials
•Store credentials
•Use Windows integrated security
•Use no credentials
Which credential way is you using and what’s the detailed error message?
2. How do you create the data source?
If I have any misunderstanding, please feel free to contact me.
Regards,
Heidi Duan
Heidi Duan
TechNet Community Support

SQL Server 2000 Enterprise Edition Compatability with Latest Operating Systems

Hi Team,
My client is using SQL Server 2000 Enterprise edition for the database in the Production.
Now,We are planning to load that data from SQL 2000 to SQL 2012 and test the functionality.
Can you please tell me on which operations systems the SQL Server 2000 is compatible to Install ?
like Windows Server 2012/ 2012 R2/ Windows 7/ 8 etc.
Thanks
Srikrishna

Installing SQL Server 2000 on Windows 2008 or later is not supported, but your question is about compatibility rather than support. SQL Server 2000 may work with the database engine but not with some other features and you'll probably need
to click through warnings installation. Proceed at your own risk if you want to go down that path.
I suggest you install on Windows 2003 for your migration testing to avoid obstacles. Not that support ends for Windows Server 2003 in a few months.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

SQL server 2008 Service pack install with mirroring

Just looking for some official documentation about installing service pack 3 when I have a mirrored set up in high-safety mode with automatic failover.
I have found this,
http://msdn.microsoft.com/en-us/library/bb677181%28v=sql.100%29.aspx would the same apply to the service packs as well?
Thanks

Hi,
Below is official doc applies from SS2005 to SS2012. Please follow this not what you have pasted
Applying CU and SP on database which is mirrored
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

ODBC function SQLDriverConnect() crashes with SQL Server 2008 R2

When calling the SQLDriverConnect() function from a 64-bit process and selecting a system DSN with a SQL Server Native Client 10.0 ODBC driver with SQL Server 2008 R2 SP3, then this call crashes here:
    sqlncli10.dll!SNIMemRegion::Pop() + 0x77 bytes
    sqlncli10.dll!SNIPacketAllocateEx2() + 0xa8 bytes
    sqlncli10.dll!Np::ReadSync() + 0x7e bytes
    sqlncli10.dll!Ssl::HandshakeReadToken() - 0x1b bytes
    user32.dll!InternalDialogBox() + 0x132 bytes
    user32.dll!DialogBoxIndirectParamAorW() + 0x56 bytes
    user32.dll!DialogBoxParamW() + 0x85 bytes
    sqlncli10.dll!SQLDriverConnectW() + 0x34f23 bytes
    odbc32.dll!SQLInternalDriverConnectW() + 0x17c bytes
    odbc32.dll!SQLDriverConnectW() + 0xa15b bytes
Am I calling SQLDriverConnect() correctly (see below)? Or is this a bug in the 64-bit version of the ODBC driver?
In the 32-bit version, everything works fine.
Here is a test program:
int _tmain(int argc, _TCHAR* argv[])
SQLHENV hEnv = NULL;
SQLHDBC hDbc = NULL;
SQLRETURN ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
ret = SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) SQL_OV_ODBC3, 0);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO)
fprintf(stderr, "SQLSetEnvAttr failed\r\n");
return EXIT_FAILURE;
ret = SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
SQLTCHAR szConnection[2048];
SQLSMALLINT cbChars;
ret = SQLDriverConnect(hDbc, ::GetDesktopWindow(), (SQLTCHAR*) _T(""), SQL_NTS,
szConnection, _countof(szConnection)-1, &cbChars, SQL_DRIVER_PROMPT);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO && ret != SQL_NO_DATA)
fprintf(stderr, "SQLDriverConnect failed\r\n");
return EXIT_FAILURE;
else
fprintf(stdout, "Success\r\n");
return 0;
The stdafx.h contains the following includes:
#include "targetver.h"
#include <stdio.h>
#include <tchar.h>
#include <Windows.h>
#include <sql.h>
#include <sqlext.h>
#include <assert.h>
Steps to reproduce the crash: compile program with Visual Studio 2010 as 64-bit console application; run it and select a 64-bit SQL Server DSN.
If the crash does not occur, try using the "AllocationPreference" registry entry set to 0x100000 (see https://msdn.microsoft.com/en-us/library/windows/hardware/Dn613975%28v=vs.85%29.aspx for details); don't forget to reboot Windows. This registry
helps to find 64-bit portability issues.

Hi T.holt,
Personally, I don’t believe SQL 2008 R2 with ADMT 3.2 is supported. From the guidelines of install the Active Directory Migration Tool (ADMT), ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. We
should use SQL Server Express and install ADMT v3.2 on a member server. ADMT installation enforces the following service pack requirements:
• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.
If you use full versions of SQL Server 2005 or SQL Server 2008. In this case, you need to install and run the ADMT console on a remote computer, and you can run multiple ADMT consoles on different remote computers. If
you use a full version of SQL Server, ADMT installation does not enforce any service pack requirements.
For more information about installing ADMT in the target domain, you can review the following article.http://technet.microsoft.com/en-us/library/cc974370(v=ws.10).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

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

Cannot install SQL Server 2008 R2 Developer on Windows 8.1

I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
TITLE: SQL Server 2008 R2 Setup
The following error has occurred:
Attempted to perform an unauthorized operation.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
This is my log file:
Overall summary:
Final result: User cancelled
Exit code (Decimal): 0
Exit message: User cancelled
Start time: 2014-04-23 23:49:10
End time: 2014-04-24 00:03:44
Requested action: Install
Machine Properties:
Machine name: PC
Machine processor count: 2
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: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: PC\computername
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
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:
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: PC\computername
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Analysis Services
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: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
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: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\SystemConfigurationCheck_Report.htm
I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.

Hello,
1. Please refer to solution provided in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
If above does not works include below as well
3. Please verify WMI service is started.
If WMI is started, consider to repair WMI.
http://windowsxp.mvps.org/repairwmi.htm
Reference
Link
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Can't uninstall SQL Server 2008 R2 Express

Hi all,
I have unfortunately let myself be persuaded (by a company selling a solution to us) to install SQL Server 2008 R2 Express on a Windows 2012 Standard Server.
At first it didn't work, the installation wizard told me to reboot the server - so I did. No change the checklist stopped at the same thing again telling me to reboot first...
Found out that I could install by using this command: SQLEXPR_x64_ENU.exe /SkipRules=RebootRequiredCheck /ACTION=install
Seemed to work, all fine! Rebooted and tried to install SQLManagmentStudio_x64_ENU.exe and got a compability warning saying that the SQL Server 2008 R2 Express is not compatible with Windows 2012 Standard Server.
I thought "Right, uninstall it and then install a new and compatible version" Can't uninstall!!
It stops with this error and nothing happens uninstall wise:
Windows Features
The following feature couln't be installed:
.NET Framework 3.5 (includes .NET 2.0 and 3.0)
Windows Server roles and features cannot be automatically installed or uninstalled via the Windows Feature Control Panel.
To install Windows Server roles and features, start Server Manager, or use the Server Manager cmdlets for Windows PowerShell.
When I look in remove roles and features there's no checkmark in .NET 3.5 Framework and it's also grayed out....
Please Help! :)
BR,
Micael

Hello,
Try installing from the Command Prompt as explained on the following resource.
http://www.sqlcoffee.com/Troubleshooting101.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 SP3 compatibility with TFS 2012?

Similar Messages

Maybe you are looking for