Home Dashboard Directory Help
Search

Spawned SQL Server 2008 R2 express SP2 installation freezes during ExecuteStandardTimingsWorkflow by Reddappa456


Status: 

Active


44
0
Sign in
to vote
Type: Bug
ID: 761370
Opened: 9/5/2012 9:59:51 PM
Access Restriction: Public
0
Workaround(s)
view
24
User(s) can reproduce this bug

Description

Spawned SQL Server 2008 R2 Express SP2 setup Installation freezes when installing "SQL Server 2008 R2 Express SP2" from another installation package (Install Script custom actions). Log Files are attached for your reference.

Note:- There is no issues when we install "SQL Server 2008 R2 Express SP2" from command prompt or from SQL Server UI. This issue is observed only when "SQL Server 2008 R2 Express SP2" setup is launched as part of another products installation. This issue is not observed with SP1 (SQL Server 2008 R2 Express SP1) and also not observed with SQL Server 2005 Express SP3/SP4.

Details
Sign in to post a comment.
Posted by Dudi6 on 6/12/2014 at 2:24 AM
This issue still remained in SQL Express 2014.
Are there any solution?
Posted by Sethu Srinivasan on 4/8/2014 at 4:41 PM
Let us know if you see this issue in SQL 2014

you can create a SQL 2014 Virtual machine on Windows Azure - http://azure.microsoft.com/en-us/pricing/free-trial/
or
You can download SQL 2014 from http://technet.microsoft.com/en-US/evalcenter/dn205290

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Posted by demp on 10/7/2013 at 8:40 AM
My case: msi installer created with WiX. SQL Server Express 2008 R2 SP1 installer was started from within my installer via C# custom action. Custom action was starting the sql server installer via the command line.
And it was working fine in Windows Server 2008, Windows 7, even in Windows XP. However, in Windows 8 it gave out about compatibility.

I updated the installer to SQL Server 2008 R2 SP2. That's when it started to get stuck at ExecuteStahdardTimingsWorkflow with no progress.

Looking at %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log revealed the piece below which gave me a clue that it cannot top msiexec.exe (Windows Installer) service.

