Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

Shouldn't I be able to upgrade to 2008 R2?
Current version:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

I've the same problem as described above.
My Version is: 10.0.2531.0 SP1
Standard Edition (64-bit), on Windows Server 2003
Additionally, I have SQL Server 2005 Developer installed on the same machine.
I choosed SQL Server 2008 to upgrade to R2.
In the log I found:
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' found no upgrade features.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'sql_engine_core_inst_ctp6_Cpu64' with SkuValue=STANDARD ProductVersion=10.0.1600.22
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition STANDARD for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=STANDARD sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix found match in sku matrix.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_engine_core_inst_Cpu64' permits upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'IS2005_Cpu64' with SkuValue=DEVELOPER ProductVersion=9.3.4035.00
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 9.0 and edition DEVELOPER for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=9.0 sourceEdition=DEVELOPER sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_is_Cpu64' is blocking upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
2010-10-01 17:54:31 Slp: Evaluating rule : FeatureUpgradeMatrixCheck
2010-10-01 17:54:31 Slp: Rule running on machine: <skipped>
2010-10-01 17:54:31 Slp: Rule evaluation done : Failed
2010-10-01 17:54:31 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 R2 version and edition upgrade matrix in Books Online.
Thanks,
Patrik

Similar Messages

Upgrade to SQL Server 2008 R2 fails

I'm trying to upgrade from SQL Server 2008 Express to SQL Server 2008 R2 Enterprise. The installation is failing. I get two log files. The first appears to be a summary. The second is an MSI install log file. The MSI log is too large to paste in here and
I cannot attach files, so I included the section where it appears to fail. Based on the log contents below, how can I fix this?
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068024447
Exit facility code:            1212
Exit error code:               29569
Exit message:                  Failed: see details below
Start time:                    2015-04-06 21:07:14
End time:                      2015-04-06 21:13:54
Requested action:              Upgrade
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\sql_engine_core_inst_ctp6_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.1600.1
Machine Properties:
Machine name:                  DAD-PC
Machine processor count:       12
OS version:                    Windows 7
OS service pack:               Service Pack 1
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.3.5500.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.3.5500.0     No
Sql Server 2008
Management Tools - Basic                 1033                 Express Edition
10.0.1600.22    No
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         H:\x64\setup\
Installation edition:          ENTERPRISE
User Input Settings:
ACTION:                        Upgrade
AGTDOMAINGROUP:                <empty>
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                True
FAILOVERCLUSTERROLLOWNERSHIP: 2
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
FTUPGRADEOPTION:               Import
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTANCEID:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSCATALOGSERVERINSTANCENAME:   Unknown
RSUPGRADEDATABASEACCOUNT:
RSUPGRADEPASSWORD:             *****
SQLDOMAINGROUP:                <empty>
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Writer
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Browser
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Compact Edition Tools
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
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\20150406_210629\SystemConfigurationCheck_Report.htm
PARTIAL MSI LOG BELOW
Action start 21:13:47: AppSearch.
MSI (s) (40:00) [21:13:47:914]: Note: 1: 1325 2: v2.0.50727
MSI (s) (40:00) [21:13:47:914]: Note: 1: 1325 2: EventLogMessages.dll
MSI (s) (40:00) [21:13:47:914]: PROPERTY CHANGE: Adding ASPNET_EVENTLOGDLL property. Its value is 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\EventLogMessages.dll'.
MSI (s) (40:00) [21:13:47:915]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\Setup 3: 2
MSI (s) (40:00) [21:13:47:915]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FBD367D1-642F-47CF-B79B-9BE48FB34007} 3: 2
MSI (s) (40:00) [21:13:47:915]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_32 property. Its value is 'C:\Program Files (x86)\Microsoft SQL Server\'.
MSI (s) (40:00) [21:13:47:916]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_64 property. Its value is 'C:\Program Files\Microsoft SQL Server\'.
MSI (s) (40:00) [21:13:47:916]: PROPERTY CHANGE: Adding DEVENV_IDE8 property. Its value is 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\'.
MSI (s) (40:00) [21:13:47:917]: PROPERTY CHANGE: Adding SQLSETUPARPWRAPPER property. Its value is 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release\x64\SetupARP.exe'.
MSI (s) (40:00) [21:13:47:917]: Doing action: RestoreSetupParams_64
Action ended 21:13:47: AppSearch. Return value 1.
MSI (s) (40:00) [21:13:47:920]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'RestoreSetupParams_64'
MSI (s) (40:C0) [21:13:47:921]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICCED.tmp, Entrypoint: RestoreSetupParams
Action start 21:13:47: RestoreSetupParams_64.
<Func Name='LaunchFunction'>
Function=RestoreSetupParams
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: RestoreSetupParams
PerfTime Start: RestoreSetupParams : Mon Apr 06 21:13:47 2015
<Func Name='RestoreSetupParams'>
        Error Code: 0x80077381 (29569)
