TimeExport - 500 Internal Server Error

Gathering Feedback

Follow

New post

Bennie Forss

• November 04, 2020 20:53

We have had problem with TimeExport for a time now. 

{

    "statusCode": 500,

    "errorCode": "UnexpectedError",

    "errorDescription": "Unexpected error occurred",

    "fields": {

        "originalMessage": "An internal error occurred while getting report data.",

        "originalStacktrace": "   at Timetracker.Web.Controllers.Api.v2._1.TimeEntryExportFuncController.GetTimeExport(String startDate, String endDate, Nullable`1 populateTopParentColumns, Nullable`1 groupTimeByDateByUser, Nullable`1 includeBillable) in C:\\builds\\agent-1\\_work\\8\\s\\TimetrackerOnline\\TimetrackerOnline.Web\\Controllers\\Api\\v2.1\\TimeEntryExportController.cs:line 77\r\n   at lambda_method(Closure , Object , Object[] )\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Logged|12_1(ControllerActionInvoker invoker)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)\r\n   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)\r\n   at AspNetCoreRateLimit.RateLimitMiddleware`1.Invoke(HttpContext context)\r\n   at Timetracker.Web.Middleware.ApiMiddleware.ApiErrorWrapperMiddleware.InvokeCore(HttpContext context, IApiErrorWrapper errorWrapper) in C:\\builds\\agent-1\\_work\\8\\s\\TimetrackerOnline\\TimetrackerOnline.Web\\Middleware\\ApiMiddleware\\ApiErrorWrapperMiddleware.cs:line 49"

    }

}

1

• 

  dev

  • November 05, 2020 09:11

  Hello Bennie,
  
  Thank you for reaching out to us regarding this issue. Our apologies for the issue you are experiencing. 
  
  We believe that your Service Account may have lost authorization. In order to confirm and fix this, whoever is the project collection admin who is assigned to the role of Service Account within your organization (you can see this under Timetracker "Settings" -> Service Account) should login and open any Timetracker page. They will see a yellow banner at a top of any Timetracker page asking them to re-authorize; please click "Authorize" and proceed as described in the banner. 
  
  Next, please navigate to Timetracker "Settings" -> "Reporting and REST API", and click "Restart Reporting" (this may take awhile). 
  
  Once complete, please issue a new token for the API "(Create New Token") and your issue should be resolved.
  
  Please let us know if this helps.
  
  Best regards,
  Vanja

  0

  Comment actions Permalink
• 

  Magnus Axelsson

  • November 17, 2020 08:51

  Hi again, we have done the above, and after an email dialog to support@7pace.com been able to authorize again. 

  But the problem comes back several times a week now. 

  We have had the service running flawless about a year but are now experience a lot of lost authorizations. 
  We constantly need to, restart the report serivce, reauthorize via the top banner when the 7pace api stops working. 

  What could cause this problem? 

  0

  Comment actions Permalink
• 

  Vanja Pletikosić

  • November 17, 2020 11:27

  Hello Magnus,
  
  Thank you for getting back to us. At this point we would like to suggest that you use the Personal Access Token authentication method, instead of OAuth.
  OAuth may be a more seamless, short-term method in that the token refreshes itself automatically and frequently. The only potential drawback may occur if something goes wrong during the refresh tokens process, which will render your token unusable and will require you to issue it again. With the Personal Access Token method of authorization, you have to manually reissue the token, but it remains valid for a period of up to one (1) year.
  
  Please follow the steps below in order In order to enable PAT authentication, please follow the steps outlined below:
  
  

  1. Open the 7pace Timetracker "Monthly" page under your Service Account - you should see a yellow warning message, prompting you to Authorize.
  2. Click "Authorize"​​
  3. Switch to the "Use Personal Access Token" tab and follow the on-screen instructions to Authorize by PAT.
     

  
  Please let me know if you have any questions regarding this.
  
  
  Best regards,
  Vanja

  0

  Comment actions Permalink
• 

  Magnus Axelsson

  • November 18, 2020 08:09

  Today everything seems to be upp and running. So I don't get any warnings and another opportunity to log in. 

  Is there a way for me to log out of the OAuth in 7pace so that I can login with a personal token instead? 

  To be clear, I'm not developing, just managing 7pace settings. I'm also set as the Servie Account. Last week I did authourize with OAuth. 
  We do have two developers working with the API. They seem to have personal access tokens. I can vefiry that in DevOps->7pace->settings->Access Tokens. The tokens are valid. 
  
  We only have one intranet page showing 7pace data. This one is the one constantly loosing its API auth and stop showing 7pace data. 

  Does it matter how I, set as a Service Account authorize? Does my service account need to be working/authirized for the web page and developers API?  

  Last question: is the web page authorizing with one of the developers personal tokens? Just curious if we need to re-authorize the web page if our staff is changing his token? 

  Btw, all your documentation links are broken ;-)
  
  

  0

  Comment actions Permalink
• 

  Vanja Pletikosić

  • November 18, 2020 15:47
  • Edited

  Hello Magnus,

   

  If you wish to revoke the current OAuth authorization please follow these steps:

  1. Navigate to https://app.vsaex.visualstudio.com/me?mkt=en-us&workflowID=devprogram 
  2. Once there, click on "Manage authorizations".
  3. Look for the application called "7pace Timetracker" and revoke the authorization (press "delete" icon).
  4. Once it is revoked navigate to the "Monthly" tab and you should get a yellow prompt saying that you need to authorize Timetracker.

   

  The main thing that you need to ensure for the Service Account is that it needs to be a Project Collection Administrator in DevOps.

  When it comes to the tokens you are seeing under DevOps -> 7pace -> Settings -> Access Tokens - these are Timetracker tokens used to access the Timetracker API.

  The Personal Access Token (PAT) is the token which allows the Timetracker API to interact with the DevOps API and it is issued in the DevOps UI.

  The API and Reporting is based on the data that is requested and processed by the Service Account, so yes it should be authorized and working.

  Regarding your last question, no additional actions would need to be taken in such a scenario.
  
  And thank you for the heads up about the broken links, they should be working now, please give it a try.
  
  
  Please let me know if this helps.
  
  Best regards,
  Vanja

   

   

  0

  Comment actions Permalink
• 

  Magnus Axelsson

  • November 26, 2020 14:48

  I belive it did solve our problems - have been running smooth now for a week.

   

  Thank you! 

  0

  Comment actions Permalink

Please sign in to leave a comment.