tfsaggregator / tfsaggregator-webhooks

WARNING: the team is no more maintaing this version. See aggreggator-cli instead.
https://github.com/tfsaggregator/aggregator-cli
19 stars 22 forks source link

Azure Deployment Failed #29

Closed DeanClements closed 5 years ago

DeanClements commented 6 years ago

Hi,

I have tried to use the Deploy to Azure option but receive the Deployment Failed message at the "Updating Website Config" stage the error message is "The current api-version doesn't support RBAC users. please use a newer version instead.(Code: Unauthorised)"

image

Thanks for any help you can provide Dean

jessehouwing commented 6 years ago

Open the solution from the tfsaggregator/tfsaggregator/develop github branch in Visual Studio 15.7, build it and right-click+publish.

On Tue, 7 Aug 2018, 16:51 DeanClements, notifications@github.com wrote:

Hi,

I have tried to use the Deploy to Azure option but receive the Deployment Failed message at the "Updating Website Config" stage the error message is "The current api-version doesn't support RBAC users. please use a newer version instead.(Code: Unauthorised)"

[image: image] https://user-images.githubusercontent.com/31061226/43783458-ac527198-9a59-11e8-903c-afd9f8815e63.png

Thanks for any help you can provide Dean

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tfsaggregator/tfsaggregator-webhooks/issues/29, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS66RdxuidBKfcMIoVp_Dfwo5Q_izks5uOamHgaJpZM4VyUJL .

giuliov commented 6 years ago

when I have an hour I will merge to master and update the README

DeanClements commented 6 years ago

Hi, thank you for your assistance, I have publish the current master branch to Azure, but I receive internal error 500 when I test the service hook from VSTS. hopefully once the current dev branch is merged, I won't have this issue. Thanks Dean

giuliov commented 6 years ago

The test button will always fail because it passes bogus data. I added some ad-hoc checks in the develop branch.

DeanClements commented 6 years ago

Hi, I still get internal 500 error if I actual create a work item in VSTS, as I have the service hook on the workitem create event.

The web.config does have the same username and password as I am passing via the service hook

the detailed error from the log stream of the app is below

HTTP Error 500.0 - Internal Server Error

The page cannot be displayed because an internal server error has occurred.

Most likely causes:

  • IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
  • IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
  • IIS was not able to process configuration for the Web site or application.
  • The authenticated user does not have permission to use this DLL.
  • The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

Things you can try:

  • Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
  • Check the event logs to see if any additional information was logged.
  • Verify the permissions for the DLL.
  • Install the .NET Extensibility feature if the request is mapped to a managed handler.
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

Module   ManagedPipelineHandler
Notification   ExecuteRequestHandler
Handler   System.Web.Http.WebHost.HttpControllerHandler
Error Code   0x00000000
Requested URL   https://FF2tfsaggregator-webhooks09f8:80/api/workitem
Physical Path   D:\home\site\wwwroot\api\workitem
Logon Method   Anonymous
Logon User   Anonymous

More Information:

This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

View more information »

Microsoft Knowledge Base Articles: