Mobile Devices - Internal Server Error (500)

[robjschroeder]

I'm getting the following error when trying to refresh data on the Mobile Devices endpoint. I've tried in multiple reports and jamf instances. These were all previously working, but has since started failing. I've created new reports with new connects, and I am getting the same errors. Mobile Devices is the only endpoint that I am having issues with. Below is the error when trying to refresh:

OLE DB or ODBC error: [DataSource.Error] Web.Contents failed to get contents from 'https://myJamfServer.jamfcloud.com/api/v2/mobile-devices/detail?page-size=100&page=1&section=GENERAL&section=HARDWARE&section=USER_AND_LOCATION&section=SECURITY&section=NETWORK&section=PURCHASING&sort=mobileDeviceId' (500): Internal Server Error.

[lukecater]

I'm getting the following error when trying to refresh data on the Mobile Devices endpoint. I've tried in multiple reports and jamf instances. These were all previously working, but has since started failing. I've created new reports with new connects, and I am getting the same errors. Mobile Devices is the only endpoint that I am having issues with. Below is the error when trying to refresh:

OLE DB or ODBC error: [DataSource.Error] Web.Contents failed to get contents from 'https://myJamfServer.jamfcloud.com/api/v2/mobile-devices/detail?page-size=100&page=1&section=GENERAL&section=HARDWARE&section=USER_AND_LOCATION&section=SECURITY&section=NETWORK&section=PURCHASING&sort=mobileDeviceId' (500): Internal Server Error.

I am experiencing a similar issue. The connector functions correctly when mobile devices table is excluded from the navigator.
I experimented with the pq file. On line 421, I changed the value of url, {“GENERAL”, “HARDWARE”, “USER_AND_LOCATION”, “SECURITY”, “NETWORK”, “PURCHASING”}, _ to url, {“GENERAL”, “APPLICATIONS”, “HARDWARE”, “USER_AND_LOCATION”}, _.
This change resulted in the connector loading on the desktop version of Power BI, but it still encountered the issue when published and attempted to refresh on the web.

[jfretheim]

Hi @robjschroeder and @lukecater--thanks for reporting the details on this (and potential workaround solution with changes to the section params in the URL).

If you're both encountering a 500 Server Error response from Jamf Pro, let's have a look at the stack trace in the Jamf Pro log for when this occurs. It isn't an error I've encountered, but there may be something different about my test environment that does not trigger the same Jamf Pro server error.

Another note about testing changes to the connector in the cloud vs. Desktop Power BI: in addition to publishing the model to Microsoft's powerbi.com, you'll need to set up Microsoft's "On-Premises Data Gateway" so the code you have written locally is executed on refresh. I have some notes about how to do that on this discussion: #33 (see the section on Testing -> powerbi.com for details).

[lukecater]

Hi @robjschroeder and @lukecater--thanks for reporting the details on this (and potential workaround solution with changes to the section params in the URL).

If you're both encountering a 500 Server Error response from Jamf Pro, let's have a look at the stack trace in the Jamf Pro log for when this occurs. It isn't an error I've encountered, but there may be something different about my test environment that does not trigger the same Jamf Pro server error.

Another note about testing changes to the connector in the cloud vs. Desktop Power BI: in addition to publishing the model to Microsoft's powerbi.com, you'll need to set up Microsoft's "On-Premises Data Gateway" so the code you have written locally is executed on refresh. I have some notes about how to do that on this discussion: #33 (see the section on Testing -> powerbi.com for details).

Thanks @jfretheim, I do have a ticket over at Jamf and they asked for debugged server logs. They said they will send them over.

[jfretheim]

Thanks @lukecater - your support specialist sent them over and I believe this should be resolved with the release of Jamf Pro 11.21.1, which is (coincidentally) imminent. You can check the cloud upgrade schedule for specific timing. The specific product issue that aligns with your case is PI141237.

Please let me know if the issue is resolved after your Jamf Pro instance is running 11.21.1 or later.

As for @robjschroeder - can you let me know if the same fix works for your case? If not, let's track down the stack trace in your Jamf Pro logs and diagnose.

[lukecater]

@jfretheim, Yes, after the update (11.21.1-t1759758255666), mobile devices and all the other tables connect successfully.

[jfretheim]

@jfretheim, Yes, after the update (11.21.1-t1759758255666), mobile devices and all the other tables connect successfully.

Ah, that's great news. Thanks for following up, @lukecater.

I'll leave this issue open for now to track @robjschroeder's issue in case it has a different root cause.