I'm trying to install Bonobo.Git.Server on my Windows 2008 R2 server (under IIS 7.0). I followed step by step the installation procedure (bonobo install) but when I try to access the application URL I got the following error:
What's up?
Well I forgot to install .NET Framework 4.6 (that was one of the prerequisites) now it works.
Related
I try to containerize a third party application running on IIS and Windows server. To do that, they supply to me a powershell script which is using Web deploy 3.
My problem is I can't install it, I always have this error code :
MSI install return value for product 'Web Deploy 3.6 ... is '1603'
The version 2 is installing though, but it's the version 3 which is required. I've also tried to install it with chocolatey, but I have the exact same error.
Here the part of the Dockerfile causing troubles :
FROM microsoft/windowsservercore-insider:10.0.17093.1000
[...]
# Register dll (the web say this can solve the error)
RUN regsvr32.exe %windir%\syswow64\vbscript.dll /s
# Copy The msi installer for web deploy 3.6
COPY webdeploy.msi C:\\Temp\\webdeploy.msi
WORKDIR C:\\Temp
# Install all webdeploy features
RUN msiexec /i webdeploy.msi LicenseAccepted="0" ADDLOCAL=ALL /quiet /qn /passive /norestart
Please do note I'am using the insider version because I need the MSMQ feature which is not released yet (It's a proof of concept).
Is there any requirement needed by webdeploy that I don't know and which is missing in the container version ?
It seems there is a bug in the preview build (as mentioned by #Gregory Suvalian). Using the last one (17623) seems to correct the problem.
This is my error
I'm running Delphi 7 and was not able to start a Http web demo
I tried to install phalanger to see if that worked, only to get error 80040154
has any one seen this error before.
I believe I have run aspnet_regiis.exe -ir to install .net 4
phalanger says iis 7.5 is installed
I found it hard to produce a new site in ISS so I carefully modified the example to my needs.
I'm questioning if I have done something wrong some were
I keep getting the error message when attempting to install IIS on Windows 7
"An error has occurred. Not all the features were successfully changed."
The iis7.log contains shows...
[07/17/2013 12:48:05] "C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries
[07/17/2013 12:48:05] Successfully added IIS_IUSRS ACE to DACL at %ProgramData%\Microsoft\Windows\WER\ReportQueue.
[07/17/2013 12:48:05] < !!FAIL!! > Failed to acquire the NetFrameworkConfigurationKey key container context (result=0x8007054f)
[07/17/2013 12:48:05] < !!FAIL!! > Install of component SharedLibraries result=0x8007054f
[07/17/2013 12:48:05] < !!FAIL!! > COMPONENT::ExecuteCommand result=0x8007054f
I have tried doing a clean boot (disabling non-microsoft services) but this has not helped.
Has anyone got anything to suggest?
Cheers,
Dave
This problem occurs due to unstable changes in Microsoft .Net Framework follow these steps to fix it out.
Step1:
Remove Microsoft .Net Framework under Turn Windows features on or off.
Step2:
Again Install IIS 6 or 7 under Turn Windows features on or off.
Step3:
Again install Microsoft .Net Framework under Turn Windows features on or off.
I've encountered the same error while I was installing the IIS on a windows 7 , 32 bit machine.
I've tried almost all the solution that I found in many websites.
In order to get rid of this error you can do a repair of the OS. it will solve the issue permanently.
Windows 7
Try this,
run cmd as Admin.
Unistall all iis.
start /w pkgmgr.exe /uu:IIS-WebServerRole;WAS-WindowsActivationService
Reinstall iis and normaly it's work
Alain
I know this is an old post, but I was just able to successfully install IIS on Windows 7 Sp1 (64bit) after having the same problem and 2 days of internet searches. I hope I can help someone with the same problem.
After running the same command "C:\WINDOWS\System32\inetsrv\iissetup.exe" /install SharedLibraries" and monitoring it using ProcessMonitor, it appeared that the installer is not able to write to the folder "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys"
I renamed MachineKeys to MachineKeys_old and reinstalled the IIS feature and it completed without any errors.
I am creating an installation that is adding a web site to IIS. But when I am trying to run the installation on a machine with IIS 7 installed and IIS 6 compatibility mode not installed, it fails the installation with:
Error 1920.Service IISADMIN (IISADMIN) failed to start. Verify that
you have sufficient privileges to start system services
If I install the compatibility feature it fixes the problem and the installation succeeds.
I want to know if there is a way to not install this feature on IIS 7.
Or if it must be installed - how can I install it automatically?
btw, I have installShield 2011 Professional.
Eventually what I did is to run as custom actions this lines
dism /online /enable-feature /featurename:IIS-IIS6ManagementCompatibility
dism /online /enable-feature /featurename:IIS-Metabase
and use as condition Not Installed and IIS_VERSION > "#6"
Thanks for Cosmin Privu help
Ben
You can try adding the compatibility fix as a custom prerequisite to your package:
http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/SetupPrereqEditor.htm
For example you can create a custom EXE which uses pkmgr.exe to install the IIS-IIS6ManagementCompatibility feature (it's like installing it from Control Panel).
It can be configured to install only when it's not found and only if IIS 7 is installed. This way you can make sure that the service can always be started for IIS 7.
I am using mono 2.8 with Visual Studio 2008. I have installed "mono-2.8-gtksharp-2.12.10-win32-9".
I am creating a windows application and its setup solution is working fine on Windows OS. But when I am creating package for Linux and follow the instruction from http://mono-tools.com/Package.aspx
Step-1 to Step-5 are done but after Step-5, I am clicking on Create Package and its do nothing even its not create any file into selected folder.
Please help..
When you choose the host for it to build the package on, make sure you are choosing a SUSE or RHEL server, or the process will silently fail.