I have a Windows Server 2008 machine and I am trying to install ARR and URL Rewrite IIS modules. When I run the ARR installer from the official website, I get an error saying "The product did not install successfully.". URL Rewrite installs just fine. See below:
The log files don't have anything useful. Just a line regarding customAction IISExecuteCA returned actual error code 1603. This installs fine on my Windows 10 machine.
I have tried the following with no luck:
Installing ARR1
Installing ARR2
Stopping IIS and WAS and WMSVC services and running the installer
Restarting the machine
Error in the installation log:
MSI (s) (E4:F4) [11:48:42:071]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBB42.tmp, Entrypoint: IISExecuteCA
1: IISCA IISExecuteCA : Begin CA Setup
1: IISCA IISExecuteCA : CA 'ExecuteInstallModuleCA' completed with return code hr=0x8007000d
1: IISCA IISExecuteCA : CA 'IISExecuteCA' completed with return code hr=0x8007000d
1: IISCA IISExecuteCA : End CA Setup
CustomAction IISExecuteCA returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (E4:08) [11:48:42:274]: User policy value 'DisableRollback' is 0
MSI (s) (E4:08) [11:48:42:274]: Machine policy value 'DisableRollback' is 0
Action ended 11:48:42: InstallFinalize. Return value 3.
Anyone experiencing a similar issue?
I was able to install ARR 2.5 and it resolved the issue! This issue appears to be due to the old Win 2008 server and its incompatibility with ARR 3.0. I found the ARR 2.5 link from here
I am running installer with /verysilent /suppressmessagebox /norestart for upgrading my application (Windows Service). In PrepareToInstall(), I have code in place to check and stop an already running instance of my service using net stop <ServiceName>. I do log the output generated by net stop and it shows that the service has indeed been stopped. However, at times, the installer prompts that :
Message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.
Click Retry to try again, Ignore to proceed anyway, or Abort to cancel installation.
The logs show :
2017-05-10 23:47:38.851 Log opened. (Time zone: UTC-07:00)
2017-05-10 23:47:38.851 Setup version: Inno Setup version 5.5.9 (u)
2017-05-10 23:47:38.851 Original Setup EXE: C:\Windows\TEMP\installer.exe
2017-05-10 23:47:38.851 Setup command line: /SL5="$FD006E,3807712,131584,C:\Windows\TEMP\installer.exe" /verysilent /suppressmessagebox /norestart /log=C:\ProgramData\<ServiceName>\installer_2026493391.txt
2017-05-10 23:47:38.851 Windows version: 6.1.7601 SP1 (NT platform: Yes)
2017-05-10 23:47:38.851 64-bit Windows: Yes
2017-05-10 23:47:38.851 Processor architecture: x64
2017-05-10 23:47:38.851 User privileges: Administrative
2017-05-10 23:47:38.867 64-bit install mode: Yes
2017-05-10 23:47:38.867 Created temporary directory: C:\Windows\TEMP\is-OO761.tmp
.....
..... Some logs irrelevant to the issue at hand
.....
2017-05-10 23:47:39.148 Stopping <ServiceName> Service - begin
2017-05-10 23:47:39.148 Command : /S /C ""net" stop <ServiceName> > "C:\Windows\TEMP\is-OO761.tmp\~execwithresult.txt" 2>&1"
2017-05-10 23:47:39.257 Stopping <ServiceName> Service - done
2017-05-10 23:47:39.257 The <Service Display Name> service is stopping.
The <Service Display Name> service was stopped successfully.
2017-05-10 23:47:39.366 RestartManager found an application using one of our files: <Service Display Name>
2017-05-10 23:47:39.366 Can use RestartManager to avoid reboot? Yes (0)
2017-05-10 23:47:39.366 Starting the installation process.
2017-05-10 23:47:39.366 Shutting down applications using our files.
2017-05-10 23:47:39.382 Some applications could not be shut down.
2017-05-10 23:47:39.382 Message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.
Click Retry to try again, Ignore to proceed anyway, or Abort to cancel installation.
There are 2 issues :
Why is message box displayed in /verysilent mode ? As per this fix, it should not be displayed in silent mode. As per documentation, I do see that :
/SILENT, /VERYSILENT
Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven't disabled it with DisableStartupPrompt or the '/SP-' command line option explained above).
Why does RestartManager seem to still believe that the exe is running when it has already been stopped ? Has anyone else seen similar issues and is there a recommended way ? (say, add a 5 second pause after the net stop command)
It's /SUPPRESSMSGBOXES, not /SUPPRESSMESSAGEBOX.
It can be an antivirus or similar, what blocks the file. If you try to move/delete the binary immediately after net stop, does it succeed?
when trying to deploy my uwp application (no difference for Simulator, local or x86, x64), I get the following error:
Error : DEP0500 : The folder "...\bin\x86\Debug\AppX" could not be deleted.
Access to the path 'mscordbi.dll' is denied
With the tool 'ProcessExplorer' I found that VS2015 itself is locking the file. After a manual delete, I can run a single deployment, but the second fails due to the locked file again. I already tried the following Things, without any effect:
- delete VS-Settings
- move projects to a new solution
Why is this file locked by Visual Studio?
I setup a new Win2012 VM in Azure with the Chef plugin and have it connected to manage.chef.io. Added a cookbook which uses the WebPi cookbook to install ServiceBus and its dependencies. The install fails with the following error:
“Error opening installation log file. Verify that the specified log file location exists and is writable.”
After some searching it looks like this is not new in Azure based on this 2013 blog post - https://nemetht.wordpress.com/2013/02/27/web-platform-installer-in-windows-azure-startup-tasks/
It offers a hack to disabled security on the folder temporarily but I'm looking for a better solution.
Any ideas?
More of the log output -
Started installing: 'Microsoft Windows Fabric V1 RTM'
.
Install completed (Failure): 'Microsoft Windows Fabric V1 RTM'
.
WindowsFabric_1_0_960_0 : Failed.
Error opening installation log file. Verify that the specified log file location exists and is writable.
DependencyFailed: Microsoft Windows Fabric V1 CU1
DependencyFailed: Windows Azure Pack: Service Bus 1.1
.
..
Verifying successful installation...
Microsoft Visual C++ 2012 SP1 Redistributable Package (x64) True
Microsoft Windows Fabric V1 RTM False
Log Location: C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Web Platform Installer\logs\install\2015-05-11T14.15.51\WindowsFabric.txt
Microsoft Windows Fabric V1 CU1 False
Windows Azure Pack: Service Bus 1.1 False
Install of Products: FAILURE
STDERR:
---- End output of "WebpiCmd.exe" /Install /products:ServiceBus_1_1 /suppressreboot /accepteula /Log:c:/chef/cache/WebPI.log ----
Ran "WebpiCmd.exe" /Install /products:ServiceBus_1_1 /suppressreboot /accepteula /Log:c:/chef/cache/WebPI.log returned -1
A Chef contact (thanks Bryan!) helped me understand this issue better. Some WebPI packages do not respect the explicit log path provided to WebPIcmd.exe. The author should fix the package to use the provided log path when it is set. So the options became:
Have the author fix the package
Run Chef in a new scheduled task as a different user which has access
to the AppData folder
Edit the cookbook to perform/unperform a registry edit to temporarily move the AppData folder to a location that the System
user has access. Either in my custom cookbook or fork the WebPI
cookbook.
Obviously, waiting on the author (Microsoft in this case) to fix the package would not happen quickly.
Changing how the Azure VM runs Chef doesn't make sense considering the whole idea is to provide the configuration at the time of provisioning and it just work. Plus changing the default setup may have unintended consequences and puts us in a non-standard environment.
In the short term, I decided to alter the registry in my custom cookbook.
registry_key 'HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders' do
values [{
:name => "Local AppData",
:type => :expand_string,
:data => "%~dp0appdata"
}]
action :create
end
webpi_product 'ServiceBus_1_1' do
accept_eula true
action :install
end
webpi_product 'ServiceBus_1_1_CU1' do
accept_eula true
action :install
end
registry_key 'HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders' do
values [{
:name => "Local AppData",
:type => :expand_string,
:data => '%%USERPROFILE%%\AppData\Local'
}]
end
This change could also be done in the WebPI cookbook as well to fix this issue for all dependent cookbooks. I decided to not approach this until the WebPI team responds to a feature request for the framework to verify packages respect the log path instead.
http://forums.iis.net/t/1225061.aspx?WebPI+Feature+Request+Validate+product+package+log+path+usage
Please go and reply to this thread to try to get the team to help protect against this common package issue.
Here is the solution with POWERSHELL
I had the same error while installing "Service Fabric SDK" during VMSS VM creation. Also the system user was used.
Issue: when I was connecting with RDP with my "admin" user and run the same, it worked.
Solution: change the registry entry as above, install and reset back
here is my solution using "powershell"
I installed 2 .reg files into %TEMP% folder. The content is the old and new exported key / value for the
plugin-sf-SDK-temp.reg
Windows Registry Editor Version 5.00
[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
"Local AppData"=hex(2):25,00,54,00,45,00,4d,00,50,00,25,00,00,00
plugin-sf-SDK-orig.reg
Windows Registry Editor Version 5.00
[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
"Local AppData"=hex(2):25,00,55,00,53,00,45,00,52,00,50,00,52,00,4f,00,46,00,\
49,00,4c,00,45,00,25,00,5c,00,41,00,70,00,70,00,44,00,61,00,74,00,61,00,5c,\
00,4c,00,6f,00,63,00,61,00,6c,00,00,00
Integrate the following code into your custom-powershelgl script:
Write-Output "Reset LocalApp Folder to TEMP"
Start-Process "$($env:windir)\regedit.exe" `
-ArgumentList "/s", "$($env:TEMP)\plugin-sf-SDK-temp.reg"
## replace the following lines with your installation - here my SF SDK installation via WebWPIcmd
Write-Output "Installing /Products:MicrosoftAzure-ServiceFabric-CoreSDK"
Start-Process "$($env:programfiles)\microsoft\web platform installer\WebPICMD.exe" `
-ArgumentList '/Install', `
'/Products:"MicrosoftAzure-ServiceFabric-CoreSDK"', `
'/AcceptEULA', "/Log:$($env:TEMP)\WebPICMD-install-service-fabric-sdk.log" `
-NoNewWindow -Wait `
-RedirectStandardOutput "$($env:TEMP)\WebPICMD.log" `
-RedirectStandardError "$($env:TEMP)\WebPICMD.error.log"
Write-Output "Reset LocalApp Folder to ORIG"
Start-Process "$($env:windir)\regedit.exe" `
-ArgumentList "/s", "$($env:TEMP)\plugin-sf-SDK-orig.reg"
I have a simple SharePoint project with one farm-scoped feature. The feature contains no modules; it just refers to an SPClaimProviderFeatureReceiver-derived class which in turn points to an SPClaimProvider-derived class.
When I tell the project to deploy, it does successfully add the assembly to the GAC, and does successfully create Feature.xml within a folder in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES, and gives this output:
------ Build started: Project: xxx, Configuration: Debug Any CPU ------
xxx -> E:\xxx\bin\AnyCPU\Debug\xxx.dll
Successfully created package at: E:\xxx\xxx.wsp
------ Deploy started: Project: xxx, Configuration: Debug Any CPU ------
Active Deployment Configuration: Default
Run Pre-Deployment Command:
Skipping deployment step because a pre-deployment command is not specified.
Recycle IIS Application Pool:
Skipping application pool recycle because no matching package on the server was found.
Retract Solution:
Skipping package retraction because no matching package on the server was found.
Add Solution:
Adding solution 'xxx.wsp'...
Deploying solution 'xxx.wsp'...
Activate Features:
No features in this solution were activated.
Run Post-Deployment Command:
Skipping deployment step because a post-deployment command is not specified.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
The deployed Feature.xml:
<?xml version="1.0" encoding="utf-8"?>
<Feature xmlns="http://schemas.microsoft.com/sharepoint/"
Title="xxx"
AutoActivateInCentralAdmin="TRUE"
Description="xxx"
Id="063aae98-029f-4c01-a20e-15b6c8576bc8"
ReceiverAssembly="xxx, Version=0.1.0.0, Culture=neutral, PublicKeyToken=6e7f8ba8e1265a7f"
ReceiverClass="xxx" Scope="Farm" />
I'm concerned that it says that no features were activated. The WSP does show up in Central Administration Solution Management, but says that it "isn't deployed", and the feature doesn't show up in Manage Farm Features. When I click on Deploy in the web interface, it says "The solution was successfully deployed" (Why didn't VS do this??). But after that the feature still doesn't show up.
In VS solution explorer, right click on project >> select properties >> select sharepoint tab
Here you have different 'Active deployment configuration'. make sure you have selected appropriate configuration from drop down list. you can modify and view steps of each configuration.
If you get this kind of error while deploying your solutions to sharepoint environment, ensure that your project is not a sandboxed solution.
Click on your project, go to properties window in Visual Studio and change the value of Sandboxed Solution from true to false. Rebuild your project and deploy.
skipping pre and post deployment command is only a warning because you haven't specified any command for these steps.
in VS SharePoint tab (see Rahil answer on how to get there), you have 2 text boxes for writing your pre and post commands