Investigating 404 Error using ControlUp Edge DX API for Device List

A user encountered a 404 error when using the API to call a script against a device list. A Network check script was supplied which could address the 414 devices before it broke, with 1 per device ID specified. The issue was discovered to be due to a machine having an altered Device ID within 3 minutes. The EdgeDX API URLs mentioned in the message were ‘Global-EdgeDX Download Manager’ = ‘downloads.sip.controlup.com’, ‘Global-EdgeDX tenant’ = "$edgetenant.sip.controlup.com" and ‘Global-Google Maps’ = ‘maps.google.com’.

Read the entire ‘Investigating 404 Error using EdgeDX API for Device List’ thread below:

while using the API to call a script to run against a device list…

i have 2908 devices and get to just over 400 and it stops with a 404 error. Is there a rate limit now or active issue?

FullyQualifiedErrorId : There was an error accessing the EdgeDX API:

The remote server returned an error: (404) Not Found.

there is a powershell script to check network connectivity: Network_Check_V7.ps1

Not sure where i found it butit checks:

“`$URLs_EdgeDX=@{

‘Global-EdgeDX Download Manager’ = ‘downloads.sip.controlup.com‘

‘Global-EdgeDX tenant’ = "$edgetenant.sip.controlup.com"

‘Global-Google Maps’ = ‘maps.google.com‘“`

it works for the first 414 devices

this time i got 320 done before it broke

Are you invoking the action API one at a time for each device or are you passing multiple devices in each call?

1 per device id

so i have dig into it and found that is currently 1 certain machine. 5 days ago it reported in as somethign was installed. I am consuming that custom report which includes the device id. however 3 days ago that machine changed it’s device id.

so i’m basically calling a bogus device id. i’m not sure how it changed device IDs inside 3 mins but it did.

Continue reading and comment on the thread ‘Investigating 404 Error using ControlUp Edge DX API for Device List’.  Not a member? Join Here!