Diagnóstico Ophelia / IIS - DWSGDAMON2

Resumen ejecutivo

RAM libre9.56 GB

RAM usada54.44 GB

Procesos w3wp6

Memoria w3wp35524.95 MB

CPU promedio5 %

Disco promedio8.12 %

Conexiones IIS promedio1.67

Roles detectadosOMemory/Cache, IIS Web/API

Servidor: DWSGDAMON2

Fecha generación: 06/11/2026 14:01:19

Processor Queue Length promedio: 0

Disk Queue Length promedio: 0.58

Alertas

Procesos w3wp consumen más de 30 GB: 35524.95 MB

Recomendaciones automáticas

Agrupar por AppPool e identificar los principales consumidores. Validar si hay Web Garden o fugas de memoria.

Top 5 AppPools por memoria

PersonsApi: 34990.56 MB en 1 proceso(s)
NotificationCenterSendApi: 452.25 MB en 1 proceso(s)
ApiLegadas: 21.86 MB en 1 proceso(s)
NotificationCenter: 20.23 MB en 1 proceso(s)
DriveSQL: 20.05 MB en 1 proceso(s)

Información del sistema

CSName	Caption	Version	LastBootUpTime	TotalRAMGB	FreeRAMGB
DWSGDAMON2	Microsoft Windows Server 2019 Standard	10.0.17763	5/23/2026 11:54:47 PM	64	9.56

CPU

Name	NumberOfCores	NumberOfLogicalProcessors	MaxClockSpeed
Intel(R) Xeon(R) Platinum 8268 CPU @ 2.90GHz	12	12	2900
Intel(R) Xeon(R) Platinum 8268 CPU @ 2.90GHz	12	12	2900

Discos

DeviceID	VolumeName	SizeGB	FreeGB	FreePercent
C:		119.4	46.25	38.74
E:	DATA_MONGO	2457.58	300.96	12.25
F:	LOG_MONGO	99.98	62.79	62.8
S:	Spool	389.98	388.32	99.57

w3wp agrupado por Application Pool

AppPool	Procesos	MemoriaTotalMB	MemoriaPromedioMB	MemoriaMaxMB	CpuTotal
PersonsApi	1	34990.56	34990.56	34990.56	1369.44
NotificationCenterSendApi	1	452.25	452.25	452.25	291.33
ApiLegadas	1	21.86	21.86	21.86	0.23
NotificationCenter	1	20.23	20.23	20.23	0.09
DriveSQL	1	20.05	20.05	20.05	0.2
Drive	1	20	20	20	0.12

AppPools con múltiples procesos

No hay datos.

Configuración de Application Pools IIS

AppPool	State	RuntimeVersion	PipelineMode	MaxProcesses	IdleTimeoutMin	IdentityType	StartMode
Drive	Started		Integrated	2	20	ApplicationPoolIdentity	AlwaysRunning
DriveSQL	Started		Integrated	2	20	ApplicationPoolIdentity	AlwaysRunning
.NET v2.0	Started	v2.0	Integrated	1	20	ApplicationPoolIdentity	OnDemand
.NET v2.0 Classic	Started	v2.0	Classic	1	20	ApplicationPoolIdentity	OnDemand
.NET v4.5	Started	v4.0	Integrated	1	20	ApplicationPoolIdentity	OnDemand
.NET v4.5 Classic	Started	v4.0	Classic	1	20	ApplicationPoolIdentity	OnDemand
AgoraApi	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
AgoraMongoToSQL	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
ApiLegadas	Started	v4.0	Integrated	1	20	ApplicationPoolIdentity	AlwaysRunning
Classic .NET AppPool	Started	v2.0	Classic	1	20	ApplicationPoolIdentity	OnDemand
DefaultAppPool	Started	v4.0	Integrated	1	20	ApplicationPoolIdentity	OnDemand
DocumentaryReferencesApi	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
DriveClientSQLMigracion	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
DriveMongoToSQL	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
DriveSqlMongoToSQL	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
MongoToSQL	Started	v4.0	Integrated	1	20	ApplicationPoolIdentity	OnDemand
NotificationCenter	Started		Integrated	1	20	ApplicationPoolIdentity	AlwaysRunning
NotificationCenterPool	Started		Integrated	1	1440	ApplicationPoolIdentity	AlwaysRunning
NotificationCenterSendApi	Started		Integrated	1	20	ApplicationPoolIdentity	AlwaysRunning
PersonsApi	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
SharedDriveApi	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
SharedServicesApi	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand
UnificacionExpedientes	Started		Integrated	1	20	ApplicationPoolIdentity	OnDemand

w3wp por Application Pool - detalle

ProcessId	AppPool	CPU	MemoryMB	PrivateMemoryMB	StartTime
8184	PersonsApi	1369.44	34990.56	35327.54	6/11/2026 11:26:50 AM
27828	NotificationCenterSendApi	291.33	452.25	525.22	6/11/2026 2:30:07 AM
1860	ApiLegadas	0.23	21.86	10.96	6/11/2026 1:48:13 PM
26768	NotificationCenter	0.09	20.23	10.43	6/11/2026 1:50:48 PM
21356	DriveSQL	0.2	20.05	10.45	6/11/2026 1:53:14 PM
21052	Drive	0.12	20	10.39	6/11/2026 1:48:05 PM

Top procesos por memoria

Name	Id	MemoryMB	CPU
w3wp	8184	34990.56	1369.44
mongod	24996	12875.8	98722.5
dsa	5088	606.55	137466.72
w3wp	27828	452.25	291.33
CoreManagementService	4344	247.14	27401.72
DoubleTake	4416	222.14	312387.14
coreServiceShell	4024	218.62	96636.92
explorer	2172	117.1	181.94
SWJobEngineWorker2x64	25240	115.59	96.47
lsass	1484	113.62	10025.38
SWJobEngineWorker2x64	23796	104.72	49.41
powershell	2592	96.4	1.11
ServerManager	22676	93.23	12.06
Registry	264	88.61	56.84
svchost	4164	84.07	84.78
SWJobEngineSvc2	27860	79.9	7064.58
cvd	6708	74.87	27596.97
WmiPrvSE	7544	74.46	29424.69
kntcma	4264	67.19	35320.53
SWJobEngineWorker2	2028	67.04	1.73
svchost	2584	66.05	16499.64
SolarWinds.Orion.LogMgmt.Agent.Plugin	14456	63.32	298.28
dwm	2460	55.64	146.09
Agent.Listener	5520	54.82	71.02
WmiPrvSE	17984	54.09	969

Top procesos por CPU acumulado

Name	Id	CPUAcumulado	MemoryMB
DoubleTake	4416	312387.14	222.14
dsa	5088	137466.72	606.55
mongod	24996	98722.56	12875.8
coreServiceShell	4024	96636.92	218.62
System	4	55869.73	0.13
kntcma	4264	35320.53	67.19
WmiPrvSE	7544	29424.69	74.46
cvd	6708	27596.97	74.87
CoreManagementService	4344	27401.72	247.14
cvfwd	4372	22809.61	19.25
svchost	2584	16499.64	66.05
zabbix_agent2	7284	15416.38	53.51
svchost	2152	14955.8	26.68
nscp	4452	12374.78	23.16
zabbix_agent2	13156	11276.83	42.17
lsass	1484	10025.38	113.62
SWJobEngineSvc2	27860	7064.58	79.9
dsa-wrs-app	15264	4461.17	15.2
services	1476	3363.7	18.12
svchost	14060	2594.22	31.06
svchost	1444	2301.11	10.16
svchost	1228	1446.69	7.58
w3wp	8184	1369.44	34990.56
svchost	2248	1321.59	30.61
svchost	1720	1025.08	22.16

Servicios Ophelia / DigitalWare

