- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all!
Been using the product for a long time now, and just today, "search" seemed to have broken. All our endpoints are still visible in the screen and such, but we can no longer "search" for devices. We're on the latest release. Only thing that really stands out is a log file, EmaWebAPILogs\ServerName\2025-11-25.log, that shows...
2025-11-25 16:50:25.1088 [ERROR], Message: Unexpected failure getting endpoint collections from repository., Exception:System.NullReferenceException Object reference not set to an instance of an object. at MeshWebCore.WebApi.Controllers.EndpointsController.<>c__DisplayClass13_0.<GetSummariesCollection>b__0(EndpointSummary r)
Correlated, kinda, to the time I search for a device in the console.
I've rebooted the servers and such, but not really much else to go on. Any thoughts/ponderings?
Thanks!
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Matt-CAH,
Greetings!
We see that you are unable to search the endpoints, though it is available and the issue has been seen from today.
Before we proceed with our analysis, we would like to know a few details asked below:
Please let us know if there was any software or hardware update after which this issue is seen?
Is the search greyed out or just not responding after typing the endpoint that needs to be searched?
Are the endpoints accessible individually from the console, both inband (Hardware manageability) and Out of band (Desktop) modes?
Are none of the endpoints reflected in the search, or are the endpoints belonging to only a specific region or endpoint group unable to search?
Finally please share us the ECT log of one endpoint.
Thanks & Regards
Arun
Intel Customer Support Technician
intel.com/vPro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please let us know if there was any software or hardware update after which this issue is seen? No. It was working in the morning, and then sometime in the middle of the day, it stopped being able to search
Is the search greyed out or just not responding after typing the endpoint that needs to be searched? Search is not greyed out, it just returns no results when searching, for known functional clients. I can SEE clients; 3900 pages of them, but search itself brings back nothing; "No Rows Found"
Are the endpoints accessible individually from the console, both inband (Hardware manageability) and Out of band (Desktop) modes? Yes. I can 'find' one, in the main list of clients, and still connect to them appropriately; both in band (AMT vPro) and just "agent based"
Are none of the endpoints reflected in the search, or are the endpoints belonging to only a specific region or endpoint group unable to search? None whatsoever. I did, for a test, set up a 'new' Endpoint Group, and moved a device to it; it shows up in there, but even if only one agent in the group, search returns "no rows".
ECT Log:
EMAConfigTool.exe --verbose
Unable to communicate with the AMT device. Limited data will be retrieved.
Intel EMA Configuration Tool
Application Version: 1.1.0.183
Scan Date: 11/26/2025 4:08:50 AM
*** Host Computer Information ***
Computer Name: DWXXXXX (Changed due to Serial being present)
Manufacturer: Dell Inc.
Model: Precision 3660
Processor: 13th Gen Intel(R) Core(TM) i9-13900K
Windows Version: Microsoft Windows 11 Pro
BIOS Version: Unknown
UUID: Unknown
*** SMBIOS Information ***
AMT Supported: False
AMT Enabled: False
*** ME Information ***
Version: Unknown
SKU: Unknown
State: None Detected
Control Mode: None
Driver Installed: False
PKI DNS Suffix: Not Found
LMS State: NotPresent
LMS Version: 2512.7.3.0
MicroLMS State: NotPresent
EHBC Enabled: False
Exception in ME: Object reference not set to an instance of an object.
Exception in ME: Object reference not set to an instance of an object.
Pausing before ending process in 3 sec. The duration of this pause can be adjusted using the --delayterm option.
Let me know if anything else is needed! Thanks so much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Matt-CAH,
Thank you for the sharing the details requested.
We see that the ECT is not able to reach the AMT or the endpoint upon which you are running the ECT is not the one with the AMT enabled or a Non AMT machine.
With that, we would request you to try searching the endpoint with the IP address, in the Intel EMA console.
And share the ECT log of a different endpoint which has full AMT on the endpoint.
Thanks & Regards
Arun
Intel Customer Support Technician
intel.com/vPro
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page