Skip to main content
Solved

Error using Automox Custom API Dashboard through PowerBI

  • January 22, 2025
  • 5 replies
  • 72 views
V
Forum|alt.badge.img

Hello,

 

I am trying to follow the Automox/PowerBi guide here: https://help.automox.com/hc/en-us/articles/8180172309780-Custom-API-Dashboard-through-PowerBI#h_01HAT7WZ8E95S0YA6E8FCYVY5B but running into an issue on step #6 (Double click to open Automox_Reports_Example_v1_wAPI.pbit from C:\temp\.).

 

When I do this, PowerBI states “query is blocked by the following errors: health, The column 'name' of the table wasn't found.” 

 

Due to this, all the PowerBI report pages are blank as the rest of the queries don’t load. When opening up health.csv, I see that it is empty. 

 

Any thoughts? 

Best answer by KyleG-Automox

Thank you!

 

It looks like you’re getting a 404 error when trying to run the script. This could potentially indicate a few issues:

 

  1. The API Key provided is invalid, expired, or in an incorrect format.
  2. The OrgID provided is incorrect.
  3. The device is having difficulty resolving console.automox.com 

I was able to replicate the 404 error in Powershell ISE using a correct API Key but incorrect OrgID. Here are the next steps you can take:

  1. Ensure your OrgID is from the same Zone the API Key is from. You can find your OrgID in your Automox Console URL (o=XXXXXX).
  2. Try running this script via Powershell ISE 64-bit or VSCode running Powershell and see if the result is different.

 

If none of these work I recommend submitting a ticket to help.automox.com. Since the API script has sensitive data (API and OrgID) we wouldn’t want to enter the data here, however our Support team can help you look at this.

 

If you have any further questions please let me know!

View original
How helpful was this post to you?

5 replies

K
  • KyleG-Automox
  • Automox Employee
  • 29 replies
  • January 28, 2025

Hey villagegybe

 

Thanks for reaching out!

 

I just tested the PowerBI template and script on a Windows 11 device against an Org with 200+ devices and did not encounter the issue you mentioned in your post.

 

Just to confirm your C:\Temp folder looks like this before running the PS script:

 

Your GrabAXAPIData.ps1 file looks like this (Note that the API Key and OrgID will be unique to your Automox Org):

 

Leaving your final output to look like this:

 

 

If this all looks correct, next step would be to bring the GrabAXAPIData.ps1 script into Powershell ISE (x64) and run it there. This will help identify any errors in the Powershell script output in the bottom text box.

 

Any errors you encounter you’re unfamiliar with you can reply to this post. Alternatively, you can submit a support case to help.automox.com for assistance as well.

 

If you have any further questions please let me know!

V
Forum|alt.badge.img
  • villagegybe
  • Author
  • Rookie
  • 2 replies
  • January 28, 2025
KyleG-Automox wrote:

Hey villagegybe

 

Thanks for reaching out!

 

I just tested the PowerBI template and script on a Windows 11 device against an Org with 200+ devices and did not encounter the issue you mentioned in your post.

 

Just to confirm your C:\Temp folder looks like this before running the PS script:

 

Your GrabAXAPIData.ps1 file looks like this (Note that the API Key and OrgID will be unique to your Automox Org):

 

Leaving your final output to look like this:

 

 

If this all looks correct, next step would be to bring the GrabAXAPIData.ps1 script into Powershell ISE (x64) and run it there. This will help identify any errors in the Powershell script output in the bottom text box.

 

Any errors you encounter you’re unfamiliar with you can reply to this post. Alternatively, you can submit a support case to help.automox.com for assistance as well.

 

If you have any further questions please let me know!

 

Hi Kyle,

 

Thanks for the help. I have verified that my Temp folder and PS file are correct.

 

Output of Powershell ISE is as follows:

 

K
  • KyleG-Automox
  • Automox Employee
  • 29 replies
  • Answer
  • January 28, 2025

Thank you!

 

It looks like you’re getting a 404 error when trying to run the script. This could potentially indicate a few issues:

 

  1. The API Key provided is invalid, expired, or in an incorrect format.
  2. The OrgID provided is incorrect.
  3. The device is having difficulty resolving console.automox.com 