Windows Error Text:   Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Thu Jul 3 22:23:09 2008
     Function Name: RestoreSetupParams
Source Line Number: 190
Error Code: 29569
MSI (s) (40!D0) [21:13:51:016]: Product: Microsoft SQL Server 2008 Database Engine Services -- Error 29569. SQL Server Setup failed to restore the instance id.
Error 29569. SQL Server Setup failed to restore the instance id.
<Failure Type='Fatal' Error='29569'>
<EndFunc Name='LaunchFunction' Return='29569' GetLastError='203'>
CustomAction RestoreSetupParams_64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Hello,
You shared with us the following lines part of one of the logs created during the upgrade process:
Error Code: 29569
MSI (s) (40!D0) [21:13:51:016]: Product: Microsoft SQL Server 2008 Database Engine Services -- Error
29569. SQL
Server Setup failed to restore the instance id.
These lines are associated with Registry corruption. If this instance is a production instance, please call Microsoft Support for help.
For more information, please read the answer provided by Cathy Miller (MSFT) on the following thread.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/15a67403-3e67-47cd-8595-4330945bd6cc/sql-server-2008-sp2-update-fails-error-29569-sql-server-setup-failed-to-restore-the-instance-id?forum=sqlsetupandupgrade
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Reports quit working after upgrade to SQL Server 2008

Folks,
I'm running Visual Studio 2008 (sp1) and recently upgraded to SQL Server 2008. Reports worked fine until after upgrade. Now I get the "Login Failed" error message.
Here is code snippets:
        CrystalDecisions.CrystalReports.Engine.ReportDocument oReport = new   CrystalDecisions.CrystalReports.Engine.ReportDocument();
        TableLogOnInfo LonOnInfo = new TableLogOnInfo();
        TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
        TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
        private Tables crTables;
        private Table crTable;
        ConnectionInfo crConnectionInfo = new ConnectionInfo();
            crConnectionInfo.IntegratedSecurity = true;
            crConnectionInfo.ServerName = Properties.Settings.Default.InstanceName + "
Instance";
            crConnectionInfo.DatabaseName = "DATABASE";
            crTables = oReport.Database.Tables;
            for (int i = 0; i < crTables.Count; i++)
                crTable = crTables<i>;
                crtableLogoninfo = crTable.LogOnInfo;
                crtableLogoninfo.ConnectionInfo = crConnectionInfo;
                crTable.ApplyLogOnInfo(crtableLogoninfo);
            oReport.RecordSelectionFormula = xFormula;
            crystalReportViewer1.ReportSource = oReport;
Has anyone had this problem? Any help would be appreciated.
Terry

CR 2008 does not support MS SQL 2008 yet, meaning we have not had time to test it completely and add it to our supported platforms.txt file.
One thing I noticed is you are using trusted authenication:
crConnectionInfo.IntegratedSecurity = true;
Make sure you give access to all users, MS changed the security properties a lot since SQL 2005 and you can't simply log into any database now. If you have a DBA check with that person on how to configure NT Authentication or the Help file. You can also do a quick test and simply use MS SQL Server authentication to confirm if it's a user permission issue.
Try creating a report that doesn't use Integrated Security, check the box off on your data logon prompt in the Designer.

SQL Server reporting services error "URl has already been reserved" while doing upgrade from SQL server 2008 R2 to SQL server 2012