What helped (a little bit brutal): added piece of code to the custom action that searched for Windows Installer service process id and explicitly killed it with taskkill /F /PID xxxxx (stopping didn't help!)

    2013-10-07 13:17:44 Slp: Completed Action: InitializeMsiAction, returned True
    2013-10-07 13:17:44 Slp: ----------------------------------------------------------------------
    2013-10-07 13:17:44 Slp: Running Action: MsiTimingAction
    2013-10-07 13:17:44 Slp: ----------------------------------------------------------------------
    2013-10-07 13:17:44 Slp: Running Action: Install_SqlSupport_Cpu64_Action
    2013-10-07 13:17:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-10-07 13:17:44 Slp: Sco: Attempting to open registry subkey
    2013-10-07 13:17:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
    2013-10-07 13:17:44 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
    2013-10-07 13:17:44 Slp: Sco: Returning service status Running
    2013-10-07 13:17:49 Slp: Sco: Returning service status Running
    2013-10-07 13:17:54 Slp: Sco: Returning service status Running
    ....
    2013-10-07 13:20:39 Slp: Sco: Returning service status Running
    2013-10-07 13:20:44 Slp: Sco: Returning service status Running
Posted by Fredrik Vestin on 12/11/2012 at 3:48 AM
I was made aware of another report that relates to the same problem. I can only encourage everyone to vote on that as well since the MS standpoint seems to be "Won't fix".
http://connect.microsoft.com/SQLServer/feedback/details/741476/sql-server-2012-express-setup-issue

For Microsoft: You claim that it is not supported to run spawn an the SQL installer from tools like InstallShield in the way described here. This worked fine up to SQL Server 2008 R2 SP1 but stopped working with SQL Server 2008 R2 SP2. This means that the SQL installer was altered from 2008 R2 SP1 to SP2 for some reason. Why was this change made? From a technical standpoint installing SP2 does not seem significantly different compared to installing SP1. Please explain the reason for this change and consider to update the installer to support this in future updates. In practice you are now preventing developers from distributing SQL Express with their installation, which cannot be what you intended. As the same problem persist in SQL Server 2012 (both RTM and SP1) we cannot distribute anything newer than SQL Server 2008 R2 SP1.
Posted by Fredrik Vestin on 11/16/2012 at 6:55 AM
I have discussed this with InstallShield support and the setup.exe that is running does not rely on the Windows installer service. Of course the SQL Server installation itself does so it will trigger the Windows installer service but the setup.exe will not, according to InstallShield support. If this indeed is the problem why is it that all versions of SQL Server Express 2005 up to SQL Server 008 R2 SP1 was working fine and this just surfaced with 2008 R2 SP2 and 2012?
Posted by Fredrik Vestin on 11/16/2012 at 5:59 AM
I can also confirm that the same problem exist with SQL Server 2012. Log file says:

The Detail_ComponentUpdate log file says:

(01) 2012-11-16 14:14:46 Slp: Running Action: MsiTimingAction
(01) 2012-11-16 14:14:46 Slp: ----------------------------------------------------------------------
(01) 2012-11-16 14:14:46 Slp: Running Action: Install_VC10Redist_Cpu64_Action
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to open registry subkey
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\10.0
(01) 2012-11-16 14:14:46 Slp: Checkpoint: PREINSTALL_VC10REDIST_CPU64_ACTION
(01) 2012-11-16 14:14:46 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to open SC Manager
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2012-11-16 14:14:46 Slp: Invoking QueryServiceStatus Win32 API
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2012-11-16 14:14:46 Slp: Sco: Attempting to close SC Manager
(01) 2012-11-16 14:14:51 Slp: Sco: Attempting to open SC Manager
(01) 2012-11-16 14:14:51 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2012-11-16 14:14:51 Slp: Invoking QueryServiceStatus Win32 API
(01) 2012-11-16 14:14:51 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2012-11-16 14:14:51 Slp: Sco: Attempting to close SC Manager
The lines between "Attempting to open SC Manager" and "Attempting to close SC Manager" repeats indefinitely.

As with SQL Server 2008 R2 SP2 the installation works fine when launched from the command prompt with the exact same parameters. The Detail_ComponentUpdate log now says:

(01) 2012-11-16 14:37:22 Slp: Running Action: MsiTimingAction
(01) 2012-11-16 14:37:22 Slp: ----------------------------------------------------------------------
(01) 2012-11-16 14:37:22 Slp: Running Action: Install_VC10Redist_Cpu64_Action
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to open registry subkey
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\10.0
(01) 2012-11-16 14:37:22 Slp: Checkpoint: PREINSTALL_VC10REDIST_CPU64_ACTION
(01) 2012-11-16 14:37:22 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to open SC Manager
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2012-11-16 14:37:22 Slp: Invoking QueryServiceStatus Win32 API
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2012-11-16 14:37:22 Slp: Sco: Attempting to close SC Manager
(01) 2012-11-16 14:37:22 Slp: Target package: "c:\dba95f8ffd0189c8a292d3e1\redist\VisualStudioShell\VC10SP1\x64\vc_red.msi"
(01) 2012-11-16 14:37:27 Slp: InstallPackage: MsiInstallProduct returned the result code 0.
(01) 2012-11-16 14:37:27 Slp: RunMsiCore succeeded.

Please also see detailed information at:
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/53181cba-74ac-482a-87ef-d0c70b121b7c/
Posted by Fredrik Vestin on 11/15/2012 at 11:06 PM
Is this really not supported, e.g spawning the sql server install from installshield?. It works fine with sp1 so something has changed with the sql installer. I will report this to installshield as they claim to have a very close collab with ms and provide prerequisite packages with sql server ready to be added to installarion projects.
Posted by Venkat9719209 on 10/28/2012 at 11:07 PM
This issue is pressent in SQL Server 2008R2 SP2 version and NOT in SP1. However the problem is, even if we ship our product with SQL Server 2008R2 SP1, if the target user PC is having SP2 version already (or installed after installing our product) same issue can be observed.
This issue can be observed even during removal of database instance (Goes for infinite loop). If end user PC is having SQL Server 2008R2 SP2, during un-installation of your product you can not delete the database instance. I can't understand why SQL installer has to check for prerequisites and try to shutdown the windows installer for removing just a database instance.
Currently this issue is not observed in SQL Server 2008 SP3 which is the latest service pack version for SQL Server 2008. But I am not sure whether Microsoft relase SP4 for SQL Server 2008 with this issue. Can someone from Microsoft let us know whether you fix this issue or introduce this behavior(Bug) in future versions also?
Posted by Reddappa456 on 10/13/2012 at 2:26 AM
Unable to Remove and create instance of "SQL Server 2008 R2 Express ", once we upgraded from SQL Server Express 2008 R2 SP1 to SP2.

Note:- The following issues observed only with "SQL Server 2008 R2 SP2 express " edition,
         There is no issues With lower express editions like "SQL Server 2005(SP1, SP2, SP3 and SP4) , SQL Server 2008(SP1, SP2) , SQL Server 2008 R2 SP1 "

Scenario 1:-
1. Create instance(say ex:- SQL_Instance) of "SQL Server 2008 R2 express SP1" from InstallShield package.
2. Upgrade "SQL Server 2008 R2 express " from SP1 to SP2 From Command prompt with administrator privileges.
3. Now Un-Install / Remove Instance(which is created in step(1)) from Installshield package.

Result:- Instance un-installation is freezes.

Scenario 2:-
1. Install SQL Server 2008 R2 Express SP2 from command prompt.
2. Create instance(say ex:- SQL_Instance) of "SQL Server 2008 R2 express SP1" from InstallShield package.

Result:- Instance installation \ Creation is freezes.

Note:- Issues are not observed in the lower express editions like "SQL Server 2005(SP1, SP2, SP3 and SP4) , SQL Server 2008(SP1, SP2) , SQL Server 2008 R2 SP1 ".




Posted by bhalperin on 10/9/2012 at 3:48 PM
Does this bug also exist for the SQL Server 2012 Express installer?
Posted by Microsoft on 9/17/2012 at 9:45 AM
Hi Reddappa, thanks for taking the time to report this issue.

In this situation it appears that SQL Express setup is being run from an InstallShield package. This scenario is not currently supported since InstallShield holds some Windows Installer handles and SQL Setup cannot restart the WI service and proceed so it appears to be hanged.

thanks,
[SQL Server Team]
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
SQL_Server_2008R2_SP2_Express_Error_Logs.zip 9/5/2012 8.92 MB