Skip to main content

Notifications

Announcements

Announcing Mentions and Quick Responses!
News and Announcements icon
Dynamics 365 Community / Blogs / /

Liquid error: Value cannot be null. Parameter name: key Profile Picture Liquid error: Value cannot be null. Parameter name: key Community member

Comments

*This post is locked for comments

  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at
    Is this limitation still relevant? "LIMITATIONS: The deployment task currently only supports traditional cloud hosted environments on private or on the Microsoft subscription. It currently does not support on-premise or the newer self-service environments. This is planned for a future release." Thanks
  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at
    Is this limitation still relevant? LIMITATIONS: The deployment task currently only supports traditional cloud hosted environments on private or on the Microsoft subscription. It currently does not support on-premise or the newer self-service environments. This is planned for a future release. Thanks
  • mhdshb1 Profile Picture mhdshb1 1,250
    Posted at
    Thank you Joris, Excellent work. It saved us a lot of time. When is the estimate for arrival of the LCS asset deployment for OnPrem?
  • perreaultd Profile Picture perreaultd
    Posted at
    Any ETA on support for on-prem or self-service environments?
  • perreaultd Profile Picture perreaultd
    Posted at
    There is one limitation i do not understand where you say that tasks is supported for cloud-hosted but not for on-prem or the "newer self-service environments". Whats the differences between those 3 env. type? I have not found any clear documentation about the "self-service environments".
  • MeaCulpa Profile Picture MeaCulpa
    Posted at
    For those who do not understand why the deployments are shown as "failed" despite succeding on LCS, here's the response I got from contacting the Microsoft Support : "I think what you may be seeing is the 60 minute maximum on hosted agent processes. If you’re running the release pipeline on an Azure DevOps (AZDO) hosted agent, AZDO will only let it run for 60 minutes. If it’s over 60 minutes, it will cancel the job. In that case, AZDO will show a failure, but LCS is still running the deployment and may actually succeed. This is expected." So it's basically your agent which timeout
  • zoemac1112 Profile Picture zoemac1112 5
    Posted at
    Ive got an issue where the task failed becuase the agent isnt above 2.119, even though it is No agent found in pool which satisfies the specified demands: azureps Agent.Version -gtVersion 2.119.1 Agent.Version - 2.150.0
  • kgmadsen Profile Picture kgmadsen 30
    Posted at
    Regarding the issue with the Error "in request to deploy file asset: 'The request is invalid." please take a look at the link here : www.linkedin.com/.../ - Worked for me ! :)
  • Martin Rasmussen Profile Picture Martin Rasmussen 15
    Posted at
    Any input to this? It fails at DevOps. i.imgur.com/3VYGwEc.jpg But it seems completed at LCS: i.imgur.com/9kaYFhV.jpg We are using the same configuration in other environments, both at the same customer and other customers, where we sometimes see the error as well.
  • Budi Ristanto Profile Picture Budi Ristanto 75
    Posted at
    Hi Joriz thanks you very much,, i got some error after upload release to lcs -> Error '' in request to deploy file asset: 'The request is invalid.' im using $(Release.ReleaseName) $(Build.BuildNumber)for name and it succesuffuly uploaded to lcs with release name and build number..