Giter Club home page Giter Club logo

Comments (5)

aidanfolkes avatar aidanfolkes commented on May 18, 2024 2

@ynijs, @chshrikh
Hi,
I was getting the same "doesn't exists." message and it turned out to be because Web Deploy Package was wrong.
The error message is incomplete. In MsDeployOnTargetMachines.ps1, line 184
throw "$packageFile doesn't exists."
$packageFile is not set. I think it should be $Path.

from azure-pipelines-extensions.

shanecastle avatar shanecastle commented on May 18, 2024

I'm getting a similar issue. If I have a release with "IIS Web App Management", I cant save the release, I get the error: "TF400893: Unable to contact the server. This is most likely caused by a network error. Please check your connection and try again."

If I run the release as is, I get a similar error. I'm deploying an app to on-prem IIS via VSTS

from azure-pipelines-extensions.

chshrikh avatar chshrikh commented on May 18, 2024

@ynijs could you please set the system.debug variable with value as true and share the logs to RM_Customer_Queries at Microsoft dot com or post them here.

from azure-pipelines-extensions.

dascalos avatar dascalos commented on May 18, 2024

I too was getting the "Doesn't Exists" error. I spent a few hours today pouring over the logs and I see what the problem is. When I publish my artifacts, I choose artifact type Server (not Share). When the IIS Deployment WinRM script runs on the IIS box, it pushes a path of c:\blah\blah\blah. The IIS box doesn't have that file on it's box. Changing artifact type to Share and all works as expected. Is there a way to do this with artifact type of Server? This is the way I would prefer to publish my artifacts.

from azure-pipelines-extensions.

Ajay-MS avatar Ajay-MS commented on May 18, 2024

@ynijs @shanecastle @aidanfolkes @dascalos
This issue has been fixed. If you still face this issue feel free to reopen this issue.

@dascalos
When you select artifact type as server, then during queue a RD, artifacts are being downloaded to agent box. But for WinRm task artifacts need to be present on target machine. So you have to you copy tasks ( like Windows File Copy or Azure File Copy) in your RD to copy artifacts from local machine to target machine. After copy task you can add WinRm tasks.

from azure-pipelines-extensions.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.