Property 'MsDeployServiceUrl' must be non-empty

[Febin Thomas]

I get this error error from bitbucket pipeline windows runner. how can I troubleshoot this error?

[Theodora Boudale]

Hi @Febin Thomas and welcome to the community!

The error indicates that the property 'MsDeployServiceUrl' doesn't have a value.

Do you see this error in the output of a command that is running during your Windows Runner build?

Are you using MSBuild and is this the property in question?

https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2013/hh728012(v=vs.120)

If so, have you configured this property in your code?

Kind regards,
Theodora

[Febin Thomas]

Hi @Theodora Boudale , Thanks for replying.

But is the given link a valid one? I get 404 code.

[Febin Thomas]

I have added the value as an unsecured repository variable. 

like

my_server_name

and the variable name is used in my bitbucket-pipeline.yml file  as follows

---

dotnet publish

-p:AllowUntrustedCertificate=True

-p:UserName=$my_server_user

-p:Password=$my_server_password

-p:MsDeployServiceUrl=$my_server_name

-p:DeployIisAppPath=MyTestAppt

-p:MSDeployPublishMethod=WMSVC

-p:WebPublishMethod=MSDeploy

I get the same error.

Please note my repository access level is admin

[Theodora Boudale]

Hi @Febin Thomas,

The link was missing a parenthesis, sorry for that, I fixed it and the link should work now.

I would suggest trying two things to narrow down if the issue seems to be specific to the runner or not:

1. Try replacing $my_server_name with the actual value in the bitbucket-pipeline.yml file for testing purposes to see if the issue is also reproducible.

2. Try running this build outside of the runner in PowerShell, on the same computer where you have the runner. Clone the branch of the repo where the build runs and do a git reset to the commit of the build. Then, execute the commands of your bitbucket-pipeline.yml file. You would need to provide values for any Pipelines variables you are using.

If the issue is reproducible in both cases, then it is most likely related to your project's configuration and you could try reaching out to Microsoft's Q&A for guidance.

If the issue is not reproducible without the runner, you can create a ticket with the support team, provide the URL of the failed build and the output that you get when you run the build in PowerShell outside the runner, and ask for assistance.

You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.

Please feel free to let me know if you have any questions!

Kind regards,
Theodora

[Febin Thomas]

hi @Theodora Boudale , surprisingly I could see that this issue can be resolved by keeping the format as follows

-p:UserName=$Env:aws_ext_user

-p:Password=$Env:aws_ext_password

-p:MsDeployServiceUrl=$Env:aws_ext_server

I really don't know how this working $Env representing the environment variable.

[Theodora Boudale]

Hi Febin,

You are right, the $Env part is needed because the runner runs in PowerShell, and PowerShell uses this syntax ($Env:variable_name) to reference environment variables. Apologies, I missed that earlier.

Kind regards,
Theodora

[Febin Thomas]

Now I am facing a different issue. I am not sure that It would be a different topic to discussion but I fall in to this issue immediately after I passed the above specified issue

Now I am trying resolve the issue of

[Theodora Boudale]

Hi Febin,

A 404 error typically indicates that the resource you are trying to access does not exist.

I would recommend again running the build in PowerShell, outside the runner, as I previously suggested, to narrow down whether this is a runner-specific issue or not.

Kind regards,
Theodora