Name	DisplayName	State	ProcessId	StartMode	PathName
OMemory	Ophelia Memory Server	Running	4540	Auto	C:\OMemory\OMemory.exe --content-root=C:\OMemory
vstsagent.digitalwareophelia.Imperium-Imperium.DWSGDAMON2	Azure Pipelines Agent (digitalwareophelia.Imperium-Imperium.DWSGDAMON2)	Running	13544	Auto	"C:\azagent\A1\bin\AgentService.exe"

Puertos relevantes Ophelia

LocalAddress	LocalPort	OwningProcess
10.238.99.131	6379	4540
::	8082	4
0.0.0.0	8443	4452

Conexiones TCP por estado

Name	Count
Bound	44
CloseWait	6
Established	176
Listen	74
TimeWait	18

Puertos escuchando

LocalAddress	LocalPort	OwningProcess
::	80	4
0.0.0.0	135	1720
::	135	1720
10.238.99.131	139	4
::	445	4
::	1801	4972
0.0.0.0	1801	4972
::	1920	4264
0.0.0.0	1920	4264
0.0.0.0	2103	4972
::	2103	4972
::	2105	4972
0.0.0.0	2105	4972
::	2107	4972
0.0.0.0	2107	4972
10.238.99.131	3260	2720
0.0.0.0	3389	1912
::	3389	1912
::	3661	4264
0.0.0.0	3661	4264
::	4118	5088
::	5666	4452
0.0.0.0	5666	4452
0.0.0.0	6014	4264
::	6320	4416
::	6325	4
::	6326	4
10.238.99.131	6379	4540
::	8082	4
::	8083	4
::	8084	4
::	8085	4
0.0.0.0	8400	6708
0.0.0.0	8403	4372
0.0.0.0	8443	4452
::	10051	13156
::	12489	4452
0.0.0.0	12489	4452
10.238.99.131	15987	24996
::	30150	7284
::	47001	4
::	49664	1332
0.0.0.0	49664	1332
::	49665	2152
0.0.0.0	49665	2152
0.0.0.0	49666	2548
::	49666	2548
0.0.0.0	49668	1484
::	49668	1484
::	49669	3504
0.0.0.0	49669	3504
::	49671	3932
0.0.0.0	49671	3932
0.0.0.0	57268	6708
0.0.0.0	57321	9720
0.0.0.0	59963	2584
::	59963	2584
::	60779	11016
0.0.0.0	60779	11016
0.0.0.0	62273	4372
::	62276	4372
0.0.0.0	62281	4972
::	62281	4972
0.0.0.0	62292	9356
::	62292	9356
::	62303	4264
0.0.0.0	62304	4264
::	62305	4264
0.0.0.0	62306	4264
127.0.0.1	62311	6708
::	62329	1476
0.0.0.0	62329	1476
::	62350	1484
0.0.0.0	62350	1484

Contadores de rendimiento - muestra 1 minuto

Counter	Min	Max	Average
\\dwsgdamon2\processor(_total)\% processor time	3.83	8.9	5
\\dwsgdamon2\memory\available mbytes	9433	9715	9643.5
\\dwsgdamon2\system\processor queue length	0	0	0
\\dwsgdamon2\physicaldisk(_total)\% disk time	6.9	9.15	8.12
\\dwsgdamon2\physicaldisk(_total)\current disk queue length	0	2	0.58
\\dwsgdamon2\web service(_total)\current connections	1	3	1.67
\\dwsgdamon2\asp.net applications(__total__)\requests/sec	0	0	0

Errores por proveedor

ProviderName	Cantidad
OCS Inventory Service	103
VstsAgentService	14
Microsoft-Windows-RestartManager	1
Microsoft-Windows-IIS-W3SVC-PerfCounters	1
IIS AspNetCore Module V2	1

Errores críticos filtrados

No hay datos.

Errores recientes - Application

