We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Saurbaum
Posts: 12
Joined: Mon Sep 29, 2014 12:13 pm

Web Deploy failure

When I try to deploy my web page that has been packaged as part of a build step in Visual Studio it always fails with this line in the log.

Restore-WDPackage : Could not connect to the remote computer ("localhost"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Deployment Agent Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId= ... _REACHABLE.

Is there something specific I should enable in the installer prerequisites to ensure this service is running?

I've tried web deploy 3.5 from Microsoft and also IIS web deploy as a prerequisite in advanced installer.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Web Deploy failure

Hello and welcome to Advanced Installer forums,

I'm not sure why you encountered the this behavior.
Can you please tell us what is your target machine software configuration (OS version, IIS version, Windows Installer version) where you can replicate the behavior?

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Saurbaum
Posts: 12
Joined: Mon Sep 29, 2014 12:13 pm

Re: Web Deploy failure

It's a clean Windows 7 Sp1 64 bit VM with the latest updates installed.

Windows installer is reporting as "Windows ® Installer. V 5.0.7601.17514"

IIS7 is installed and configured (by advanced installer) to match the defaults if you clicked to enabled IIS manually.

The web package I'm trying to get deployed works if I use the deploy.cmd file which gets built at the same time, and that makes use of Web Deploy though not via powershell which the log implies is being used inside Advanced Installer.
Saurbaum
Posts: 12
Joined: Mon Sep 29, 2014 12:13 pm

Re: Web Deploy failure

I've managed to get a similar error out of the generated deploy.cmd file if I specify that it should use a specific machine and direct it to use "localhost" then I get the same error displayed as the Advanced installer does.

I don't know what more is happening in the deploy script to cause this change of behaviour compared to performing the local installation without specifying anything.

C:\Users\Install\Desktop>SCP.Web.deploy.cmd /T /G:False /M:localhost
SetParameters from:
"C:\Users\Install\Desktop\SCP.Web.SetParameters.xml"
You can change IIS Application Name, Physical path, connectionString
or other deploy parameters in the above file.
-------------------------------------------------------
Start executing msdeploy.exe
-------------------------------------------------------
"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -source:package='C:
\Users\Install\Desktop\SCP.Web.zip' -dest:auto,computerName="localhost",includeA
cls="False",tempAgent="False" -verb:sync -disableLink:AppPoolExtension -disableL
ink:ContentExtension -disableLink:CertificateExtension -setParamFile:"C:\Users\I
nstall\Desktop\SCP.Web.SetParameters.xml" -whatif
Info: Using ID '28cc7f75-fb24-44ce-bed6-32b91c3e8bca' for connections to the rem
ote server.
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the remote computer ("localhost"). On the
remote computer, make sure that Web Deploy is installed and that the required p
rocess ("Web Deployment Agent Service") is started. Learn more at: http://go.mi
crosoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Web Deploy failure

Hello,

Can you please assure that you are using the Web Deployment Agent Service (MsDepSvc) for deploying packages? This is what we use internally.

If not, the solution would be to directly use the IIS deploy profile (.publishsettings) with the Cloud option in the IIS page -> your web deploy package -> Publishing view -> Target section -> Cloud -> Profile Source.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Saurbaum
Posts: 12
Joined: Mon Sep 29, 2014 12:13 pm

Re: Web Deploy failure

Is there a way to install that as part of the Advanced Installer package to ensure it's present on the target machine?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Web Deploy failure

Hello,

First of all I apologize for such a delayed reply.

Our "Web Deployment" feature requires Microsoft Web Deploy 3.5 and PowerShell 2.0 (or later) to be installed on the target machine where the main installation runs. Therefore, in order to make sure that Web Deploy 3.5 and PowerShell 2.0 (or later) are installed on the target machine, then you can add them as prerequisites to your project. Just go to "Prerequisites" page and add our "IIS Web Deploy 3.5" and "PowerShell" predefined prerequisites as pre-install prerequisites to your project. Then, rebuild and test again the installation.

If the behavior still persists, could you send us a sample (.aip + a sample web deployment package) which replicates the behavior to support at advancedinstaller dot com so we can test and investigate this on our side?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: Web Deploy failure

I have the same issue. I have added PowerShell, IIS Web Depoly and Web Server Role to the Prerequisites. But the installation of the Web Deploy Package fails (Win Server 2012).



MSI (s) (38:DC) [12:33:39:865]: Executing op: CustomActionSchedule(Action=AI_IIsConfig,ActionType=11265,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (38:E0) [12:33:39:865]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI9E76.tmp, Entrypoint: OnIIsConfig
AI_IIsConfig: Installing "FASPool"
AI_IIsConfig: Installing "Default Web Site/FAS"
AI_IIsConfig: Installing "FAS"
IIS Web Deploy Publish execution log:
IIS Web Deploy publish Error log:
Restore-WDPackage : Es konnte keine Verbindung mit dem Remotecomputer ("localhost") hergestellt werden. Stellen Sie sicher, dass Web Deploy auf dem Remotecomputer installiert ist und der erforderliche Prozess ("Webbereitstellungs-Agent-Dienst") gestartet wurde. Weitere Informationen unter: http://go.microsoft.com/fwlink/?LinkId= ... _REACHABLE.
In C:\Users\Administrator\AppData\Local\Temp\pssE1D3.ps1:81 Zeichen:3
+ Restore-WDPackage @testParams
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) , Deplo ymentDetailedException
+ FullyQualifiedErrorId : ERROR_DESTINATION_NOT_REACHABLE,Microsoft.Web.De ployment.PowerShell.SyncPackage

Non-Invasive Test-Publish failed!

Error 4033. An error has occurred during the IIS Web Deploy configuration process for package "FAS".

Do you want to skip this package and continue the installation ?
MSI (s) (38!9C) [12:34:11:928]: Product: Your Application -- Error 4033. An error has occurred during the IIS Web Deploy configuration process for package "FAS".

Do you want to skip this package and continue the installation ?

MSI (s) (38:DC) [12:34:11:928]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (38:DC) [12:34:11:928]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (38:DC) [12:34:11:928]: User policy value 'DisableRollback' is 0
Attachments
prereq.PNG
prereq.PNG (15.7 KiB) Viewed 15310 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Web Deploy failure

Hello,

Can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate and test your installation scenario?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Web Deploy failure

Hello Bo,

I've tested your installation scenario on a Windows Server 2012 R2 German machine and I was finally able to isolate the issue. It seems this happens because of the silent command line you are using for the "Web Deploy" prerequisite.

When the Web Deploy prerequisite is launched with the "/quiet" command the "Remote Agent Service" feature of the Web Deploy product is not installed. The absence of this Web Deploy feature will cause the installation failure of your web deployment package. To avoid this issue you can use a silent command line which will install all features of the Web Deployment prerequisite product.

For instance, you can go to "Prerequisites page -> Setup File tab" and in the "Install Command Lines" fields use the following command:

Code: Select all

ADDLOCAL=ALL /qn /norestart LicenseAccepted="0"
Also, please note that the silent installation of the Web Deploy prerequisite could fail if the installation process is not launched elevated. So, it is recommended to enable the "Run as administrator" option from "Install Parameters" page too.

As a side note, considering that our default command line for the "Web Deploy" prerequisites is "/quiet", to avoid such issues in the future we will update the default silent command of the above prerequisites so they be installed fully-featured.

If you have any questions just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: Web Deploy failure

Thanks! Now it's working :)
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Web Deploy failure

You're always welcome.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: Web Deploy failure

Hi!
i have on other thing: it is working great aslong the WebDeploy is installed as a Feature-base prerequisite.
If i add it under the Chained prerequisites it seems like the Propertie "ADDLOCAL=ALL" is ignored.
How can i tell a Chained MSI to install complete?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Web Deploy failure

Hello,

Please note it is not possible to install the Web Deploy setup as a chained package added to the main project. This is because the chained packages will be installed at the very end of the main installation, thus after the web deployment package is being deployed by our IIS custom action. Therefore, considering that the Web Deploy package should already be present on target machine before the web deployment package installation, the only solution is to add it as a pre-install or feature-based prerequisite.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”