Azure-pipelines-tasks: Azure SQL Daptabase Deployment: Task.uploadFile cmdlet is not working with Hosted VS 2017

[TechWatching]

Environment

• Server - Azure Pipelines
• Agent - Hosted Agent (Hosted VS2017)

Issue Description

Task : Azure SQL Database Deployment (Action : Export)
The Azure SQL Database Deployment task is failing. The export of an Azure Database. seems to work fine, the bacpac file is correcty saved to GeneratedOutputFiles folder but the when the task is "uploading files to the logs" an error occurs.

The same build with the same parameters on the same database worked perfectly the days before, could it be a storage space issue ?

Task logs

Debug logs of the Azure SQL Daptabase Deployment task.
logs.txt

Error logs

Unable to process command '##vso[task.uploadfile] D:\a\1\s\GeneratedOutputFiles**-int.bacpac' successfully
Cannot upload task attachment file, attachment file location is not specified or attachment file not exist on disk
at Microsoft.VisualStudio.Services.Agent.Worker.TaskCommandExtension.ProcessTaskAddAttachmentCommand(IExecutionContext context, Dictionary`2 eventProperties, String data)
at Microsoft.VisualStudio.Services.Agent.Worker.WorkerCommandManager.TryProcessCommand(IExecutionContext context, String input)

[evolve700]

Had to delete my previous comment because the log was not redacted correctly.
Still, I too tncounter this issue on my own privately hosted build machine. The exact same error occurs. Here's the non-debug log:
azuresql.log

[TingluoHuang]

@TechWatching try remove the write space in your ##command

##vso[task.uploadfile] D:\a\1\s\GeneratedOutputFiles********-int.bacpac to ##vso[task.uploadfile]D:\a\1\s\GeneratedOutputFiles********-int.bacpac

[TechWatching]

I am using the visual designer for my build so I have no control on this. The command you are mentionning is a command done by the "Azure SQL Database Deployment" task. I only can see the logs.

[szymon-wesolowski]

Have exactly same problem.

[bryanmacfarlane]

@kmkumaran - this seems scoped to the azure sql task. task.upload file is working fine

[Ajay-MS]

Closing as this issue has been fixed.

PR - https://github.com/Microsoft/azure-pipelines-tasks/pull/9268

It will be deployed with next deployment. ETA - 3 to 4 weeks approx.

[older]

I get the same error. It could be a coincidence but I suspect that this happens when database name contains dash character ("-").

[robdavey555]

_Note: My database name does not use "-"_

I have an issue with the Export function. Extract works fine but I need to use export so I get my data.

This is the step in my release pipeline

I have compared the Extract and Export functions in SqlAzureActions.ps1 and cannot spot any reason why Extract would work but Export would fail.

Any suggestions?

[robdavey555]

@arjgupta Is there any update on this issue. Do you need any additional info from me?

[arjgupta]

@robdavey555 , are you using Team Foundation Server ? You seem to have an older version of the task which does not have the fix for this issue.

[robdavey555]

@arjgupta - I am using an Azure Devops (VSTS) pipeline. This issue seems to be resolved now so must have been fixed elsewhere. Thank you.