same here - all releases failing all morning.

Exception Message: One or more errors occurred. (type AggregateException) Exception Stack Trace: at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Microsoft.VisualStudio.Services.ReleaseManagement.Artifact.Extensions.Build.BuildArtifact.GetBuildArtifacts(IVssRequestContext requestContext, Guid projectId, Int32 buildId) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\ArtifactType\Build\BuildArtifact.cs:line 189 at Microsoft.VisualStudio.Services.ReleaseManagement.Artifact.Extensions.Build.BuildArtifact.GetArtifactConfigurationVariables(IVssRequestContext context, IDictionary`2 sourceInputs) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\ArtifactType\Build\BuildArtifact.cs:line 1941 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetArtifactVariables(Release release, IVssRequestContext requestContext) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 368 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetMergedReleaseVariables(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentSnapshotDelta deploymentDelta, Boolean includeArtifactVariables) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 562 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetAutomationEngineInput(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep step, Int32 trialNumber, DeployPhaseSnapshot snapshotToProcess, ReleaseEnvironmentSnapshotDelta deploymentDelta) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 283 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.Run(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep deployStep, DeployPhaseSnapshot snapshotToProcess) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 262 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseOrchestrator.RunDeployPhase(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep deployStep, DeployPhaseSnapshot snapshotToProcess) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseOrchestrator.cs:line 465 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseOrchestrator.InvokeRunner(Release release, ReleaseEnvironmentStep deployStep, ReleaseEnvironment releaseEnvironment, DeployPhaseSnapshot snapshotToProcess, Func`5 runDeployPhase, Action`4 acceptStep, Action`3 rejectStep, Action`4 handleException) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseOrchestrator.cs:line 436 Inner Exception Details: Exception Message: Page not found. (type VssServiceResponseException) Exception Stack Trace: at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<HandleResponseAsync>d_53.MoveNext() in C:\tmp\a_work\6\s\Vssf\Client\WebApi\VssHttpClientBase.cs:line 922 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d_51.MoveNext() in C:\tmp\a_work\6\s\Vssf\Client\WebApi\VssHttpClientBase.cs:line 869 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Team Exception: System.AggregateException

Yes, we are getting the same error too. What is going on?

,

I am having the same issue this morning too. Please let us know what is happening.

Same issue here:

Exception Message: One or more errors occurred. (type AggregateException) Exception Stack Trace: at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Microsoft.VisualStudio.Services.ReleaseManagement.Artifact.Extensions.Build.BuildArtifact.GetBuildArtifacts(IVssRequestContext requestContext, Guid projectId, Int32 buildId) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\ArtifactType\Build\BuildArtifact.cs:line 189 at Microsoft.VisualStudio.Services.ReleaseManagement.Artifact.Extensions.Build.BuildArtifact.GetArtifactConfigurationVariables(IVssRequestContext context, IDictionary`2 sourceInputs) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\ArtifactType\Build\BuildArtifact.cs:line 1941 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetArtifactVariables(Release release, IVssRequestContext requestContext) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 368 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetMergedReleaseVariables(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentSnapshotDelta deploymentDelta, Boolean includeArtifactVariables) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 562 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.GetAutomationEngineInput(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep step, Int32 trialNumber, DeployPhaseSnapshot snapshotToProcess, ReleaseEnvironmentSnapshotDelta deploymentDelta) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 283 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseRunner.Run(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep deployStep, DeployPhaseSnapshot snapshotToProcess) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseRunner.cs:line 262 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseOrchestrator.RunDeployPhase(Release release, ReleaseEnvironment releaseEnvironment, ReleaseEnvironmentStep deployStep, DeployPhaseSnapshot snapshotToProcess) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseOrchestrator.cs:line 465 at Microsoft.VisualStudio.Services.ReleaseManagement.Server.Processors.DeployPhaseOrchestrator.InvokeRunner(Release release, ReleaseEnvironmentStep deployStep, ReleaseEnvironment releaseEnvironment, DeployPhaseSnapshot snapshotToProcess, Func`5 runDeployPhase, Action`4 acceptStep, Action`3 rejectStep, Action`4 handleException) in C:\tmp\a_work\6\s\ReleaseManagement\Service\ReleaseManagement2\Server\Processors\DeployPhaseOrchestrator.cs:line 436 Inner Exception Details: Exception Message: Page not found. (type VssServiceResponseException) Exception Stack Trace: at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<HandleResponseAsync>d_ 53.MoveNext() in C:\tmp\a_work\6\s\Vssf\Client\WebApi\VssHttpClientBase.cs:line 922 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d_51.MoveNext() in C:\tmp\a_work\6\s\Vssf\Client\WebApi\VssHttpClientBase.cs:line 869 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Team

Exception: System.AggregateException

same issue here

Same issue here..

Sorry to be slow to respond to this but if you're still having the issue, one option we found to get around this was add our release steps inside our build pipeline essentially just piggyback on the running build agent. It's a temporary fix to keep things going...

We have fixed this issue. Please let us know if you are still seeing this issue.