"URl has already been reserved".
Reporting services for port 80 and 443 works fine both for reports and reportingserver on SQL server 2008 R2. But when I try to upgrade from SQL server 2008 R2 to 2012 this error pops up. How to make sure before upgrading regarding reporting services that
URL reserves and SSL are fine or how to fix reporting services are upgrade like repair install.
Thanks

Hi yashmitl,
In your case, please running the following command to check the current URL reservations on http.sys.
netsh http show urlacl
Then, please delete the URL reservation by executing the following command try to resolve the issue.
netsh http delete urlacl <url>
There is a similar issue, you can refer to it.
http://social.technet.microsoft.com/Forums/en-US/d5204dd3-e26d-4592-8ef0-a94005fc46a5/the-url-has-already-been-reserved?forum=sqlreportingservices
Hope this helps.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

I installed visual studio 2010 in my windows 8.1 system.during the installation sql server 2008 r2 features were installed.so which version of sql server i need to install(2008 or 2008 r2)?

hi,
I installed visual studio 2010 in my windows 8.1 system.during the installation sql server 2008 r2 features were installed.so which version of sql server i need to install(2008 or 2008 r2)?
regards,
harsha.

My guess is SQL Server 2008 R2.
Check the following KB article for details:
http://support.microsoft.com/kb/2681562
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Unable to upgrade from SQL Server 2008 R2 to SP1

Hi there
I am currently in the middle of installing and configuring Sharepoint 2013 on a Windows 2012 R2 Virtual Server. I have first installed SQL Server 2008 R2 and then installed sharepoint 2013 including all of the prerequisites.
When I go to the SharePoint products configuration wizard, I get an error on the 'specify configuration database settings' page saying that I do not have the right SQL version as sharepoint 2013 needs SQL server 2008 R2 SP1 installed.
So I downloaded SP1 for SQL server 2008 R2 x86 but when I run the update, there are no instances for me to select to upgrade - it just says 'Shared Features'.
Sorry if this is a silly question - I am quite new to SQL!
Tom

Hello,
You probably have a 64-bit SQL Server 2008 R2 instance but you downloaded a 32-bit version of SP1 for SQL Server 2008 R2.
Please download the 64-bit version of SP1.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrade to SQL Server 2008

Hi Forum,
We have SAP B1 8.8 with SQL Server 2005.
We'd like to upgrade our SQL Server 2005 to 2008.
Is there anything that we need to do on the SAP side to get this done?.
Regards,
Manuel Roman

Hi,
Are you the one creating the add-on? then you can recompile it anytime if not then try to contact
you developer to recompile it.
You can try creating a test database for 2008 then connect it this will assure that it will run.
Much better if you uninstall the 2005 then install the 2008 then restore your database.
Regards,
Clint

Unable to connect to sql server 2008 r2 after upgrading from framework 4.0 to 4.5.2 in windows 7 environment

