Question

dilbert2015 on Tue, 07 Oct 2014 21:17:08


Hi, installing SQL Express 2008 R2 SP2 onto Windows Server 2012 R2.   I had previously removed SQL Express 2012 due to failed install due to incompatibility with our SAN.   (I had uninstalled it via Programs & Features, and also by following Shanky's tips. http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx).

This is what's in Detail log: 

014-10-07 13:12:00 Slp: Parameter 5 : SqlEngineConfigAction_install_confignonrc

2014-10-07 13:12:00 Slp: Parameter 6 : 0x50806C41

014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:02 Slp: Cannot find service {0}.

The SqlEngineConfigAction_install_confignonrc part is what is in the background before the Cannot find service {0}. Parameter name: SQLWriter pops up.

And in Event Viewer:

Log Name:      Application
Source:        Microsoft-Windows-RestartManager
Date:          10/7/2014 1:11:48 PM
Event ID:      10010
Task Category: None
Level:         Warning
Keywords:     
User:          SYSTEM
Computer:     
Description:
Application 'C:\31f53f2e988a36f2c31e\x64\setup100.exe' (pid 688) cannot be restarted - Application SID does not match Conductor SID..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
    <EventID>10010</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-07T20:11:48.532980400Z" />
    <EventRecordID>4538</EventRecordID>
    <Correlation />
    <Execution ProcessID="732" ThreadID="2548" />
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
      <RmSessionId>0</RmSessionId>
      <Pid>688</Pid>
      <FullPath>C:\31f53f2e988a36f2c31e\x64\setup100.exe</FullPath>
      <DisplayName>Managed SQL Server Installer</DisplayName>
      <AppVersion>0</AppVersion>
      <AppType>5</AppType>
      <TSSessionId>2</TSSessionId>
      <Status>67108865</Status>
      <Reason>1</Reason>
    </RmUnsupportedRestartEvent>
  </UserData>
</Event>

Found one article saying you can get this if previous version not fully removed, and to do a repair of the previous version, but as I said I uninstalled it and followed all steps for cleanup, so nothing to repair. 







Sponsored



Replies

Shanky_621 on Tue, 07 Oct 2014 22:20:15


Application 'C:\31f53f2e988a36f2c31e\x64\setup100.exe' (pid 688) cannot be restarted - Application SID does not match Conductor SID..

Event Xml:

Hi,

With search on net I found out that

the error ”Application SID does not match Conductor SID” will be generated whenever the user account the service is being run under does not match the user account used to launch the setup instance. The term “Conductor” refers to the MSI setup engine. It also appears that if the setup is executed with elevated permissions (Run As Administrator), then the SID check is bypassed.

So again did you right click on setup file and selected run as administrator.

Above error is unclear. Can you please again upload summary file and Details.txt file on shared location for analysis. This link would help you locate it. Please share the link here.

Did you removed registry keys as a part of uninstallation? I am sure I mentioned to use reg key removal method only when removing from add remove program gave error. I also mentioned that removing reg parameters can cause inconsistency hope you read that. Did you took registry backup before deleting reg parameters

dilbert2015 on Tue, 07 Oct 2014 22:43:45


I've uploaded the files, thanks.

I did remove via Add/Remove with no errors (just warnings of other sql component dependencies that must be installed first/or along with it), but if after this, it still leaves those entries in registry and program files, are you saying I should leave them?  

I have a backup of entire registry but it is from right after my failed SQL 2012 install the other day, before deleting anything from the registry.

I'm pretty sure I did do Run as Admin (I generally do as a habit for installs), but to be safe I will turn off UAC completely for now so that won't not an issue when I run it again.

Shanky_621 on Tue, 07 Oct 2014 22:48:15


I asked it to share it here :) Just in case more users want to have a look

https://onedrive.live.com/?id=F68DBF79A213C85A!106&cid=f68dbf79a213c85a&authkey=!Ag4RbPcwUY4Q-yw


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


Shanky_621 on Tue, 07 Oct 2014 23:17:49


Hi,

Below was in details.txt file