TimeCreated	ProviderName	Id	Message
6/11/2026 10:26:04 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/10/2026 10:20:19 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/10/2026 2:20:58 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/10/2026 2:14:22 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/10/2026 10:19:47 AM	VstsAgentService	100	2026-06-10 15:19:47Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/10/2026 6:56:08 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/9/2026 3:18:56 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/9/2026 2:05:22 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/9/2026 8:26:32 AM	IIS AspNetCore Module V2	1007	Application '/LM/W3SVC/3/ROOT/PersonsApi' with physical root 'C:\inetpub\wwwroot\ApiLegadas\PersonsApi\' failed to load coreclr. Exception message: Managed server didn't initialize after 120000 ms.
6/9/2026 7:49:15 AM	VstsAgentService	100	2026-06-09 12:49:15Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/8/2026 8:34:30 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/8/2026 5:47:48 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/7/2026 5:50:23 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/7/2026 6:24:10 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/7/2026 2:11:50 AM	Microsoft-Windows-IIS-W3SVC-PerfCounters	2001	It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.
6/7/2026 2:09:32 AM	VstsAgentService	100	2026-06-07 07:09:32Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/6/2026 12:54:45 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/6/2026 3:06:21 AM	VstsAgentService	100	2026-06-06 08:06:21Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/5/2026 11:34:50 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/5/2026 6:00:40 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/5/2026 3:08:05 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/4/2026 2:57:04 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/4/2026 7:41:58 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/4/2026 3:02:46 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/3/2026 2:52:54 PM	VstsAgentService	100	2026-06-03 19:52:54Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/3/2026 11:30:07 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/3/2026 3:12:03 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/2/2026 10:55:35 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/2/2026 9:35:26 PM	VstsAgentService	100	2026-06-03 02:35:26Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
6/2/2026 9:38:12 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/2/2026 12:50:08 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/1/2026 2:40:30 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
6/1/2026 1:28:31 PM	VstsAgentService	100	2026-06-01 18:28:31Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/31/2026 11:01:43 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/31/2026 7:05:17 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/31/2026 7:04:54 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/31/2026 1:58:11 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 11:41:45 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 11:41:22 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 11:41:00 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 12:14:03 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 9:22:42 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 9:18:37 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 9:18:14 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 9:17:52 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 2:56:28 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 2:29:30 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/28/2026 10:53:14 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/28/2026 4:14:38 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/27/2026 6:55:40 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/27/2026 3:14:14 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/27/2026 8:03:06 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/27/2026 8:02:43 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/27/2026 3:06:54 AM	VstsAgentService	100	2026-05-27 08:06:54Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/26/2026 11:10:18 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/26/2026 11:09:56 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/26/2026 7:33:40 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/26/2026 4:35:28 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/25/2026 6:09:21 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/25/2026 4:16:28 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/25/2026 4:20:13 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 9:09:54 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 5:29:37 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 3:31:28 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 3:02:31 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 2:34:19 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 2:20:49 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 2:18:01 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 2:17:21 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/24/2026 2:15:22 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/23/2026 9:09:43 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/23/2026 6:25:24 PM	VstsAgentService	100	2026-05-23 23:25:24Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/23/2026 5:33:01 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/23/2026 5:25:23 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/23/2026 5:25:00 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/22/2026 2:42:07 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/22/2026 4:39:19 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/21/2026 6:16:25 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/21/2026 5:28:59 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/21/2026 3:51:58 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/20/2026 9:03:28 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/20/2026 4:14:08 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/20/2026 5:11:15 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/20/2026 5:10:52 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/19/2026 7:53:44 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/19/2026 10:30:38 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/19/2026 1:34:43 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/18/2026 10:52:47 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/18/2026 8:42:10 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/18/2026 1:14:50 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/17/2026 3:45:30 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/17/2026 6:34:12 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/17/2026 1:17:31 AM	VstsAgentService	100	2026-05-17 06:17:31Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/17/2026 1:11:24 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/17/2026 1:11:01 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/16/2026 3:12:22 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/16/2026 12:47:34 AM	VstsAgentService	100	2026-05-16 05:47:34Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/15/2026 9:31:05 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 9:22:10 PM	VstsAgentService	100	2026-05-16 02:22:10Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/15/2026 3:19:39 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 3:19:16 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 3:13:28 PM	Microsoft-Windows-RestartManager	10006	Application or service 'Trend Micro Deep Security Agent' could not be shut down.
5/15/2026 11:13:21 AM	VstsAgentService	100	2026-05-15 16:13:21Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/15/2026 10:55:59 AM	VstsAgentService	100	2026-05-15 15:55:59Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
5/15/2026 9:31:01 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 9:30:38 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 7:35:51 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/15/2026 7:00:50 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/14/2026 4:28:01 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/14/2026 7:01:21 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/14/2026 7:00:58 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/13/2026 1:46:52 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/12/2026 9:55:00 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/12/2026 9:54:38 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/12/2026 10:00:43 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/11/2026 5:31:54 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/11/2026 2:58:14 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/10/2026 9:09:12 PM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/10/2026 10:42:20 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/10/2026 6:42:15 AM	OCS Inventory Service	20	Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.

