Error in parsing - Input string was not in a correct format

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

12/19/2025 09:07:11 : RpcHandler [ Thread-7 ] DEBUG : “ENTER Close”
12/19/2025 09:07:11 : RpcHandler [ Thread-7 ] DEBUG : “EXIT Close”
12/19/2025 09:07:13 : RpcServer [ Thread-6 ] DEBUG : “listening on port : 5050”
12/19/2025 09:07:13 : RpcServer [ Thread-6 ] DEBUG : “Execution registry has [0] items.”
12/19/2025 09:07:13 : KeyStore [ Thread-6 ] DEBUG : “FLAGS: UseMachineKeyStore, UseExistingKey”
12/19/2025 09:07:13 : KeyStore [ Thread-6 ] DEBUG : “KEY CONTAINER NAME: IQService Transmission Keys5050”
12/19/2025 09:07:13 : KeyStore [ Thread-6 ] DEBUG : “DEBUG – Existing RSA key not found, using default key.”
12/19/2025 09:07:13 : RpcServer [ Thread-3 ] DEBUG : “New Connection…”
12/19/2025 09:07:13 : RpcServer [ Thread-6 ] DEBUG : “New Listener Thread Created…”
12/19/2025 09:07:17 : RpcHandler [ Thread-4 ] ERROR : “Malformed request received from client - ::ffff:168.63.129.16:49309. Received header length as - Error in parsing - Input string was not in a correct format.”
12/19/2025 09:07:17 : RpcHandler [ Thread-4 ] INFO : "OutgoingResponse:

<?xml version="1.0" encoding="utf-8"?> Malformed request received. "
2

Hi @kmohankumar, could you please give us more info on this issue? For which AD attribute you are seeing this issue? Is this happening during account creation?

3

This error we are seeing continuously in the IQservice log file , Even with out any operation , our IQservice log is continuously getting this error

4

Hi @kmohankumar,

Can you verify if all the IQService configs are correct in ISC ?

5

Mohan Koribilli: This could be cause of this issue. I have not faced this kind of issue.

Why it happens “even without any operation”

Because it’s not triggered by provisioning.It’s triggered by infrastructure checks (health probe / monitoring / scanner) that run on a schedule.

Azure’s health probes often show up as 168.63.129.16 in logs

Option A (most common): If IQService VM is behind an Azure Load Balancer. correct it port numbers