Attempting to merge service security settings for service MSSQLServerADHelper100
2014-10-07 13:12:00 Slp: Sco: Attempting to persist service security settings for service MSSQLServerADHelper100
2014-10-07 13:12:00 SQLEngine: --SqlEngineSetupPrivate: Applying SDDL to Service 'SQLWriter' SDDL: D:(A;NP;0x00020011;;;S-1-5-21-2578389462-845333541-2326229951-1008)
2014-10-07 13:12:00 Slp: Sco: Failed to open service handle for service SQLWriter
2014-10-07 13:12:00 SQLEngine: --SqlEngineSetupPrivate: Cannot find serivce SQLWriter.

2014-10-07 13:12:00 Slp: Message: Cannot find service {0}.
2014-10-07 13:12:00 Slp: Parameter name: SQLWriter.
2014-10-07 13:12:00 Slp: Watson Bucket 1 

There are two probable causes

1. Installation media is corrupt and missing some files may support files related to SQLwriter so it failed. Please dowload media again extract it and run setup again. IMO I dont think this as probable cause

2. This one I consider most probable cause . This support article says that

When an instance of the x86-based version of Microsoft SQL Server 2008 and an instance of the x64-based version of SQL Server 2008 are installed on an x64-based computer, and you try to install a new instance of one version after you uninstall the instance of the other version, the installation fails. For example, the installation fails if you try to install a new instance of the x64-based version after you uninstall the x86-based version.

Reason

This problem occurs because the SQL Server Active Directory Helper Service is removed when you uninstall any instance of SQL Server 2008. On an x64-based computer, both 32-bit instances and 64-bit instances share the SQL Server Active Directory Helper service. However, a separate reference count of the service is maintained for each platform. Therefore, when you uninstall the last instance of either platform, the SQL Server Active Directory Helper service is deleted.

If multiple instances of a single platform are installed, this problem does not occur.

SOLUTION:

To work around this problem, repair the installation of the remaining instance of SQL Server 2008. When you repair the installation, the SQL Server Active Directory Helper Service is restored.

For more information about how to repair an installation of SQL Server 2008, visit the following Microsoft Developer Network (MSDN) Web site:http://technet.microsoft.com/en-us/library/cc646006%28v=sql.105%29.aspx


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


dilbert2015 on Wed, 08 Oct 2014 15:00:04


Thanks Shanky, but I saw that "repair" article and mentioned it in last paragraph of my first post.  But you can't repair something you uninstalled w/Add/Remove and deleted it's program files/registry entries.  If you know a way, let me know. 

When I go to the link you gave, all it does is take me to my own Onedrive page with those 2 files.  I see nothing on the page asking me to share anything.    At any rate, I removed my personal info from the files and re-uploaded them, but to share with others here (if that's what you're asking) you'd have to tell me how.  I only know how to share with an email address so I shared with yours.



Shanky_621 on Wed, 08 Oct 2014 15:10:40



When I go to the link you gave, all it does is take me to my own Onedrive page with those 2 files.  I see nothing on the page asking me to share anything.    At any rate, I removed my personal info from the files and re-uploaded them, but to share with others here (if that's what you're asking) you'd have to tell me how.  I only know how to share with an email address so I shared with yours.



One drive location I posted was not for you but for other helpers on forum to see the message and give valuabe suggestion.

Did you read whole article (about repair) patiently. Did you run the setup again ,then on window which popped up clicked on maintenace and then it would guide you further how to repair ?

dilbert2015 on Thu, 09 Oct 2014 15:25:06


I did the repair of the previous product I had installed, and reinstalled 2008 Express R2 SP2 and I'm back to the "Could not find the Database Engine startup handle".  And yes, I am doing "Run as Administrator".

I think one problem is that I had tried installing so many versions of Express (first Express 2012, then when finding out it was incompatible with our SAN, I either installed, or just launched install but Canceled out before the copying occurred, at least 2 or 3 different versions of 2008 Express, after I kept discovering so many versions of 2008 online)     And from what I've seen,even launching the install but Canceling out without proceeding, it will have already created folders, reg entries, etc.   

I do see several groups in User Manager that are for SQL.   Your document on uninstall didn't address that.  Perhaps these should be deleted  as well before installing?



Shanky_621 on Thu, 09 Oct 2014 16:02:33


