11

I have Windows server 2012 R2 with installed Web Deploy 3.5.

I try to deploy my application, but got next error:

enter image description here

Log file contains next:

enter image description here

Is there any solution?

Maxim Zhukov
  • 10,060
  • 5
  • 44
  • 88
  • 1
    Possible duplicate of [Error: "The configuration section 'system.webServer/management/delegation' cannot be read because it is missing schema](http://stackoverflow.com/questions/32004797/error-the-configuration-section-system-webserver-management-delegation-canno) – Carl Onager May 05 '17 at 09:14

4 Answers4

15

I had installed Web Deploy 3.6 & Web Deploy 3.5. Uninstall 3.6 and reinstall 3.5 solved my problem.

adiga
  • 34,372
  • 9
  • 61
  • 83
Maxim Zhukov
  • 10,060
  • 5
  • 44
  • 88
5

In my case, it was the sequence of installation for management service and web deployment.

You need to install management service first and then install web deployment.

if you mess up the order like I did, uninstall web deployment and reinstall it.

maxisam
  • 21,975
  • 9
  • 75
  • 84
4

In my opinion this issue is most likely an issue with the installation of web deploy 3.6

I noticed that when I installed the component using the web.matrix it do not work properly, you need to use the webdeploy stand alone installer (you can download it from the MS page): first delete the web.deployment 3.6 (reinstalling or repairing do not work), then, click the setup and choose a custom setup installation and be sure to mark all the components from the list. Done.

After this fix you can use web.deployment 3.6 without any issues.

I hope it helps

David Rivera
  • 56
  • 1
  • 1
    Same experience here; Installing WD 3.6 using Web Deploy, I received the error specified by the OP. Uninstalled WD 3.6 from control panel; Downloaded and installed WD 3.6 msi, did not receive the error anymore. – H A Sep 21 '17 at 17:02
1

This is crazy.

I installed Windows Server 2019, followed mostly what I needed as features, no single place had all of what you needed listed. Then installed 3.6, found I needed more. Went back and updated 3.6 now it had more to install. Then I got a similar error, basically schema not found. I left everything alone, completely uninstalled 3.6, booted, installed 3.6 custom and made sure everything was selected, booted again, bam.. clicked validate connection and came right up.

Brett Maiwald
  • 41
  • 2