locked
inplace Upgrade from 2008 R2 to 2014 SQL RRS feed

  • Question

  • Hi, I m trying to upgrade SQL server 2008 R2 to 2014 and stuck with it. the error log from bootstrap is not very helpful. Here is the error message, Anyone has come across similar error? Thanks!
    Wednesday, September 21, 2016 8:14 PM

Answers

  • Yeah, I looked at the earlier logs. 1st time it failed due to missing permissions on a replication folder, we fixed those permissions and removed the ghost instance that created (MSSQLSERVER.INACTIVE). we tried again and failed with the above error logs which don't have much useful info. 

      I ll open a ticket probably tomorrow and ping you the tkt #. But I work in EST. 

    Thank you!

    Monday, September 26, 2016 10:53 PM

All replies

  • Hi ,

    The above one dont have much information what is the issue,how ever it looks like the .Netframework 4 is trying to install,incase if you have tried with command line- see any issues with parameters,steps-

    Ngen.exe (Native Image Generator)
    https://msdn.microsoft.com/en-us/library/6t9t5wcf(v=vs.110).aspx

    Also before you upgrade from sql server 2008r2 to sql server 2014- you need to check the pre-requisites like

    >SQL Server 2008 R2 SP2 or later should be exists along with please go through the 

    Hardware and Software Requirements for Installing SQL Server 2014
    https://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx

    once all matches then go for-

    SQL Server 2014 Upgrade Technical Guide
    https://www.ugiss.org/2015/10/28/sql-server-2014-upgrade-technical-guide/

    Also if .Net get corrupted you might be need to repair it  .

    https://www.microsoft.com/en-us/download/details.aspx?id=30135



    Regards, S_NO "_"

    Thursday, September 22, 2016 1:01 AM
  • Posting just fragment of log is not going to help much. Please upload summary.txt file and details.txt file on shared drive and then share the link with me so that I can analyze.

    Did you run SQL Server 2014 upgrade advisor before upgrading. If not then you did blunder

    Did you made sure your SQL Server 2008 r2 was patched to latest Service pack

    What edition of 2008 R2 were you upgrading and to what edition of SQL Server 2014.

    Did you read Hardware and software requirements for SQL Server 2014


    Cheers,

    Shashank

    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

    MVP


    Thursday, September 22, 2016 4:42 AM
  • Hi, Thanks for the replies! We are upgradeing SQL 2008 R2 Enterprise (SP3) to SQL 2014 Enterprise. upgrade advisor worked fine, didn't report any issues. I uploaded the files here, Thank you!

    Here is the summary and Details are : 

    https://drive.google.com/file/d/0B1_jYV5yH4DRQWcxZl9rQjh0V28/view?usp=sharing

    Thursday, September 22, 2016 5:47 PM
  • Some log:

    -----------------------

    (08) 2016-09-21 10:43:17 Slp: Skipping rule NoRebootPackageDownLevel
    (08) 2016-09-21 10:43:17 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (08) 2016-09-21 10:43:17 Slp: Condition "Is the OS version equal or higher than 6.1" did not pass as it returned true and false was expected.

    (08) 2016-09-21 10:43:17 Slp: Rule is not applicable in the current scenario.
    (08) 2016-09-21 10:43:17 Slp: Loading rule: ServerCorePlatformCheck
    (08) 2016-09-21 10:43:17 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetOsInfo
    (08) 2016-09-21 10:43:17 Slp: Rule applied features  : ALL
    (08) 2016-09-21 10:43:17 Slp: ----------------------------------------------------------------------
    (08) 2016-09-21 10:43:17 Slp: Skipping rule ServerCorePlatformCheck
    (08) 2016-09-21 10:43:17 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (08) 2016-09-21 10:43:17 Slp: Condition "IsServerCore" did not pass as it returned false and true was expected.

    (08) 2016-09-21 10:43:17 Slp: Rule is not applicable in the current scenario.
    (08) 2016-09-21 10:43:17 Slp: Loading rule: ServerCore64BitCheck
    (08) 2016-09-21 10:43:17 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetWOW64PlatformCheck
    (08) 2016-09-21 10:43:17 Slp: Rule applied features  : ALL
    (08) 2016-09-21 10:43:17 Slp: ----------------------------------------------------------------------
    (08) 2016-09-21 10:43:17 Slp: Skipping rule ServerCore64BitCheck
    (08) 2016-09-21 10:43:17 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (08) 2016-09-21 10:43:17 Slp: Condition "IsServerCore" did not pass as it returned false and true was expected.

    -----------------------

    IS the OS layer properly validated?


    Santosh Singh

    Friday, September 23, 2016 4:24 PM
  • Hi, Thanks for the replies! We are upgradeing SQL 2008 R2 Enterprise (SP3) to SQL 2014 Enterprise. upgrade advisor worked fine, didn't report any issues. I uploaded the files here, Thank you!

    Here is the summary and Details are : 

    https://drive.google.com/file/d/0B1_jYV5yH4DRQWcxZl9rQjh0V28/view?usp=sharing

    As per Summary.txt. I can see

     The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,REPLICATION. Then, run SQL Server Setup again.

    So basically you should uninstall the previous feature and run the setup again.

    I can also see you have two SSMS client instances and both have different patch level, this can be the cause of failure.

    Product Instance Instance ID Feature Language Edition Version Clustered Configured SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033

    Enterprise Edition 10.53.6220.0 No Yes SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Enterprise Edition 10.53.6220.0 No Yes SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033

    Enterprise Edition 10.53.6000.34 No Yes SQL Server 2008 R2


    Moreover the reason for failure might be in below log file

    C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160921_104309\sql_engine_core_inst_loc_Cpu64_1033_1.log

    Please upload the content again on shared drive.



    Cheers,

    Shashank

    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

    MVP

    Friday, September 23, 2016 4:51 PM
  • Thanks! Yeah, thats interesting. I will take a look into that, also here is the content from the C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160921_104309\sql_engine_core_inst_loc_Cpu64_1033_1.log:

    Appreciate your help! 

    === Verbose logging started: 9/21/2016  10:46:31  Build type: SHIP UNICODE 5.00.9600.00  Calling process: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\SQLServer2014\x64\ScenarioEngine.exe ===
    MSI (c) (60:74) [10:46:31:276]: Resetting cached policy values
    MSI (c) (60:74) [10:46:31:276]: Machine policy value 'Debug' is 0
    MSI (c) (60:74) [10:46:31:276]: ******* RunEngine:
               ******* Product: C:\Microsoft SQL Server 2014\Enterprise\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (c) (60:74) [10:46:31:276]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (60:74) [10:46:31:276]: Grabbed execution mutex.
    MSI (c) (60:74) [10:46:31:276]: Cloaking enabled.
    MSI (c) (60:74) [10:46:31:276]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (60:74) [10:46:31:276]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (1C:38) [10:46:31:292]: Running installation inside multi-package transaction C:\Microsoft SQL Server 2014\Enterprise\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi
    MSI (s) (1C:38) [10:46:31:292]: Grabbed execution mutex.
    MSI (s) (1C:68) [10:46:31:292]: Resetting cached policy values
    MSI (s) (1C:68) [10:46:31:292]: Machine policy value 'Debug' is 0
    MSI (s) (1C:68) [10:46:31:292]: ******* RunEngine:
               ******* Product: C:\Microsoft SQL Server 2014\Enterprise\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (s) (1C:68) [10:46:31:292]: Machine policy value 'TransformsSecure' is 1
    MSI (s) (1C:68) [10:46:31:292]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (1C:68) [10:46:31:292]: Specified instance {D45C3EC4-282E-4798-98C7-E7BF2362F04E} via transform :InstID02.mst;:InstName01.mst is already installed. MSINEWINSTANCE requires a new instance that is not installed.
    MSI (s) (1C:68) [10:46:31:292]: MainEngineThread is returning 1639
    MSI (s) (1C:38) [10:46:31:292]: User policy value 'DisableRollback' is 0
    MSI (s) (1C:38) [10:46:31:292]: Machine policy value 'DisableRollback' is 0
    MSI (s) (1C:38) [10:46:31:292]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (1C:38) [10:46:31:292]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (1C:38) [10:46:31:292]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (1C:38) [10:46:31:292]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (60:74) [10:46:31:292]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (60:74) [10:46:31:292]: MainEngineThread is returning 1639
    === Verbose logging stopped: 9/21/2016  10:46:31 ===

    Friday, September 23, 2016 6:17 PM
  • I am interested in complete log. Please share on shared drive as you did before

    Cheers,

    Shashank

    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

    MVP

    Friday, September 23, 2016 6:23 PM
  • Sure, Here it is: 

     Uploaded doc

    Friday, September 23, 2016 6:38 PM
  • Sure, Here it is: 

     Uploaded doc

    I can see

    Specified instance {D45C3EC4-282E-4798-98C7-E7BF2362F04E} via transform :InstID02.mst;:

    InstName01.mst is already installed. MSINEWINSTANCE requires a new instance that is not

    installed. MSI (s) (1C:68) [10:46:31:292]: MainEngineThread is returning 1639

    I guess as reported by summary.txt file you need to completely uninstall SQL Server 2008 R2 and then install SQL Server 2014. The message says it was trying to upgrade but found out some instance.mst which was already their so cannot proceed.

    You might as well require a manual cleanup

    • 1. Uninstall the existing SQL Server  and all the components from the add remove program.
    • 2. Backup the registry.
    • 3. Delete the following keys using regedit:
      • --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
      • --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
    • 4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
    • 5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
    • 6. Rename all the SQL Server folders in the computer.
    • 7. Reboot the machine.


    Cheers,

    Shashank

    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

    MVP

    Saturday, September 24, 2016 6:30 AM
  • Thank you for the input! This is live production server and we are trying in place upgrade which is not recommended. So unfortunately uninstall is not an option for me. I lll try to open a case with Microsoft if they help us get around the problem. I highly suspect they may not have easy solution as well. Appreciate all the help!
    Saturday, September 24, 2016 12:58 PM
  • Well, D45C3EC4-282E-4798-98C7-E7BF2362F04E GUID is for the product. It looks like there were some components which failed. Did you look at very first failed setup logs and followed steps given there?

    Opening case with Microsoft is a suggested option. If you work during India time then feel free to ping me on facebook/twitter and provide case # to me.


    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog | Team Blog | @Twitter | Facebook
    Author: SQL Server 2012 AlwaysOn - Paperback, Kindle

    Saturday, September 24, 2016 3:18 PM
  • Yeah, I looked at the earlier logs. 1st time it failed due to missing permissions on a replication folder, we fixed those permissions and removed the ghost instance that created (MSSQLSERVER.INACTIVE). we tried again and failed with the above error logs which don't have much useful info. 

      I ll open a ticket probably tomorrow and ping you the tkt #. But I work in EST. 

    Thank you!

    Monday, September 26, 2016 10:53 PM