Reporting API issue with error code "ServiceAccountNotSet"

Officially Answered

Follow

New post

Asanka Garusinghe

• July 20, 2020 08:07

Hi, 
We've just encountered an issue as mentioned below while consuming "api/odata/TimeExport"  with legacy version ?api-version=2.1  and using Reporting API active token. 

{
"statusCode": 403,
"errorCode": "ServiceAccountNotSet",
"errorDescription": "Service Account is not configured. Please set Service Account in Timetracker settings"
}

I couldn't see any issues on service account and I have set MySelf as Service Account already. This was working last week. but suddenly, this has appeared. any clue? or a suggestion? 

1

• 

  tharindra jayamaha

  • July 21, 2020 10:29

  I have the same problem that following error is getting in API Call. This hold the time exporting of most of our projects as we cannot get Azure DevOps Time logs via 7pace. Great if this can be fixed soon.

   

  {
  "statusCode": 403,
  "errorCode": "ReportingApiIsPreparing",
  "errorDescription": "Reporting API is preparing now. Please try in couple of minutes"
  }

  1

  Comment actions Permalink
• 

  Maxim Shestakov

  • July 21, 2020 13:31

  Hello everyone!

  From the error message provided, I see that you have an issue with the Service Account setup.

  To fix it, please follow this instruction: 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 log in 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 a while). 
  
  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.

  +Tharindra, if this will not help you - please provide your organization name, so we could check what else might be wrong.

  Regards,
  Maxim

  0

  Comment actions Permalink
• 

  Mathew Kitching

  • July 22, 2020 18:16
  • Edited

  Hi Maxim, 

   

  I've been having the same problem as mentioned above. We configured our service account correctly and restarted our reporting. Once we received our new API token, all we've been getting is:

  ```

  {

  "statusCode":403,

  "errorCode":"ReportingApiIsPreparing",

  "errorDescription":"Reporting API is preparing now. Please try in couple of minutes"

  }

  ```

   

  Any help you can provide with this would be very much appreciated.

  Organization name: anagraphgeo

   

  Cheers, 

  Mathew

  0

  Comment actions Permalink
• 

  Maxim Shestakov

  • July 23, 2020 14:05

  Hi Mathew!

  Should be enabled now, please confirm

  Maxim

  0

  Comment actions Permalink
• 

  Mathew Kitching

  • June 06, 2022 14:19

  Hi Maxim, 

  It appears we are having the same problem again.

  Can this be looked into? 

  thanks,

  Mathew

  0

  Comment actions Permalink
• 

  Vanja Pletikosić

  • June 07, 2022 13:33

  Hello Mathew,
  
  Can you please provide us with more details? What exact issue are you seeing and are you seeing any kind of error? When did the issue start?
  
  Best regards,
  Vanja

  0

  Comment actions Permalink
• 

  Mathew Kitching

  • June 07, 2022 13:47

  Hi Vanja,

  It seems after a solid hour the problem resolved itself.

  This is the error we were having after generating a new auth key when our old auth key was suddenly invalidated.

  "statusCode":403,
  
  "errorCode":"ReportingApiIsPreparing",
  
  "errorDescription":"Reporting API is preparing now. Please try in couple of minutes"

  Thanks,

  Mat

  0

  Comment actions Permalink

Please sign in to leave a comment.