I am running a major upgrade to an installed product. The product installs files to SQL server's binn folder for provision of extended stored procedures.
The install and upgrade work well until I try to upgrade whilst SQL server has my files loaded. The upgrade presents a dialog of applications needed to be closed down, SQL Server is the one and only entry. I select 'DO NOT STOP APPLICATION' choice and try to continue. Despite this selection, SQL Server is stopped and consequently the SQL scripts I have chosen to run during install fail to run because of no connection to the SQL Server !
I did have an issue with the product uninstall The same files were in use and SQL Server was required to be stopped. I marked their component as permanent and manually added them to the RemoveFile table. Then the uninstall ceased reporting 'SQL Server required to stop' and successfully removed product and files OK.
However, I think RESTART MANAGER may be testing differently during the upgrade/installation.
Does any one know why SQL Server would be shut down even when I said 'don't' ? I would expect it to re-display the dialog and mither until I did shut it down.
I am wondering if any other files are 'in use' and would be grateful if any one could provide an example of how to find out if a file is in use from InstallScript,during execution.
The install and upgrade work well until I try to upgrade whilst SQL server has my files loaded. The upgrade presents a dialog of applications needed to be closed down, SQL Server is the one and only entry. I select 'DO NOT STOP APPLICATION' choice and try to continue. Despite this selection, SQL Server is stopped and consequently the SQL scripts I have chosen to run during install fail to run because of no connection to the SQL Server !
I did have an issue with the product uninstall The same files were in use and SQL Server was required to be stopped. I marked their component as permanent and manually added them to the RemoveFile table. Then the uninstall ceased reporting 'SQL Server required to stop' and successfully removed product and files OK.
However, I think RESTART MANAGER may be testing differently during the upgrade/installation.
Does any one know why SQL Server would be shut down even when I said 'don't' ? I would expect it to re-display the dialog and mither until I did shut it down.
I am wondering if any other files are 'in use' and would be grateful if any one could provide an example of how to find out if a file is in use from InstallScript,during execution.