So did you selected SQL Server account as Local system while installing setup? This was the main cause for the error.

Again what does most recent errorlog sayfrom below location

C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log ?

dilbert2015 on Thu, 09 Oct 2014 17:49:56


Here is the ERRORLOG file from C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log.  At the bottom I am seeing the error you said before was a SAN issue.  I had hoped that issue was only with SQL 2012, but it appears it is even with 2008?

If that is still the issue, I'm trying to understand if by the articles, if the SAN conflict is an OS issue or an SQL issue?   In other words, is it because the OS is Server 2012?   Or would this still occur if I install SQL 2008 on Server 2008 R2?    I don't know that they will be willing to upgrade the SAN, and I don't really want to fool with a .VHD (virtual disk) as a workaround speaks of.

If you're asking if I did this from your article:  select startup account for Database Engine services as NT Authority\SYSTEM  , I don't recall what I did this last time.  I was doing that the last few days, but I think I didn't switch it to that once, just to see if I would have success.  I don't know if that was this last time or not when I switched it.  Is there anywhere I can check that after the fact?

014-10-08 12:53:09.84 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
 Jun 28 2012 08:36:30
 Copyright (c) Microsoft Corporation
 Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2014-10-08 12:53:09.84 Server      (c) Microsoft Corporation.
2014-10-08 12:53:09.84 Server      All rights reserved.
2014-10-08 12:53:09.84 Server      Server process ID is 2640.
2014-10-08 12:53:09.84 Server      System Manufacturer: 'IBM', System Model: 'IBM System x -[7870AC1]-'.
2014-10-08 12:53:09.84 Server      Authentication mode is WINDOWS-ONLY.
2014-10-08 12:53:09.84 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-10-08 12:53:09.84 Server      This instance of SQL Server last reported using a process ID of 2848 at 10/8/2014 10:56:44 AM (local) 10/8/2014 5:56:44 PM (UTC). This is an informational message only; no user action is required.
2014-10-08 12:53:09.84 Server      Registry startup parameters:
  -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
  -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
  -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-10-08 12:53:09.84 Server      Command Line Startup Parameters:
  -m SqlSetup
  -f
  -Q
  -q SQL_Latin1_General_CP1_CI_AS
  -T 4022
  -T 4010
  -T 3659
  -T 3610
  -T 902
  -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf
  -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf
2014-10-08 12:53:09.86 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-10-08 12:53:09.86 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-10-08 12:53:09.86 Server      Detected 16 CPUs. This is an informational message; no user action is required.
2014-10-08 12:53:10.00 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-10-08 12:53:10.01 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2014-10-08 12:53:10.01 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2014-10-08 12:53:10.03 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-10-08 12:53:10.05 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
2014-10-08 12:53:10.06 spid7s      Warning ******************
2014-10-08 12:53:10.06 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-10-08 12:53:10.06 spid7s      Starting up database 'master'.
2014-10-08 12:53:10.08 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.08 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.


Shanky_621 on Thu, 09 Oct 2014 18:28:03


Again This is not directly related to SQL Server. What is happening here is SQL server is looking for sector size 4096 ( 4K size) but it finds size to be (2048 K) that is why iy is not able to initialize. More than that I dont have idea did you spoke to SAN provider about this error.

What is OS version and edition is it patched to latest SP ?

Please read This support article it has update to improve SQL Server compatibility with advance format disks.Again I am sure nothing can be done from SQL Server side its OS or storage that needs to be tweaked.

dilbert2015 on Thu, 09 Oct 2014 20:38:08


The update you link to says it's only for Server 2008/Win7.

I noted in previous post that OS is Server 2012 R2.   No SP's exist for it yet.

I just noticed here https://social.technet.microsoft.com/Forums/ja-JP/07d6f2bc-b7c3-480c-8779-71bcff81d9ce/sql-server-2012-enterprise-cluster-setup-fail-could-not-find-the-database-engine-startup-handle?forum=sqlsetupandupgrade, that in the mentioned alert they are blaming the SQL error as actually based on conflict between the OS (2012) and older Compellent Storage Center software, so I will update my SAN admin on the situation to see what he can do.

Thanks.