Errores recientes - System

TimeCreated	ProviderName	Id	Message
6/11/2026 12:51:12 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/11/2026 12:51:11 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/9/2026 11:21:55 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/9/2026 10:21:01 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/9/2026 8:28:02 AM	Microsoft-Windows-DistributedCOM	10010	The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
6/9/2026 8:26:57 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/9/2026 7:49:09 AM	Microsoft-Windows-GroupPolicy	1126	Windows was unable to determine whether new Group Policy settings defined by a network administrator should be enforced for this user or computer because this computer's clock is not synchronized with the clock of one of the domain controllers for the domain. Because of this issue, this computer system may not be in compliance with the network administrator’s requirements, and users of this system may not be able to use some functionality on the network. Windows will periodically attempt to retry this operation, and it is possible that either this system or the domain controller will correct the time settings without intervention by an administrator, so the problem will be corrected. If this issue persists for more than an hour, checking the local system's clock settings to ensure they are accurate and are synchronized with the clocks on the network's domain controllers is one way to...
6/9/2026 5:37:21 AM	Volsnap	14	The shadow copies of volume E: were aborted because of an IO failure on volume S:.
6/7/2026 9:13:55 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/7/2026 9:13:55 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/7/2026 9:13:55 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/7/2026 9:13:55 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/7/2026 8:27:53 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
6/3/2026 10:17:21 AM	Microsoft-Windows-DistributedCOM	10010	The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
6/3/2026 10:17:21 AM	Microsoft-Windows-DistributedCOM	10010	The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
6/2/2026 4:50:42 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/2/2026 1:40:33 PM	Microsoft-Windows-DistributedCOM	10010	The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
6/1/2026 4:58:19 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/1/2026 4:49:34 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/1/2026 3:53:53 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
6/1/2026 3:53:47 PM	Service Control Manager	7034	The Zabbix Agent 2 [631853.1.1.CO] service terminated unexpectedly. It has done this 1 time(s).
6/1/2026 3:53:46 PM	Service Control Manager	7000	The Diagnostic System Host service failed to start due to the following error: The paging file is too small for this operation to complete.
6/1/2026 3:53:46 PM	Service Control Manager	7000	The Diagnostic System Host service failed to start due to the following error: Not enough memory resources are available to process this command.
6/1/2026 3:53:46 PM	Service Control Manager	7000	The Diagnostic System Host service failed to start due to the following error: The paging file is too small for this operation to complete.
6/1/2026 3:53:46 PM	Service Control Manager	7000	The Diagnostic System Host service failed to start due to the following error: Not enough memory resources are available to process this command.
5/31/2026 8:54:03 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/31/2026 8:54:03 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/31/2026 8:54:03 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/31/2026 8:54:03 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/31/2026 8:54:03 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/31/2026 8:54:02 PM	Microsoft-Windows-DistributedCOM	10010	The server {3EEF301F-B596-4C0B-BD92-013BEAFCE793} did not register with DCOM within the required timeout.
5/31/2026 8:54:02 PM	Microsoft-Windows-DistributedCOM	10010	The server {3EEF301F-B596-4C0B-BD92-013BEAFCE793} did not register with DCOM within the required timeout.
5/31/2026 1:52:29 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/31/2026 12:51:39 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/28/2026 11:16:44 AM	Microsoft-Windows-DistributedCOM	10010	The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/26/2026 4:49:19 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/26/2026 4:49:18 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/26/2026 4:49:18 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/26/2026 4:49:17 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/26/2026 4:49:17 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:19:58 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:19:57 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:19:57 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:19:57 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:19:57 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/24/2026 12:00:21 AM	Microsoft-Windows-TPM-WMI	1801	Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here. DeviceAttributes: BucketId: BucketConfidenceLevel: UpdateType: For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
5/23/2026 11:55:06 PM	Microsoft-Windows-WinRM	10150	The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. User Action Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: winrm get winrm/config/service Additional Data Listener transport: HTTP Listener address: *
5/23/2026 11:55:06 PM	Microsoft-Windows-WinRM	10150	The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. User Action Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: winrm get winrm/config/service Additional Data Listener transport: HTTP Listener address: *
5/23/2026 11:55:05 PM	Service Control Manager	7000	The luafv service failed to start due to the following error: This driver has been blocked from loading
5/23/2026 11:54:26 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:54:26 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:54:26 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:54:26 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:39:16 PM	Microsoft-Windows-TPM-WMI	1801	Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here. DeviceAttributes: BucketId: BucketConfidenceLevel: UpdateType: For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
5/23/2026 11:34:14 PM	Microsoft-Windows-WinRM	10150	The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. User Action Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: winrm get winrm/config/service Additional Data Listener transport: HTTP Listener address: *
5/23/2026 11:34:14 PM	Microsoft-Windows-WinRM	10150	The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. User Action Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: winrm get winrm/config/service Additional Data Listener transport: HTTP Listener address: *
5/23/2026 11:34:13 PM	Service Control Manager	7000	The luafv service failed to start due to the following error: This driver has been blocked from loading
5/23/2026 11:33:29 PM	Service Control Manager	7034	The Zabbix Agent 2 service terminated unexpectedly. It has done this 1 time(s).
5/23/2026 11:33:28 PM	Service Control Manager	7043	The Double-Take service did not shut down properly after receiving a preshutdown control.
5/23/2026 11:31:50 PM	Service Control Manager	7023	The Update Orchestrator Service service terminated with the following error: This operation returned because the timeout period expired.
5/23/2026 11:31:47 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:31:47 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:31:47 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/23/2026 11:31:46 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 9:32:33 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 9:32:33 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 9:32:33 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 9:32:33 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 9:32:32 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 8:34:15 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 8:34:15 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 8:34:15 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 8:34:15 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/22/2026 8:34:14 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/21/2026 11:09:06 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/21/2026 5:20:13 PM	Microsoft-Windows-DistributedCOM	10010	The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/19/2026 7:34:35 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/19/2026 7:34:34 PM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/17/2026 12:03:40 PM	Service Control Manager	7032	The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the MongoDB Server (MongoDB6) service, but this action failed with the following error: An instance of the service is already running.
5/17/2026 12:02:40 PM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 6:15:08 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/17/2026 6:15:07 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/17/2026 6:15:07 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/17/2026 6:15:07 AM	Microsoft-Windows-DistributedCOM	10001	Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding
5/17/2026 3:40:06 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:39:02 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:37:59 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:36:55 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:35:52 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:34:49 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:33:45 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:32:42 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:31:38 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:30:35 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:29:31 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:28:28 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:27:25 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:26:21 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:25:18 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:24:14 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:23:11 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:22:08 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:21:04 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:20:01 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:18:57 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:17:54 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:16:50 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:15:47 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:14:43 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:13:40 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:12:37 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:11:33 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:10:30 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:09:27 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:08:23 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:07:20 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:06:16 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:05:13 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:04:10 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
5/17/2026 3:03:07 AM	Service Control Manager	7031	The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.