1

The release is created via TFS 2015. We just add 2 simple environments as following and link the release with a build. enter image description here But when the release is triggered, it always fail and the log shows "object reference not set to an instance of an object".

enter image description here

Is there any thing wrong with my setup? The release and build are using the same queue. And the agents attached onto the queue are work because the build (vNext Build) can success. Anyone can help on this problem??

Update: And the log only shows "Deployment on this environment was cancelled". What is the root cause of that? enter image description here

Max
  • 175
  • 1
  • 12

1 Answers1

-1

Please check the call stack in the event viewer as mentioned at https://connect.microsoft.com/VisualStudio/feedback/details/2745800/release-fail-with-deployment-on-this-environment-was-cancelled-message and if it is same call stack then you hit the same bug which will be fixed with TFS2015U3. For now to unblock yourself, you may write to RM_Customer_Queries@microsoft.com and i shall help you getting a dll with the fix which you can patch on your setup.

As the dll would be not officially signed by microsoft hence you have to wait for TFS2015U3 to be released to be used in any production environment. You can try it in a test environment though.

  • 1. I cannot found any event log related with my build agents on the machine where the agents running. 2. Yes, we have the project build service user in our project, but if I remove these (we have 2 of them with the same identifier) user, our build cannot run, and it complain: ##[error]TF14044: Access Denied: User Project Build Service (TEAM FOUNDATION) needs the AdminWorkspaces global permission(s). – Max Jun 02 '16 at 03:36
  • Can you please check the event viewer of server machine? start command prompt --> eventvwr --> Applications and Services Logs --> Microsoft Team Foundation Server --> Debug ( do repro and check error log). – chandan kumar anjani Jun 02 '16 at 16:38