Content API 500 Internal Server Error
Hi Archer Folks!
Wondering if anyone has encountered and overcame a "500 Internal Server Error" when using the Content API (GRC API) and Power BI (or other Business Intelligence tool)? We can connect to most applications just fine, but get the error when connecting to Findings. Here's what it looks like:
Wondering if anyone has a solution or direction on where to go from here. I looked in the logs, but didn't find anything around the time of the error.
Many thanks in advance!
Douglas, I'm scheduled to discuss this very issue with the engineering team tomorrow morning. It may be helpful to learn more about your use case. Can I contact you?
Hi Bodie, thanks for reaching out. Yes, I'd be happy to discuss what we're looking to accomplish. I'll send you a direct message with my contact info. Thanks!
I'm getting this same error using Power BI. Usually happens when the Archer application has many records (Findins, Risks, Loss Events). Did you figure how to solve this?
We upgraded 2 of our non-prod environments to Archer 6.5 P1 and the issue has not surfaced on any of the apps. I'll know on 3/15 if it works in PROD and DEV environments on 6.5 P1. Our issue showed up in DEV, but I couldn't test the other environments until our infrastructure team updated the contentapi directory to anonymous and by that time they already upgraded.
In case you're wondering why we don't upgraded DEV first, it's because if we need to do an emergency package to PROD, Archer doesn't let you package from a higher version to a lower version....so we upgraded INT, then TEST, then PROD, then DEV. Interesting workaround, but it's worked out quite well. This works great for an in-place upgrade...new hardware (side-by-side) installations don't follow that path.
I hope that works for you Andres! I recall seeing Archer 6.5 P2 had additional fixes for the Content API integration in the release notes as well so that might be a better version to use.
I did eventually find out the data reason for my 500 error. There was a user that had been selected in a user/group list field and then deleted from the instance. Until the content was edited and re-saved, the deleted user was still stored in that field. Since deleted users are not displayed in the UI, when I edited the record and re-saved it, the deleted user was removed from the field and the error was resolved for me. I was able to identify affected content records and fields using this SQL query:
c.content_id 'tracking id',
join tblivcontent c on iuc.content_id = c.content_id
join tblmodule m on c.module_id = m.module_id
join tblModuleTranslation mt on m.module_id = mt.module_id
join tblfieldtranslation ft on iuc.field_id = ft.field_id
join tbluser u on iuc.user_id = u.user_id
u.acct_status_id = 99999