Hi All,
BackGround
I used to connect to database with Encrypt set true in sql connection which helps established encrypted data base connection . I verified that created certificate in order
to provide Encrypted connection to database for client is valid.
Issue :Issue
is un-able to connect to sql sever2008 r2 from vs2013 by enforcing encryption to true.
while trying to test the connection from vs2013 error log getting recorded as well as error notification is getting populated as below .
Step1 :
from Vs2013 trying to connect to sql server 2008 r2
step 2: on Click test Connection . getting below mentioned error notification
Event Viewer Log:<o:p></o:p>
<o:p></o:p>
(Process Id: 7472)
<o:p></o:p>
.Net SqlClient Data Provider:<o:p></o:p>
A connection was successfully established with the server, but then an error
occurred during the login process. (provider: SSL Provider, error: 0 - The
target principal name is incorrect.)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection, Action`1 wrapCloseInAction)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)<o:p></o:p>
   at
System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle,
SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean
callerHasConnectionLock)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean
canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte
flushMode, Boolean canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec,
FeatureExtension requestedFeatures, SessionData recoverySessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential
credential, TimeoutTimer timeout)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer
timeout, SqlConnectionString connectionOptions, SqlCredential credential,
String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, SqlCredential credential,
Object providerInfo, String newPassword, SecureString newSecurePassword,
Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions,
SessionData reconnectSessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo,
DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions
userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool
pool, DbConnection owningObject, DbConnectionOptions options,
DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate,
Boolean onlyOneCheckConnection, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection
owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions
userOptions, DbConnectionInternal oldConnection, DbConnectionInternal&
connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection
outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1
retry, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)<o:p></o:p>
   at System.Data.SqlClient.SqlConnection.Open()<o:p></o:p>
Inner Exception:<o:p></o:p>
:<o:p></o:p>
The target principal name is incorrect

The target principal name is incorrect
Hi Rahul.U,
Are you able to connect to SQL Server successfully from SQL Server Management Studio (SSMS) when enforcing encryption?
According to above error message, it could be caused by the inappropriate server name or incorrect TrustServerCertificate configuration in the connection string from Visual Studio. There are some proposals for you troubleshooting this error.
1. Make sure that you connect to the SQL server using the fully qualified domain name (FQDN).
2. When connecting to a SQL Server instance with a valid certificate, please add the
TrustServerCertificate
parameter and set it to true in the connection string. For more details, please review this
article.
However, if you can successfully connect to SQL Server via SSMS, but still fail to connect to SQL Server from Visual Studio, I would like to recommend you post the question in the .Net Framework forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=netdevelopment . It is appropriate and more experts will assist you.
There are similar articles about error “The target principal name is incorrect” for your reference.
http://serverfault.com/questions/458935/aws-rds-sql-server-ssl-connection-the-target-principal-name-is-incorrect
http://www.derekseaman.com/2013/09/sql-2012-failover-cluster-pt-12-kerberos-n.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Connection failed SQL Server 2008 R2 with Instance Name but with IP connect

Hello,
We have a server where SQL Server 2008 R2 is installed. Now from our local pc we connect to that database. I try to connect that database using instance name but cannot. If I put IP Address in the server name field, then it connect. my other colleague, they
can connect using instance name but I cannot.
How can I resolve this problem? How can I connect using Instance Name?
Please help.

Faisal there are a couple of possibilities for you. Some have been mentioned already. For us to help if you can provide some further information this would be appreciated. In the mean time some things that you can check
If you are able to connect to the instance via Server IP Address then the instance is configured for remote connections and the firewall does allow for remote connections to come through. You can check the SQL Server Configuration Manager on the server to
check what protocols (Named Pipes & TCP/IP are enabled). You can also check that the Browser is running.
What error message do you receive when trying to connect via the ServerName or ServerName\InstanceName remotely?
You could look at creating an entry in your host file with the server name and IP address on you workstation and test this. I am thinking that if a colleague is able to connect remotely via ServerName or ServerName\InstanceName that you potentially have
a caching issue or a DNS issue. Are you able to ping the servername from your workstation and get a valid response from the correct IP address?
I hope this helps.
Thanks
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

Database upgradation from SQL Server 2008 to 2012

Hi Experts,
I am upgrading MSSQL 2008 to MSSQL 2012. This box contains all of the DBs for our Sharepoint installation.
We have identified that we can run the setup wizard to change the database and basically restore a backup from the 2008 database onto the 2012 database running in 2008 compatibility mode. But what should be done about the SharePoint Foundation database running
on the 2008 database?
Help me to resolve the issue.
Regards
Prakash M

Hi Prakash,
Here you are the steps i have used while doing such upgrade:
To Migrate SharePoint DBs from SQL Server to another either same version or to a new version (2008 to 2008 or 2008 to 2012) you can follow the following steps:
Stop all SharePoint and IIS Related Services.
Stop IIS.
Detach all related SQL Server databases.
Configuration database
Central Administration content database
Content databases
Service application databases
Move all database files (.mdf, .ldf, and .ndf) to the new server.
Set up same user permissions on the new SQL server.
Attach your databases to the new SQL Server.
Verify ports in your new SQL server.
Go to your SharePoint server and create your SQL Server Alias.
Start all your SharePoint service
Hope this is helpful
Kind Regards, John Naguib Technical Consultant/Architect MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Upgrade from SQL server developer 2008 R2 to SQL Server developer 2012

Hi,
We have bought 5 licenses of SQL server developer 2012.
This licenses provided us an option to use SQL server 2008 R2. And we have been using 2008 R2 till now.
But now we want to upgrade to SQL server developer 2012 edition
I want to know the process for up-gradation. When I looked at the licensing portal, it says "This product does not require a product key"
My questions are:
1) Should I download the 2012 version from licensing center and pass the downloaded copy to respective team members?
2) Can the team member download the SQL server 2012 developer edition from Microsoft site and install it on their machines?
3) Do we need to first un-install 2008 R2?
4) How the licensing can be managed in cases of products which say "This product does not require a product key.", i.e. how can I make sure that no more than 5 installations are done by the team
Thanks

Hi,
We have bought 5 licenses of SQL server developer 2012.
This licenses provided us an option to use SQL server 2008 R2. And we have been using 2008 R2 till now.
But now we want to upgrade to SQL server developer 2012 edition
I want to know the process for up-gradation. When I looked at the licensing portal, it says "This product does not require a product key"
My questions are:
1) Should I download the 2012 version from licensing center and pass the downloaded copy to respective team members?
2) Can the team member download the SQL server 2012 developer edition from Microsoft site and install it on their machines?
3) Do we need to first un-install 2008 R2?
4) How the licensing can be managed in cases of products which say "This product does not require a product key.", i.e. how can I make sure that no more than 5 installations are done by the team
Thanks
1. Developer edition has license associated with it .And yes you can download it if you have subscription.But please be informed that you cannot use Developer edition in production,its not allowed and illegal.
2.You can upgarde from SQL server 2008 R2 to 2012 developer edition by Inplace upgrade method ,you can also follow side by side approach.For side by side approach you have to get new box ,intall OS,then install SQL server 2012 ,move logins and jobs and move
databases by backup restore.You must see supported upgrades
http://technet.microsoft.com/en-us/library/ms143393(v=sql.110).aspx
3.No not ins any case ,please dont do that
4.Licensing question should best be asked with Microsoft licensing expert.
reg process of upgarde first run upgrade advisor and look for error if any.Then run SQL server 2012 setup and in maintenance section select edition upgrade,other process is same as SQL Server installtion
http://www.mssqltips.com/sqlservertip/2505/version-and-edition-upgrades-with-sql-server-2008-r2/
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Difference between database features - SQL Server 2008 R2 navtive vs SQL Server 2012 with SQL Server 2008 compatibility set?

I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the impact of the upgrade, I am planning to restore / create our application database onto SQL Server 2012 with compatibility level 100 (SQL Server 2008 and
SQL Server 2008 R2).
Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?

Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?
Yes there can be difference and impact there are few features deprecated in SQL Server 2012 you must be aware about that. Please see
Deprecated Database Features in SQL Server 2012
Deprecated SQL Server features in SQL Server 2012
After you migrate database to 2012 please don't move ahead with production unless you have tested your application to new created database
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 Article
MVP

Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1

We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1. Upgrade was successful. Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
Studio are unable to log in via Windows Authentication.
The error they receive is listed below:
Connect not connect to XXXXXXX
Login Failed. The login is from an untrusted domain and cannot be used with Windows Authentication.
(Microsoft SQL Server, Error: 18452)
If we switch to Mixed authentication, users can log in via SQL Server Authentication.
Our security policy prohibits SQL Authentication.
Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?
Thanks.
DJ

Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
Extended Protection is?
Erland Sommarskog, SQL Server MVP, [email protected]

Upgrade to SQL Server 2014

Should there/Would there be any issue/s I might run into with upgrading from SQL Server 2008 to 2014 ?
Or any known issue/s?
Yes, I understand this is project server; however the SQL software was acquired (about time) and we're planning the migration/upgrade for the SQL Server for project server.
Thank you for any and all help/suggestions/ideas
kbwrecker

Further to this, even Project Server 2013 isn't supported on SQL Server 2014 yet:
http://technet.microsoft.com/en-us/library/ee683978(v=office.15).aspx see: "SQL Server 2014 is not yet supported for Project Server 2013."
So previous versions of Project Server wont be supported.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

Similar Messages

Maybe you are looking for