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

Similar Messages

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

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

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 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

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

Upgrade to Windows Server 2008 installation fails (reports Services to uninstall but they are not installed)

I am upgrading a Windows Server 2003 to 2008.
When I run the install it completes the Compability check and reports that Sharepoint Services and WSUS are installed. They are not installed and are not running Services either. I have attempted to remove Registry keys for these but this does not resolve
my issue.
Control Panel, Add/Remove does not report these as installed either.
How do I get the 2008 install to continue and ignore these OR how do I "truly" get these "uninstalled" if there is nothing I can do to find out what is reporting that they are installed?

SBS 2003 does contain these feature by default. Is this a small business server OS? If so I'd try them over here.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=sbsserver&filter=alltypes&sort=lastpostdesc
This one may also help.
Transition from Small Business Server to Standard Windows Server
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

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

Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

I've been searching for HOURS how to resolve this issue:
I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
======================================================================================
Rule Check Result
Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
=====================================================================================
This is the Configuration Report issue:
Microsoft SQL Server 2014 - System Configuration Check Report
UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
KJRTMUpgradeBlockRule
Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack. Failed The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
====================================================================================
I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
out!!!
Thanks.

Hi again
This is the scenario:
-I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
-As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
resolved immediately with the Windows Update service.
-Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
Now we are on 12.0.2000.8
Thanks anyway and all of you for your interest!!!

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]

CFMXE 7.x and SQL Server 2008

Hello - a client recently upgraded to SQL Server 2008 and we can no longer connect from CFMXE 7.x.
I have asked them to go through the steps outlined here <http://blog.mxunit.org/2009/02/connecting-sql-server-2008-to.html> but errors persist. The DSN is defined using the standard SQL Server driver - is there an updated one that is required for 2008?
The error I have now is Cannot open database "database" requested by the login. The login failed.
Caveats - I have no access to the database server.
Suggestions?

I know we have a couple of CF 7 servers that are connecting using the built in sql drivers to sql 2008 without issue, so out of the box it should work.
I would suggest seeing if dynamic ports are enabled on the sql server, which would maybe cause a problem if there is a firewall involved and perhaps with the CF drivers.
To ensure you stay on port 1433, I think in CF 7 you can specify additional connection params in the DSN under the advanced dialog. I don't have a machine in front of me. I'd have to try it out.
Alternatelly you could try the "other" driver for the DSN, and use a JDBC connection string to connect and specify the port. If you need a better example, email me and I'll send over an example.
Our 2005 - 2008 Sql upgrades have been very smooth with regards to the DSN, and we didn't have to update anything aside from the server ip, so it should work.
Byron Mann
[email protected]
[email protected]
Software Architect
hosting.com | hostmysite.com
http://www.hostmysite.com/?utm_source=bb

Error while installing sql server 2008 r2 on win7

what can i do? i had .net framework 3.5 sp1
details is:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Users\seven\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException:
Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
   at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
   at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
   at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
   --- End of inner exception stack trace ---
   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
   at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
   at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
   at System.Configuration.SettingsBase.get_Item(String propertyName)
   at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
   at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
   at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
LandingPage
    Assembly Version: 10.0.0.0
    Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
    CodeBase: file:///d:/1ce672d6bc649fad4aefc7b7a6/x64/LandingPage.exe
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.SqlServer.Configuration.Sco
    Assembly Version: 10.0.0.0
    Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
    CodeBase: file:///d:/1ce672d6bc649fad4aefc7b7a6/x64/Microsoft.SqlServer.Configuration.Sco.DLL
Microsoft.SqlServer.Chainer.Infrastructure
    Assembly Version: 10.0.0.0
    Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
    CodeBase: file:///d:/1ce672d6bc649fad4aefc7b7a6/x64/Microsoft.SqlServer.Chainer.Infrastructure.DLL
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.Management.Controls
    Assembly Version: 10.0.0.0
    Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
    CodeBase: file:///d:/1ce672d6bc649fad4aefc7b7a6/x64/Microsoft.SqlServer.Management.Controls.DLL
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi mahdy,
According to the error message, this issue is probably caused by a LandingPage.exe error. It couldn't bind to System assembly. The issue occurs while reading user.config
in the configuration file, there is code like this <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >. In this issue, it seems the application tried
to call the LandingPage.exe version 4.0.0.0, and this version is not existing in the machine. That should be the cause. So would you please kindly to check if LandingPage.exe 4.0.0.0 is existing?
As a workaround, Please try deleting the following sub folder to see if this will work:
Driver:\users\(my profile)\AppData\Local\Microsoft_Corporation
If you can't see AppData folder, please using following steps to show hidden files:
   1. Open an explorer window, hit "ALT-T" choose
Folder Options then go to the view tab.
   2. Turn on
Show hidden files, folders or drives and disable Hide protected Operating System files (recommended)
Please read the following blog:
http://blogs.msdn.com/b/vsnetsetup/archive/2009/10/29/sql-server-2008-setup-fails-with-a-microsoft-net-framework-exception.aspx
If there are any other questions, please feel free to ask.
Thanks
Grace
Please kindly mark the answer if it is a workaround. Thanks a lot *^_^*

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

Upgrade to SQL Server 2008 R2 fails

Similar Messages

Maybe you are looking for