I am working with an Installscript Project and i have a few features that the user can install. When the user selects to install both SQL Server Express 2008 and a webclient application, DISM is failing.
SQL install runs first and installs with no issues, the Webclient installs second and first uses DISM to enable my required IIS components. The problem is that it seems like the SQL install has something open that is causing the DISM app to fail. I look in the log file and i see multiple lines stating "DISM Manager: PID=4000 Failed to create the image session process. A process is already servicing the image. - CDISMManager::CreateImageSession(hr:0x800700b7)"
If i omit installing the SQL server then the DISM tool works as it should with no issues at all. I have not been able so far to figure out what is causing the failure with SQL..
Is this a pure InstallScript project or a InstallScript MSI project? The behavior you report sounds suspiciously like the latter, where running SQL Server Express 2008 R2 will drop the MSI handle after it performs its own checks for supported operating system. I cannot say for sure though if this is the issue you are encountering.
Another thing I would try myself is enabling the UI for the install of SQL Server 2008 by removing the /Q parameter and see if the install is somehow reporting that it is complete too soon.
What do the logs from SQL Server report?
Related
I already had SQL Server 2019. After upgrading my Windows 10 to latest October Update, I found my SQL Server does not have latest service packs.
I downloaded latest service pack CU8 from Microsoft and ran it. After initializing set up, I get error
Attempted to perform an unauthorized operation
Many research and no luck even in SO.
Please advise.
https://www.microsoft.com/en-us/edge/business/download
Please get the offline installer for latest Microsoft Edge (Chromium) on above link.
Once you have it, run Edge installer and then try to run SQL Update again.
This worked. I ran the latest Edge standalone install and it unblocked the MSSQL patch.
I also confirm that it works. Thanks
https://www.microsoft.com/en-us/edge/business/download
I can confirm this fixes the issue when trying to install SQL 2014 Express Advanced on Windows 10 with H2 update installed.
I had the same error, and installing the standalone Microsoft Edge fixes the error.
After reviewing the logs and digging into windows registry and security, I found the problem was "Microsoft Edge" registry key. Somehow it is read-only for administrator and I figured it out I need to use SYSTEM account to apply the service pack.
Finally I found I can do that using an executable in SysInternals package which is famous for doing weird things in Windows.
This is what I did to apply the service pack.
Run Cmd or PowerShell as Administrator
Go to SysInternals and make sure you have the PsExec64.exe there
Run below command:
.\PsExec64.exe -sid "D:\Downloads\SQLServer2019-KB4577194-x64.exe"
This way you will execute the service pack using SYSTEM account which has highest privilege.
Service pack installed successfully!
I work with Microsoft Access 2016 with a SQL Server 2008 R2 backend. I have used SQL Server Management Studio to create some SSIS package for quick copying of data (right-click DB -> Tasks -> Import/Export).
I was able to create a button in Access to kick off the SSIS package successfully using VBA. I use the Shell function to run the following command:
"C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\DTExec.exe" /F "\\MyPath\MySSISPackage.dtsx". This works on my machine because I'm running my particular instance of DTExec.exe to execute the SSIS package.
I need to set up users' Win10 64-bit computers now so that this process will work for them as well. I don't know if DTExec was installed when I installed SSMS or my local SQL Server Express Edition DB, but the user doesn't need either of these programs. What is the bare minimum I need to install on the users' computers for it to work for them also?
I've done a lot of googling but either the scenario didn't quite fit mine, or I just wasn't understanding what they were talking about. The users will have Microsoft Access only as a start.
Links to download locations would be extra appreciated!
Thanks!
For running SSIS packages in a production environment you must install and license SQL Server. A user who only has Microsoft Access installed cannot run SSIS packages.
You can install and run SSIS packages on your SQL Server (Standard Edition or higher), but not on your clients' PCs.
Once you have credentials all sorted out with DBA team. At min you will need read (select permission) on desired database(s) . Build your ssis in VS2017 locally and test. It will run great I'm sure. And when your ready to deploy you can use steps below.
Steps below outline package deployment mode.
I am trying to install MS SQL SERVER 2016 with SQL Server R Services using web installer and command line.
I am doing this based on this article https://msdn.microsoft.com/en-us/library/mt695943.aspx
Using same web installer, but not command line works perfectly. All desired features are there.
Problem is that command line installation installs only SQLEngine and Replication features.
Logs investigation does not help much. It seems that proper files have not been downloaded and this is the reason why they are missing
My command line is:
SQLServer2016-SSEI-Expr.exe /ConfigurationFile=C:\temp\configuration.ini /IACCEPTSQLSERVERLICENSETERMS /MediaPath=C:\SQLSetup /ENU
And the configuration file content is
[OPTIONS]
Action=Install
INSTANCENAME=MSSQL2016
FEATURES=SQL,AdvancedAnalytics
IACCEPTROPENLICENSETERMS
SECURITYMODE=SQL
SQLSYSADMINACCOUNTS="<username>"
SAPWD="%password%"
What am I doing wrong?
Update: Logs: https://dl.dropboxusercontent.com/u/3028367/20161005_093914.zip
Update 2: I think I have found the reason for missing files
When I run SQLServer2016-SSEI-Expr.exe /? I get this out put:
Optional settings for basic install
==================================
D:\Downloads\SQLServer2016-SSEI-Expr.exe [/ConfigurationFile=C:\Configuration.ini] [/IAcceptSqlServerLicenseTerms] [/Med
iaPath=C:\SqlServer2016Setup] [/ENU]
ConfigurationFile Specifies the ConfigurationFile to use.
IAcceptSqlServerLicenseTerms Required to acknowledge acceptance of the license terms.
MediaPath Location where SQL Server setup media will be downloaded and extracted to.
ENU Use this parameter to install the English version of SQL Server on a localized operating
system.
"Basic!" I need "custom" It is available with the same installer if I use UI
It seems your INI file asks SQLServer to install only few features like SQLEngine and analytics.
when you specify
FEATURES=SQL,Tools
SQL will install..
. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, SQL Server Data Tools, and other shared components
when you specify
FEATURES=SQLENGINE,REPLICATION,FULLTEXT,CONN,IS,BC,SDK,SSMS,ADV_SSMS,OCS
It will install all the above mentioned features
so you might be missing some features due to the way you are specifying
Due to this article https://support.microsoft.com/en-us/kb/3192738 only basic installation is supported by web installer, at least at this point
I had sql server 2008 r2 express edition in my PC .But i unistalled it ,In order to install Sql server 2008 Enterprise edition trial version in my PC.
But some features in sql server 2008 showing "attempt to perform an unauthorized operation" error during installation process.
My operating system is windows 7 home basic 64 bit.
these are the feature which are showing error while installation:
sql server database engine service
sql server replication
sql server analysis services
please help me with this issue
Here's a couple things to try from people who have had similar problems:
Check: %\Microsoft SQL Server\100\Setup Bootstrap\Log\SystemConfigurationCheck_Report.htm
Copy installation files to disk and run from there.
Run setup as administrator.
Create a new local administrator account and use that to run the installation.
When error occurs, dont exit installation, run process monitor trace, click retry for installation, stop trace, locate registry key where where access denied is, give your account temporary full control on that key, retry again.
Use the slipstream procedure to update SQL Server 2008
This method allows you to update the entire product when you run the SQL Server 2008 Setup program after following one of the following procedures:
Procedure 1: Basic slipstream steps
Follow the following steps to create a slipstream drop that you can use for installing the original media and a service pack at the same time.
Install the following prerequisites for SQL Server 2008.
.NET Framework 2.0 SP2 for SQL Server 2008 Express Edition
You can obtain the .NET Framework 2.0 SP2 from the following Web site in Microsoft Download Center:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5b2c0358-915b-4eb5-9b1d-10e506da9d0f&displaylang=en
.NET Framework 3.5 SP1 for other editions
To download and install the .NET Framework 3.5 SP1, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkID=120550
Windows Installer 4.5
To download and install Windows Installer 4.5, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkID=49112
Download the latest service pack package that matches you system architecture. For example download the x64 package of SQL Server 2008 Service Pack 1 if your system is an x64-based system.
Extract the service pack by running the following command:
SQLServer2008SP1-KB968369-x64-ENU.exe /x:C:\SP1
Run the service pack to install Setup files on the computer. You will receive a Setup Support Files dialog box if the Setup support files have not been installed. You can also run the following file to install the setup support files:
C:\SP1\x64\setup\1033\sqlsupport.msi
Finally,
run the Setup.exe file from the SQL Server 2008 source media by specifying the /PCUSource parameter. For example:
Setup.exe /PCUSource=C:\SP1
I have been googling for this issue a lot but there were no solution working for me. atlast , I formatted my system for a fresh install which worked fr me.
The solution is simple.
1 - Install ONLY "Sql Server Database Engine"
2 - Start installation again and add any other features to your instance
P.S. No need to run as Admin or in Windows 7 compat-mode (if you are installing on 8 or 10)
In my Case, creating an Administrator Windows Account and installing SQL Server worked!
Also you can simply activate the built-in windows Administrator Account by running the "net user administrator /active:yes" command in command prompt(Admin Mode), then log in as Administrator. Now You can Install SQL Server without problem!
Finally I should say that you can use SQL Server from your own normal windows account after Installation and I recommend deactivating Administrator Account by "net user administrator /active:no"
I'm trying to install the developer edition of SQL Server 2008 R2. I run the setup as admin, but after it installs the "Setup Support Files", it closes and returns back to the installation center screen.
Any ideas?
I had this same problem and it appears to be something to do with previous versions leaving behind elements in their install/uninstall. I fixed it by running the Microsoft install/uninstall utility linked below. During the process you are asked what program you are trying to install and MSSQL Server 2008 R2 is listed. After running this the install continued after the "Setup Support Files" stage. Hope it helps!
http://support.microsoft.com/mats/Program_Install_and_Uninstall
So does it even installs Support files? You can check it by looking into "Programs and Features" (if using Windows Vista or 7) and if it is not there then it is not even installing support files. In that case may be you are missing components required for Support files itself (e.g. older version of Windows Installer).
Sometimes, SQL Server installer itself acts funny and without any reason it just crashes. Did you tried to run it again? Or try to run the installer after rebooting your system (I know this sound like a too rookie advice but in many cases rebooting OS solves issue).
The problem started when I change the shared folder directory from \Program Files(86)\SQL Server to custom folder. If I could have rename back to default, it should have been fine but I stop the installation and restart the install again assuming it will install fresh, but it did not and it hangs all the time.
I appreciate the comment from Lee, as per his advice I ran the fix it tool from Microsoft. The tool finds SQL Server 2008 R2 installed and I choose to uninstall.
When re-install the SQL Engine, it went through because this time, I did not change the Share Folder location and leave it to the default. I think this is some kind of bug in the SQL Installation. I wonder why Installation has to hang...!
The problem might be the location of the Setup Support Files.
Remove all the Setup Support Files using Control Panel/Uninstall Program.
After that install SQL 2008 from the beginning.