MECM (Microsoft Endpoint Configuration Manager) CSD (Client Software Distribution) Discovery Not WorkingIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Attempts to run the MECM Discover and Store Data (REST) subflow fail with error "class java.lang.String cannot be cast to class com.snc.process_flow.stream.InputStreamProxy" After following the steps in KB1817766, the issue remains unresolved. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After checking the MIDserver logs, you will be able to find the following error messages: 2026-03-24 03:16:06-0700 INFO (Gobbling stdout: Powershell is executing against: ldap-XXXXX' -script 'D:\miserver\Prod\ServiceNow MID Server <MIDSERVER_NAME>\agent\scripts\PowerShell\AD\AddUserToGroupCrossDomain.ps1' 'use_mid_service_account' $false -useCred $true -ismid $false -isDiscovery $false -debug $true -logInfo $false -logLevel ') [StreamGobbler:143] Gobbled: </powershell>2026-03-24 03:16:08-0700 DEBUG (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [MIDPowerShellUtils:113] Execution status: success2026-03-24 03:16:08-0700 DEBUG (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [MIDPowerShellUtils:113] Username XXXXXX\XXXX worked!2026-03-24 03:16:09-0700 WARN (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [StandardCredentialsProvider:420] Failed to insert a new credential affinity entry2026-03-24 03:16:09-0700 DEBUG (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [MIDPowerShellUtils:113] Successfully executed AddUserToGroupCrossDomain.ps12026-03-24 03:16:09-0700 INFO (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [ECCSender:242] Enqueuing: D:\miserver\Prod\ServiceNow MID Server <MIDSERVER_NAME>\agent\work\monitors\ECCSender\output_1\ecc_queue.26059d4a33b3f214609fd0ac4f5c7b99.xml2026-03-24 03:16:09-0700 INFO (Worker-Expedited:PowershellProbe-26059d4a33b3f214609fd0ac4f5c7b99) [AWorker:208] Worker completed: Powershell source: ldap-XXXXX time: 0:00:09.8712026-03-24 03:16:09-0700 INFO (ECCSender.1) [ECCSenderCache:555] Sending ecc_queue.XXXXX.xml2026-03-24 03:16:53-0700 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2026-03-24T14:16:53.494Z, stats threads: 109, memory max: 1019.0mb, allocated: 1019.0mb, used: 105.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes2026-03-24 03:17:07-0700 INFO (ECCQueueMonitor.1) [ECCQueueMonitor:418] Received message with timestamp: 2026-03-24 14:17:07. Existing Query window is : 2026-03-24 12:15:58, Updated the query window to: 2026-03-24 12:17:072026-03-24 03:17:07-0700 INFO (Worker-Expedited:IPaaSActionProbe-0b45950aebb3b254befff409bad0cd2e) [AWorker:184] Worker starting: IPaaSActionProbe source: XXXXXX2026-03-24 03:17:07-0700 INFO (ECCQueueMonitor.1) [FileReadWrite:75] Time being written to the file : 17743546270002026-03-24 03:17:07-0700 INFO (Worker-Expedited:IPaaSActionProbe-0b45950aebb3b254befff409bad0cd2e) [MIDSystem:35] contextId=c745950ad5b3b2542944259c51013b29 *** Script: Microsoft Endpoint Configuration Manager spoke: Response received for token request - Error: Login failed. No such host is known (XXXXXX)Error: Login failed. No valid credentials provided (Mechanism level: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt))2026-03-24 03:17:07-0700 ERROR (Worker-Expedited:IPaaSActionProbe-0b45950aebb3b254befff409bad0cd2e) [MidPFLogger:47] IPaaSActionProbe | Http Request authentication failed:Authentication token retrieval failed for Microsoft Endpoint Configuration Manager spoke due to : Invalid credentials. Verify key distribution center, realm and connection URL values.2026-03-24 03:17:07-0700 ERROR (Worker-Expedited:IPaaSActionProbe-0b45950aebb3b254befff409bad0cd2e) [MidPFLogger:47] IPaaSActionProbe | Error encountered executing HTTP request : Http Request authentication failed:Authentication token retrieval failed for Microsoft Endpoint Configuration Manager spoke due to : Invalid credentials. Verify key distribution center, realm and connection URL values.2026-03-24 03:17:07-0700 ERROR (Worker-Expedited:IPaaSActionProbe-0b45950aebb3b254befff409bad0cd2e) [MidPFLogger:47] IPaaSActionProbe | Encountered error executing instruction: OpInstruction{id=22, opClass=com.snc.process_flow.stream.operation.SplitterOperation, io=ReadOnlyDefaultOutputsIo{input={pagination_variable_map=FlowReference{value=s1o.pagination_variable_map}, split_using=StringValue{fValue='JSON'}, stream=FlowReference{value=s2o.response_stream}, pagination_config=FlowReference{value=s3i.pagination_config}, item_path=StringValue{fValue='$.value'}}, output={split_stream=s3o.split_stream, updated_page_variables=s3o.updated_page_variables, __step_status__=s3o.__step_status__}, defaultOutput={}}, name=4465a6f3c35301101fa899XXXX, parentActionId=eb73ea73c353XXXX}java.lang.ClassCastException: class java.lang.String cannot be cast to class com.snc.process_flow.stream.InputStreamProxy (java.lang.String is in module java.base of loader 'bootstrap'; com.snc.process_flow.stream.InputStreamProxy is in unnamed module of loader 'app')at com.snc.process_flow.stream.operation.SplitterOperation.run(SplitterOperation.java:65)at com.snc.process_flow.engine.Operation.run2(Operation.java:90)at com.snc.process_flow.v2.exec.OpRunner.runOperation(OpRunner.java:74) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } MID server is unable to connect to the endpoint with the given credentials. The credentials used to connect to the SCM endpoint are incorrect, which means that the username, password, or any other required authentication details provided do not match what the endpoint expects. As a result, the endpoint is actively rejecting the authentication attempt, preventing the MID server from establishing a successful connection. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Verify the Credentials for the SCCM endpoint that the MID server is connecting to. Use the following KB Article for this if needed:How to troubleshoot MID Server WMI and PowerShell credential issues for Windows Discovery Also for reference: SCCM spoke or Microsoft Endpoint Configuration Manager spoke fails with Authentication issues Double-check that Key Distribution Center (KDC) has been linked to a valid domain controller