I was able to replicate the 404 error in Powershell ISE using a correct API Key but incorrect OrgID. Here are the next steps you can take:

  1. Ensure your OrgID is from the same Zone the API Key is from. You can find your OrgID in your Automox Console URL (o=XXXXXX).
  2. Try running this script via Powershell ISE 64-bit or VSCode running Powershell and see if the result is different.

 

If none of these work I recommend submitting a ticket to help.automox.com. Since the API script has sensitive data (API and OrgID) we wouldn’t want to enter the data here, however our Support team can help you look at this.

 

If you have any further questions please let me know!

V
Forum|alt.badge.img
  • villagegybe
  • Author
  • Rookie
  • 2 replies
  • January 29, 2025
KyleG-Automox wrote:

Thank you!

 

It looks like you’re getting a 404 error when trying to run the script. This could potentially indicate a few issues:

 

  1. The API Key provided is invalid, expired, or in an incorrect format.
  2. The OrgID provided is incorrect.
  3. The device is having difficulty resolving console.automox.com 

I was able to replicate the 404 error in Powershell ISE using a correct API Key but incorrect OrgID. Here are the next steps you can take:

  1. Ensure your OrgID is from the same Zone the API Key is from. You can find your OrgID in your Automox Console URL (o=XXXXXX).
  2. Try running this script via Powershell ISE 64-bit or VSCode running Powershell and see if the result is different.

 

If none of these work I recommend submitting a ticket to help.automox.com. Since the API script has sensitive data (API and OrgID) we wouldn’t want to enter the data here, however our Support team can help you look at this.

 

If you have any further questions please let me know!

 

Hi Kyle,

 

Thanks for working with me, got it up and running. Your point #2, Org ID being incorrect, was the issue. I used the Automox account ID value instead of org ID. 

 

Two other follow-ups now that we have this running:

 

  1. I’m using the API key for “MyCompany”-workstations currently. Does this integration support having “MyCompany”-servers as well, which I’m assuming I would need to generate another API key for? It would be nice to not have two separate PBI dashboards. 
  2. Am I able to drill deeper into this data, or it it best to pivot into the console? For example, with the below, how can I figure out what this one device is?

    1.  

K
  • KyleG-Automox
  • Automox Employee
  • 29 replies
  • January 29, 2025
villagegybe wrote:
KyleG-Automox wrote:

Thank you!

 

It looks like you’re getting a 404 error when trying to run the script. This could potentially indicate a few issues:

 

  1. The API Key provided is invalid, expired, or in an incorrect format.
  2. The OrgID provided is incorrect.
  3. The device is having difficulty resolving console.automox.com 

I was able to replicate the 404 error in Powershell ISE using a correct API Key but incorrect OrgID. Here are the next steps you can take:

  1. Ensure your OrgID is from the same Zone the API Key is from. You can find your OrgID in your Automox Console URL (o=XXXXXX).
  2. Try running this script via Powershell ISE 64-bit or VSCode running Powershell and see if the result is different.

 

If none of these work I recommend submitting a ticket to help.automox.com. Since the API script has sensitive data (API and OrgID) we wouldn’t want to enter the data here, however our Support team can help you look at this.

 

If you have any further questions please let me know!

 

Hi Kyle,

 

Thanks for working with me, got it up and running. Your point #2, Org ID being incorrect, was the issue. I used the Automox account ID value instead of org ID. 

 

Two other follow-ups now that we have this running:

 

  1. I’m using the API key for “MyCompany”-workstations currently. Does this integration support having “MyCompany”-servers as well, which I’m assuming I would need to generate another API key for? It would be nice to not have two separate PBI dashboards. 
  2. Am I able to drill deeper into this data, or it it best to pivot into the console? For example, with the below, how can I figure out what this one device is?

    1.  

 

 

Fantastic! Very happy to hear it works now.

 

To answer your additional questions:

 

  1. The PowerBI template’s current state is single Org only. In the Powershell scripts current state there is no loop for multiple Orgs, however something like a Foreach loop with the OrgIDs could be added if you have Powershell experience. Bare in mind while the script may pull the data properly, its not guaranteed all the PowerBI tabs will support the data from all Orgs.
  2. The script is hardcoded to pull a number of patches and not a list at this time. You can verify this in the PolicyStates json file.

 

There’s are great questions! I will be sure to provide them to the team as suggestions for future enhancements.

 

Please let me know if you have any other questions!

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings