Endpoint not showing up in dashboard - curl error 58 for url

johndball
Comes here often

Endpoint not showing up in dashboard - curl error 58 for url

Hi folks,

 

I have three Windows 11 Pro machines that, out of the five machines deployed today, refuse to show up in the dashboard. I've tried numerous/various Meraki MDM installer versions from 3.5.x up to 4.0.0 but nothing seems to work.

Two of the machines were upgrades from 3.8.2 to 4.0.0. One of them is a fresh Windows 11 Pro install directly using 4.0.0.

 

Rolling back from 4.0.0 to a lower version does not fix the issue. It seems that once the 4.0.0 installer makes it ways onto the machine, and if the machine errors out for whatever reason, the Meraki MDM agent never syncs regardless of what installer is used after that. I even manually combed the registry removing entries for Meraki and started back at a lower version of the MDM agent but that didn't help. Not sure if this is server side or what's up.

 

When I originally started this thread, it was one machine, now three machines. I've paused the 4.0.0 deployment across the domain.

 

Upgrade from 3.8.2 to 4.0.0:

2023-12-19 06:57:01.556972 [1644]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 06:58:20.374357 [1644]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 06:58:49.45056 [3172]: ClientManager::check_client_pulse(): client localhost:14 timed out; restarting
2023-12-19 06:58:50.60331 [896]: PutEventsThread: Stop request received, queue depth = 0
2023-12-19 06:58:50.60817 [896]: PutEventsThread: Thread complete
2023-12-19 06:58:50.62242 [11056]: PutEventsThread: Thread running...
2023-12-19 06:58:50.193781 [8932]: TunClient thread [localhost:14], starting up...
2023-12-19 06:59:32.804561 [1644]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 07:00:46.91871 [1644]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 07:00:50.989321 [3172]: ClientManager::check_client_pulse(): client localhost:14 timed out; restarting
2023-12-19 07:00:52.5324 [11056]: PutEventsThread: Stop request received, queue depth = 0
2023-12-19 07:00:52.5723 [11056]: PutEventsThread: Thread complete
2023-12-19 07:00:52.7964 [5616]: PutEventsThread: Thread running...
2023-12-19 07:00:52.120180 [1616]: TunClient thread [localhost:14], starting up...

 

 

Fresh Windows 11 Pro running 4.0.0:

 

2023-12-18 23:00:02.251833 [29968]: 4.0.0 Dec 4 2023 20:53:03
2023-12-18 23:00:02.256279 [29968]: VerifyRegistryKeyType(): Registry value type verification failure: Software\Meraki\EndpointAgent\UUID\(exception=The handle is invalid.)
2023-12-18 23:00:02.277970 [29968]: service_main: version = 4.0.0
2023-12-18 23:00:02.278032 [29968]: service_main: self_path = C:\Program Files\Meraki\Endpoint Agent 4.0.0\m_agent_service.exe
2023-12-18 23:00:02.278056 [29968]: service_main: self_dir = C:\Program Files\Meraki\Endpoint Agent 4.0.0\
2023-12-18 23:00:02.278087 [29968]: service_main: temp_dir = C:\Windows\TEMP\
2023-12-18 23:00:02.278110 [29968]: service_main: secure_temp_directory = C:\ProgramData\Meraki\Endpoint Agent\Temp\
2023-12-18 23:00:02.280839 [29968]: service_main: temp_dir(current_user) = C:\Users\[redacted]\AppData\Local\Temp\
2023-12-18 23:00:02.280879 [29968]: service_main: system root = C:\Windows\
2023-12-18 23:00:02.280903 [29968]: service_main: G::lobal().UUID = [redacted]
2023-12-18 23:00:02.280923 [29968]: service_main: G::lobal().session_id = 17578
2023-12-18 23:00:02.281021 [29968]: service_main: organization_id =
2023-12-18 23:00:02.283483 [29968]: service_main: my etheraddr = [redacted]

2023-12-19 05:32:16.775141 [29968]: fetch_with_client_authentication(): curl error 58 for url https://ios.meraki.com/cf/config?[redacted]
2023-12-19 05:32:16.775297 [29968]: AgentConfig::fetch(): fetch_with_client_authentication() false
2023-12-19 05:33:14.473975 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:34:15.188668 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:34:47.400572 [29968]: fetch_with_client_authentication(): curl error 58 for url https://ios.meraki.com/cf/config?[redacted]
2023-12-19 05:34:47.400837 [29968]: AgentConfig::fetch(): fetch_with_client_authentication() false
2023-12-19 05:35:15.809382 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:36:16.437074 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:37:17.151848 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:38:17.804276 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:39:18.427192 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states
2023-12-19 05:39:58.404164 [29968]: fetch_with_client_authentication(): curl error 58 for url https://ios.meraki.com/cf/config?[redacted]
2023-12-19 05:39:58.404430 [29968]: AgentConfig::fetch(): fetch_with_client_authentication() false
2023-12-19 05:40:19.51132 [30000]: ConnState::sample_win_common(): NOT ASSOCIATED, not getting net states

4 Replies 4
BlakeRichardson
Kind of a big deal
Kind of a big deal

I would open a ticket with support but have you made sure any upstream firewall has the correct ports open to allow the agent to communicate with the dashboard. 

Will do and yes. Everything was fine until I hit 4.0.0 then machines started dropping. I'm up to five machines no longer checking in before the GPO propagation stopped across the test domain.

dlenos
New here

Any  solution to this? I am seeing this now.

johndball
Comes here often

No. I spent a few weeks with support under Meraki Case 11190763. Multiple screen shares, screen shots, and logs later and the engineering folks said "could not reproduce." So... no solution from Cisco Meraki.

 

My solution is to remove all traces of the MDM client, purge Meraki-related files from C:\windows\temp, delete the client from the dashboard, then install version 1.0.98, 3.0.2, 3.8.2, then finally 4.0.0 in that order. I was able to get all of my faulty machines working with this.

 

Meraki support with the engineering folks watched me do this with screenshots and video but they can't get the error in their lab so...

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels