Diagnóstico Ophelia / IIS - DWSGDAAPP1

Resumen ejecutivo

RAM libre31.37 GB
RAM usada32.63 GB
Procesos w3wp75
Memoria w3wp24726.28 MB
CPU promedio12.94 %
Disco promedio24.84 %
Conexiones IIS promedio5.42
Roles detectadosOMemory/Cache, BPMTimer, Orion BPM, IIS Web/API

Servidor: DWSGDAAPP1

Fecha generación: 05/31/2026 14:01:21

Processor Queue Length promedio: 0

Disk Queue Length promedio: 0.92

Alertas

Recomendaciones automáticas

Top 5 AppPools por memoria

Información del sistema

CSNameCaptionVersionLastBootUpTimeTotalRAMGBFreeRAMGB
DWSGDAAPP1Microsoft Windows Server 2019 Standard10.0.177635/23/2026 11:18:01 PM6431.37

CPU

NameNumberOfCoresNumberOfLogicalProcessorsMaxClockSpeed
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394
Intel(R) Xeon(R) CPU E5-2699A v4 @ 2.40GHz222394

Discos

DeviceIDVolumeNameSizeGBFreeGBFreePercent
C:149.430.620.49
D:APP249.9863.2325.29
S:Spool59.9859.8899.82

w3wp agrupado por Application Pool

AppPoolProcesosMemoriaTotalMBMemoriaPromedioMBMemoriaMaxMBCpuTotal
ReportingCore12619.52619.52619.5426.81
ApoloApi42517.66629.42651.61101.36
AgoraApi32373.85791.281186.7468.13
ApoloApiBPM21308.17654.08656.4259.31
RequestFileApi2861.55430.78450.7631.94
DMSMailService1717.75717.75717.7524.53
BPMApi1634.51634.51634.5180.48
AgoraApiRequestFile1626.11626.11626.1163.53
WSApiBPM1613.89613.89613.8968.09
NotificationCenterCheckEmailApi1594.64594.64594.6445.23
ApoloBpmMinimalGetConfig1573.21573.21573.2147.73
RadicateApiNew_EF1541.64541.64541.6411.91
ApoloMinimalApiBpmGetTemplateDataLite1512.78512.78512.7857.41
SharedServicesApi2495.93247.96475.399.65
CoreBI1488.72488.72488.7217.08
AuditorApi3479.02159.67167.4714.85
DMSInventoryStorageLoad1439.74439.74439.7412.19
AgoraApiApolo1433.59433.59433.5919.7
ApoloUpdateBpmMinimal1428.56428.56428.5614.91
Hades1402.1402.1402.139.09
ApoloApiRequestFile1386.59386.59386.5917.56
SharedDriveApi1363.2363.2363.2529.77
DocumentaryReferencesApi2347.73173.86327.1823.27
ApoloApiDms1344.75344.75344.7518.34
DriveSQL1335.88335.88335.8875.08
SGDEAPortal.ReassignTask.Api1331.62331.62331.6222.61
ProcessTable1330.41330.41330.4140.83
BPM.BeginProcess1329.58329.58329.589.61
AgoraApiDms1280.11280.11280.1114.58
AgoraApiBPM1279.13279.13279.1316.64
NotificationCenter1268.9268.9268.927.12
NotificationCenterBPM1258.86258.86258.8645.58
WSApi1225.86225.86225.8636.41
LoanApi1217.16217.16217.1618.39
ApoloInitializateBpmMinimal1196.65196.65196.655.25
DMSDrafDocumentApi1182.98182.98182.987.94
DMS1173.5173.5173.58.11
ImperiumQueryApi1158.98158.98158.9823.12
OpheliaDiretoryActive1148.93148.93148.9329.22
ArtemisApi3139.9646.6599.0210.33
DMSApiRequestFile1119.54119.54119.542.44
ImportacionCCD1116.75116.75116.7563.92
NotificationCenterCheckEmailApiV21115.27115.27115.278.94
DMSCommonsApi2115.2657.6394.754.92
ChatApi1113.54113.54113.5412.31
_c_HefestoApi1109.78109.78109.7814.38
FTPApi1109.1109.1109.138.47
BPMApiRadicadoWeb1105.7105.7105.715.44
RadicateApi1105.26105.26105.265.84
SGDEAPortalApi1101.05101.05101.0516.5
BPM.Api.FinishTracking193.0493.0493.042.19
SharedDriveApiV2Payments186.8186.8186.8110.56
Api472185.0785.0785.0713.28
TaskbarV2184.1584.1584.1514.02
IntegrantionApi183.5583.5583.5511.77
SchedelerApi175.3275.3275.322.98
OpheliaSuiteV2155.255.255.211
RequestFileUpdateStateApi123.423.423.40.61
Apolo121.8521.8521.851.7
NotificationCenterClientCheckEmails121.5721.5721.571.48
DMSRequestFile121.3721.3721.370.98

AppPools con múltiples procesos

AppPoolProcesosMemoriaTotalMBMemoriaPromedioMBMemoriaMaxMBCpuTotal
ApoloApi42517.66629.42651.61101.36
AgoraApi32373.85791.281186.7468.13
AuditorApi3479.02159.67167.4714.85
ArtemisApi3139.9646.6599.0210.33
ApoloApiBPM21308.17654.08656.4259.31
RequestFileApi2861.55430.78450.7631.94
SharedServicesApi2495.93247.96475.399.65
DocumentaryReferencesApi2347.73173.86327.1823.27
DMSCommonsApi2115.2657.6394.754.92

Configuración de Application Pools IIS

AppPoolStateRuntimeVersionPipelineModeMaxProcessesIdleTimeoutMinIdentityTypeStartMode
ApoloApiStartedIntegrated420ApplicationPoolIdentityOnDemand
AgoraApiStartedIntegrated320ApplicationPoolIdentityAlwaysRunning
ArtemisApiStartedIntegrated320ApplicationPoolIdentityOnDemand
AuditorApiStartedIntegrated320ApplicationPoolIdentityOnDemand
DMSStartedIntegrated320ApplicationPoolIdentityAlwaysRunning
DMSApiWebStartedIntegrated320ApplicationPoolIdentityOnDemand
DMSWebFormEntryStartedv4.0Integrated320ApplicationPoolIdentityOnDemand
DMSWebFormExitStartedv4.0Integrated320ApplicationPoolIdentityOnDemand
ApoloApiBPMStartedIntegrated220SpecificUserOnDemand
DMSCommonsApiStartedIntegrated220ApplicationPoolIdentityOnDemand
DocumentaryReferencesApiStartedIntegrated220ApplicationPoolIdentityOnDemand
RadicateApiStartedIntegrated220ApplicationPoolIdentityOnDemand
RequestFileApiStartedIntegrated220ApplicationPoolIdentityAlwaysRunning
RequestFileApiPaymentsV2StartedIntegrated220ApplicationPoolIdentityOnDemand
RequestPQRSDEntryApiStartedIntegrated220ApplicationPoolIdentityOnDemand
SharedServicesApiStartedIntegrated220ApplicationPoolIdentityOnDemand
.NET v2.0Startedv2.0Integrated120ApplicationPoolIdentityOnDemand
.NET v2.0 ClassicStartedv2.0Classic120ApplicationPoolIdentityOnDemand
.NET v4.5Startedv4.0Integrated120ApplicationPoolIdentityOnDemand
.NET v4.5 ClassicStartedv4.0Classic120ApplicationPoolIdentityOnDemand
_c_BPM.CancelCaseStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_CombinacionCorrespondenciaApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_DocumentaryReferencesApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_DocumentarySaveFromReferencesApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_DriveSQLStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_HefestoStartedv4.0Integrated120ApplicationPoolIdentityOnDemand
_c_HefestoApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_HefestoMAApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_RadicateApiNew_EFStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_RequestFileApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_RequestPQRSDEntryApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_SGDEAPortalApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_SharedDriveApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_SharedServicesApiStartedIntegrated120ApplicationPoolIdentityOnDemand
_c_SmartSupervisionApiStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraApiApoloStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraApiAuditStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraApiBPMStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraApiDmsStartedIntegrated120ApplicationPoolIdentityOnDemand
AgoraApiRequestFileStartedIntegrated120ApplicationPoolIdentityOnDemand
Api472StartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloApiDmsStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloApiRequestFileStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloBpmMinimalGetConfigStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloInitializateBpmMinimalStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloMinimalApiBpmGetTemplateDataLiteStartedIntegrated120ApplicationPoolIdentityOnDemand
ApoloUpdateBpmMinimalStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.Api.BeginProcessStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.Api.CreateCaseStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.Api.FinishTrackingStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.Api.GetDataStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.BeginProcessStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.CancelCaseStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.CreateCaseStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.DelegateTrackingStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.FinishTrackingStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.ReturnStageStartedIntegrated120ApplicationPoolIdentityOnDemand
BPM.UpdateDateLimitStartedIntegrated120ApplicationPoolIdentityOnDemand
BPMApiStartedIntegrated120ApplicationPoolIdentityOnDemand
BPMApiRadicadoWebStartedIntegrated120ApplicationPoolIdentityAlwaysRunning
ChatApiStartedIntegrated120ApplicationPoolIdentityOnDemand
Classic .NET AppPoolStartedv2.0Classic120ApplicationPoolIdentityOnDemand
CoreBIStartedIntegrated120SpecificUserOnDemand
DefaultAppPoolStartedv4.0Integrated120ApplicationPoolIdentityOnDemand
DMSApiRequestFileStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSDigitalizacionStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSDistributionStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSDrafDocumentApiStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSEmailStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSImportStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSInventoryStorageLoadStartedIntegrated120SpecificUserOnDemand
DMSMailServiceStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSMassiveDigitizationStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSParameterizationStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSReferencesStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSRequestFileStartedIntegrated120ApplicationPoolIdentityOnDemand
DMSSearcherV2StartedIntegrated120ApplicationPoolIdentityOnDemand
DocumentaryReferences_NewEFStartedIntegrated120ApplicationPoolIdentityOnDemand
DocumentaryReferencesApiCEMStartedIntegrated120ApplicationPoolIdentityOnDemand
DocumentarySaveFromReferencesApiStartedIntegrated120ApplicationPoolIdentityOnDemand
DriveStartedIntegrated120ApplicationPoolIdentityOnDemand
DriveSQLStartedIntegrated120ApplicationPoolIdentityOnDemand
DriveSQL_OLDStartedIntegrated120ApplicationPoolIdentityOnDemand
DriveSQLCEMStartedIntegrated120ApplicationPoolIdentityOnDemand
DriveSqlPDFAStartedIntegrated120ApplicationPoolIdentityOnDemand
FTPApiStartedIntegrated120ApplicationPoolIdentityOnDemand
HadesStartedIntegrated120ApplicationPoolIdentityOnDemand
HefestoApiStartedIntegrated120ApplicationPoolIdentityOnDemand
HefestoWordPdfApiStartedIntegrated120ApplicationPoolIdentityOnDemand
ImperiumQueryApiStartedIntegrated120ApplicationPoolIdentityOnDemand
ImportacionCCDStartedIntegrated120ApplicationPoolIdentityOnDemand
IntegrantionApiStartedIntegrated120ApplicationPoolIdentityOnDemand
LoanApiStartedIntegrated120ApplicationPoolIdentityOnDemand
MantenimientoStartedv4.0Integrated120ApplicationPoolIdentityOnDemand
NessusStartedv4.0Integrated120ApplicationPoolIdentityOnDemand
NotificationCenterStartedIntegrated11440ApplicationPoolIdentityOnDemand
NotificationCenterBPMStartedIntegrated120LocalSystemOnDemand
NotificationCenterCheckEmailApiStartedIntegrated120LocalSystemOnDemand
NotificationCenterCheckEmailApiV2StartedIntegrated120ApplicationPoolIdentityOnDemand
NotificationCenterClientCheckEmailsStartedIntegrated120ApplicationPoolIdentityAlwaysRunning
NotificationCenterSendApiStartedIntegrated120ApplicationPoolIdentityOnDemand
OpheliaDiretoryActiveStartedv4.0Integrated120ApplicationPoolIdentityOnDemand
OpheliaSuiteV2Startedv4.0Integrated120ApplicationPoolIdentityOnDemand
PersonsApiStartedIntegrated120ApplicationPoolIdentityOnDemand
ProcessTableStartedIntegrated120ApplicationPoolIdentityOnDemand
ProcessTableV2StartedIntegrated120ApplicationPoolIdentityOnDemand
RadicateApiNew_EFStartedIntegrated120ApplicationPoolIdentityOnDemand
ReportingCoreStartedIntegrated120SpecificUserOnDemand
RequestFileApiPaymentsStartedIntegrated120ApplicationPoolIdentityOnDemand
RequestFileApiV2StartedIntegrated120ApplicationPoolIdentityOnDemand
RequestFileUpdateStateApiStartedIntegrated120ApplicationPoolIdentityOnDemand
SchedelerApiStartedIntegrated120ApplicationPoolIdentityOnDemand
SGDEAPortal.ReassignTask.ApiStartedIntegrated10ApplicationPoolIdentityAlwaysRunning
SGDEAPortalApiStartedIntegrated120ApplicationPoolIdentityOnDemand
SharedDriveApiStartedIntegrated120ApplicationPoolIdentityOnDemand
SharedDriveApiCEMStartedIntegrated120ApplicationPoolIdentityOnDemand
SharedDriveApiV2StartedIntegrated120ApplicationPoolIdentityOnDemand
SharedDriveApiV2PaymentsStartedIntegrated120ApplicationPoolIdentityOnDemand
SharedServicesApiCEMStartedIntegrated120ApplicationPoolIdentityOnDemand
SmartSupervisionApiStartedIntegrated120ApplicationPoolIdentityOnDemand
TaskbarV2StartedIntegrated120ApplicationPoolIdentityOnDemand
WSApiStartedIntegrated120ApplicationPoolIdentityOnDemand
WSApiBPMStartedIntegrated120ApplicationPoolIdentityOnDemand

w3wp por Application Pool - detalle

ProcessIdAppPoolCPUMemoryMBPrivateMemoryMBStartTime
51412ReportingCore426.812619.52549.445/30/2026 2:11:13 PM
17764AgoraApi29.31186.741121.795/31/2026 1:00:00 PM
52580AgoraApi21.97742.48684.995/31/2026 1:00:00 PM
53836DMSMailService24.53717.75643.965/31/2026 5:54:20 AM
54696ApoloApiBPM24.97656.42591.125/31/2026 12:42:27 PM
14824ApoloApiBPM34.34651.75602.295/31/2026 8:13:33 AM
42208ApoloApi12.22651.61605.425/31/2026 1:06:28 PM
40112ApoloApi41.62650.81699.635/31/2026 10:53:57 AM
16948ApoloApi20.83636.26614.345/31/2026 11:56:31 AM
32720BPMApi80.48634.51624.275/30/2026 2:09:55 PM
65928AgoraApiRequestFile63.53626.11542.555/31/2026 2:50:04 AM
47392WSApiBPM68.09613.89541.475/30/2026 2:12:27 PM
34004NotificationCenterCheckEmailApi45.23594.64580.935/30/2026 2:11:06 PM
12940ApoloApi26.69578.98552.475/31/2026 12:32:17 PM
17568ApoloBpmMinimalGetConfig47.73573.21543.395/31/2026 12:45:08 PM
33596RadicateApiNew_EF11.91541.64482.595/31/2026 1:01:29 PM
52576ApoloMinimalApiBpmGetTemplateDataLite57.41512.78470.835/31/2026 12:44:43 PM
66868CoreBI17.08488.72426.865/30/2026 2:13:17 PM
44352SharedServicesApi9.42475.39419.485/31/2026 1:04:41 PM
30356RequestFileApi12.27450.76356.215/31/2026 1:00:58 PM
37756AgoraApi16.86444.63377.975/31/2026 1:00:00 PM
42808DMSInventoryStorageLoad12.19439.74402.945/30/2026 9:04:20 PM
47116AgoraApiApolo19.7433.59368.275/30/2026 2:10:37 PM
40436ApoloUpdateBpmMinimal14.91428.56390.595/31/2026 12:45:22 PM
1908RequestFileApi19.67410.79298.165/31/2026 10:35:02 AM
34524Hades39.09402.1531.575/30/2026 2:10:34 PM
58892ApoloApiRequestFile17.56386.59338.115/30/2026 2:11:10 PM
41884SharedDriveApi529.77363.2340.795/30/2026 2:10:21 PM
29072ApoloApiDms18.34344.75280.475/30/2026 2:10:10 PM
57156DriveSQL75.08335.88293.25/30/2026 2:10:46 PM
18856SGDEAPortal.ReassignTask.Api22.61331.62271.735/30/2026 2:09:30 PM
1952ProcessTable40.83330.41246.395/30/2026 2:13:39 PM
47760BPM.BeginProcess9.61329.58264.715/31/2026 12:44:26 PM
60884DocumentaryReferencesApi23.16327.18234.555/31/2026 1:02:58 PM
50572AgoraApiDms14.58280.11215.595/31/2026 2:50:04 AM
60744AgoraApiBPM16.64279.13214.645/31/2026 2:50:04 AM
29092NotificationCenter27.12268.9203.925/31/2026 3:00:00 AM
12540NotificationCenterBPM45.58258.86193.515/31/2026 2:30:04 AM
15576WSApi36.41225.86165.065/30/2026 2:11:19 PM
22032LoanApi18.39217.16164.515/30/2026 2:10:48 PM
46544ApoloInitializateBpmMinimal5.25196.65148.595/31/2026 12:45:14 PM
43976DMSDrafDocumentApi7.94182.98195.065/31/2026 1:12:44 PM
65760DMS8.11173.5180.745/31/2026 1:30:55 PM
15996AuditorApi6.5167.47169.45/31/2026 11:23:54 AM
41016AuditorApi4.33162.64165.75/31/2026 12:32:54 PM
43740ImperiumQueryApi23.12158.98300.625/30/2026 2:13:21 PM
29656OpheliaDiretoryActive29.22148.93290.455/30/2026 2:11:36 PM
5856AuditorApi4.02148.91150.715/31/2026 1:06:17 PM
39028DMSApiRequestFile2.44119.54120.465/31/2026 1:11:39 PM
18816ImportacionCCD63.92116.7581.045/30/2026 2:13:25 PM
60440NotificationCenterCheckEmailApiV28.94115.2771.55/30/2026 9:00:54 PM
47948ChatApi12.31113.54123.615/30/2026 2:11:45 PM
35924_c_HefestoApi14.38109.7867.215/30/2026 2:10:20 PM
29908FTPApi38.47109.164.445/30/2026 2:14:10 PM
41012BPMApiRadicadoWeb15.44105.765.325/30/2026 2:09:30 PM
60188RadicateApi5.84105.2664.785/31/2026 4:44:38 AM
61908SGDEAPortalApi16.5101.0561.715/30/2026 7:12:58 PM
64308ArtemisApi9.9199.0260.835/30/2026 11:32:29 PM
39640DMSCommonsApi4.7394.75101.575/31/2026 4:41:54 AM
53868BPM.Api.FinishTracking2.1993.0456.965/31/2026 1:08:31 PM
43296SharedDriveApiV2Payments10.5686.8191.875/30/2026 2:09:51 PM
11804Api47213.2885.0791.335/30/2026 2:10:55 PM
54332TaskbarV214.0284.1590.035/30/2026 2:11:38 PM
16536IntegrantionApi11.7783.5590.825/30/2026 2:12:20 PM
57764SchedelerApi2.9875.3290.95/31/2026 9:50:33 AM
8932OpheliaSuiteV21155.2222.215/30/2026 4:06:30 PM
64320RequestFileUpdateStateApi0.6123.411.545/31/2026 12:45:33 PM
49832Apolo1.721.8511.025/31/2026 9:47:08 AM
62576NotificationCenterClientCheckEmails1.4821.5710.775/31/2026 12:02:17 PM
22504DMSRequestFile0.9821.3710.645/31/2026 1:43:55 PM
12312DocumentaryReferencesApi0.1120.5510.345/31/2026 1:45:57 PM
27204SharedServicesApi0.2320.5410.355/31/2026 1:50:26 PM
19256DMSCommonsApi0.1920.5110.295/31/2026 1:45:58 PM
50444ArtemisApi0.1920.4810.35/31/2026 1:53:48 PM
50308ArtemisApi0.2320.4610.275/31/2026 1:50:57 PM

Top procesos por memoria

NameIdMemoryMBCPU
w3wp514122619.5426.81
w3wp177641186.7429.3
w3wp52580742.5121.97
w3wp53836717.7524.53
w3wp54696656.4224.97
w3wp14824651.7534.34
w3wp42208651.6112.22
w3wp40112650.8141.62
w3wp16948636.2620.83
w3wp32720634.5180.48
w3wp65928626.1163.53
w3wp47392613.8968.09
w3wp34004594.6445.23
w3wp12940578.9826.69
w3wp17568573.2347.73
w3wp33596541.6411.91
w3wp52576512.7957.41
dsa4568497.8733452.61
w3wp66868488.6917.08
w3wp44352475.399.42
coreServiceShell3508459.0369980.23
w3wp30356450.7612.27
w3wp37756444.6416.88
w3wp42808439.7412.19
w3wp47116433.5919.72

Top procesos por CPU acumulado

NameIdCPUAcumuladoMemoryMB
coreServiceShell350869980.25459.03
dsa456833452.61497.87
kntcma396431115.55121.44
WmiPrvSE637222438.6975.44
DoubleTake398020737.78159.32
svchost193620566.4238.9
System420421.590.31
zabbix_agent2432817529.3345.65
zabbix_agent22423216701.9546.65
newrelic-infra642813319.95121.79
CoreManagementService189609912.38267.54
tm_netagent121008331.3324.66
svchost25728290.5847.54
OMemory41968165.45218.02
lsass10407878.3868.32
fluent-bit141605010.8334.84
WmiPrvSE133243951.5850.43
nscp41683892.5234.14
WmiPrvSE157963323.4529.76
WmiPrvSE85242780.0270
services10162035.720.18
svchost13121627.8427.94
SolarWinds.Agent.Service43001330.0631.45
svchost18041147.8111.7
conhost64841144.4212.72

Servicios Ophelia / DigitalWare

NameDisplayNameStateProcessIdStartModePathName
OMemoryOphelia Memory ServerRunning4196AutoC:\OMemory\OMemory.exe --content-root=C:\OMemory
Ophelia BPMTimerOphelia BPMTimerRunning38240Auto"C:\OpheliaSuite\BPMTimer\OpheliaSuiteV2.Core.BPMTimer.exe" ThisisParameter
Ophelia Orion BPM V2Ophelia Orion BPM V2Running53140Auto"D:\OpheliaSuite\OrionBPM\OpheliaSuiteV2.Core.Orion.Manager.exe" ThisisParameter
vstsagent.digitalwareophelia.Imperium-Imperium.DWSGDAAPP1Azure Pipelines Agent (digitalwareophelia.Imperium-Imperium.DWSGDAAPP1)Running5960Auto"C:\azagent\A1\bin\AgentService.exe"

Puertos relevantes Ophelia

LocalAddressLocalPortOwningProcess
10.238.99.15363794196
10.238.99.153658053140
::658053140
10.238.99.153658553140
::658553140
::80254
::80824
0.0.0.084434168
::5508038240
10.238.99.1535508038240

Conexiones TCP por estado

NameCount
Bound277
CloseWait1
Established337
LastAck1
Listen72
TimeWait149

Puertos escuchando

LocalAddressLocalPortOwningProcess
::1351312
0.0.0.01351312
10.238.99.1531394
::4454
::18014396
0.0.0.018014396
0.0.0.019203964
::19203964
::21034396
0.0.0.021034396
::21054396
0.0.0.021054396
::21074396
0.0.0.021074396
::21563724
0.0.0.033891436
::33891436
::36613964
0.0.0.036613964
::41184568
0.0.0.056664168
::56664168
0.0.0.060143964
::63203980
::63254
::63264
10.238.99.15363794196
10.238.99.153658053140
::658053140
10.238.99.153658553140
::658553140
::80254
::80824
0.0.0.084434168
::1005124232
::124894168
0.0.0.0124894168
127.0.0.11271012584
127.0.0.1180036428
::301504328
127.0.0.1424243944
::470014
0.0.0.0496651020
::496651020
::496661936
0.0.0.0496661936
0.0.0.0496672188
::496672188
0.0.0.0496681040
::496681040
::496693056
0.0.0.0496693056
0.0.0.0496833440
::496833440
::549052572
0.0.0.0549052572
::5508038240
10.238.99.1535508038240
::571214396
0.0.0.0571214396
0.0.0.0571224384
::571224384
::571273964
0.0.0.0571283964
::571293964
0.0.0.0571303964
0.0.0.0571381016
::571381016
::571541040
0.0.0.0571541040
::6553256904
0.0.0.06553256904

Contadores de rendimiento - muestra 1 minuto

CounterMinMaxAverage
\\dwsgdaapp1\processor(_total)\% processor time5.4332.812.94
\\dwsgdaapp1\memory\available mbytes314443195331736.92
\\dwsgdaapp1\system\processor queue length000
\\dwsgdaapp1\physicaldisk(_total)\% disk time1.69136.3524.84
\\dwsgdaapp1\physicaldisk(_total)\current disk queue length050.92
\\dwsgdaapp1\web service(_total)\current connections385.42
\\dwsgdaapp1\asp.net applications(__total__)\requests/sec000

Errores por proveedor

ProviderNameCantidad
OpheliaSuiteV2.Core.BPMTimer74
.NET Runtime20
OpheliaSuiteV2.Core.Orion.Manager12
OCS Inventory Service9
IIS AspNetCore Module V24
Microsoft-Windows-IIS-W3SVC-PerfCounters1

Errores críticos filtrados

TimeCreatedProviderNameIdMessage
5/31/2026 3:00:02 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/30/2026 3:25:23 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Invalid pointer operation
5/30/2026 3:00:01 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/29/2026 4:00:48 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: e75508f0780e3771 TraceId: 8b9a72028e17ef17ecd8f11e47febe28 ParentId: 0000000000000000 RequestId: 800063c9-0007-bb00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 3:59:58 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 7f417536dab69c0e TraceId: 8e6c5cebdeb113cabc6ede6670a88961 ParentId: 0000000000000000 RequestId: 8000174b-0006-d400-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 2:54:31 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: f46de1fa50707765 TraceId: ac34ace3cb27b38f286ff0297ec29b5c ParentId: 0000000000000000 RequestId: 8000a9d1-0008-ee00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 2:11:25 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: b6567ff4b61d1979 TraceId: 46a8f486b7a2ec7657f391e8def1b46d ParentId: 0000000000000000 RequestId: 80002190-0005-cf00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 10:37:11 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 1ad2cd269c6c32ae TraceId: 731bdf513dfe4b1913a2981d61d22e01 ParentId: 0000000000000000 RequestId: 80001b5e-0007-7800-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 10:32:56 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 05e17e26d146f807 TraceId: 69e190fef513ff8841ba6fb85cb61495 ParentId: 0000000000000000 RequestId: 800059d7-0005-de00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 10:31:44 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 26f22db53d9fad1c TraceId: 75cc07cbf05b4030d3df5254512a147a ParentId: 0000000000000000 RequestId: 800092a5-0008-ee00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 3:00:03 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/29/2026 2:57:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:57:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:57:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:55:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:55:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:54:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:54:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:53:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:53:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:12 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob EventId: 0 ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService EventId: 0 ValidateTrackingQueueService.Execute. Exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole...
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager10100Category: Microsoft.EntityFrameworkCore.Query EventId: 10100 An exception occurred while iterating over the results of a query for context type 'OpheliaSuiteV2.Core.Orion.Manager.DataAccess.DbContextOrion'. Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj...
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager20004Category: Microsoft.EntityFrameworkCore.Database.Connection EventId: 20004 An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
5/29/2026 2:49:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:49:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:48:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:48:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:12 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:45:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:45:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:44:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:44:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:43:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:43:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)

Errores recientes - Application

TimeCreatedProviderNameIdMessage
5/31/2026 6:32:46 AMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/31/2026 6:32:23 AMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/31/2026 5:40:00 AM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/31/2026 3:00:02 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/30/2026 7:26:27 PMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 7:26:04 PMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 5:34:50 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/30/2026 4:06:30 PMIIS AspNetCore Module V21034Could not load configuration. Exception message: Attribute 'processPath' is required.
5/30/2026 3:19:03 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/30/2026 2:10:55 PMIIS AspNetCore Module V21034Could not load configuration. Exception message: Attribute 'processPath' is required.
5/30/2026 1:08:15 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api.Domain.Services.SendGridDomainService.Dispose() in C:\AzureAgent\_work\42\s\OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api\Domain\Services\SendGridDomainService.cs:line 306 at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, Str...
5/30/2026 1:08:15 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/30/2026 1:06:10 PMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 12:02:51 PMMicrosoft-Windows-IIS-W3SVC-PerfCounters2001It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.
5/30/2026 3:25:23 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Invalid pointer operation
5/30/2026 3:00:01 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/30/2026 1:09:35 AMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/30/2026 12:30:25 AMIIS AspNetCore Module V21034Could not load configuration. Exception message: Attribute 'processPath' is required.
5/30/2026 12:20:48 AM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api.Domain.Services.SendGridDomainService.Dispose() in C:\AzureAgent\_work\42\s\OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api\Domain\Services\SendGridDomainService.cs:line 306 at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, Str...
5/29/2026 5:50:08 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/29/2026 4:00:48 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: e75508f0780e3771 TraceId: 8b9a72028e17ef17ecd8f11e47febe28 ParentId: 0000000000000000 RequestId: 800063c9-0007-bb00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 3:59:58 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 7f417536dab69c0e TraceId: 8e6c5cebdeb113cabc6ede6670a88961 ParentId: 0000000000000000 RequestId: 8000174b-0006-d400-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 2:54:31 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: f46de1fa50707765 TraceId: ac34ace3cb27b38f286ff0297ec29b5c ParentId: 0000000000000000 RequestId: 8000a9d1-0008-ee00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 2:11:25 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: b6567ff4b61d1979 TraceId: 46a8f486b7a2ec7657f391e8def1b46d ParentId: 0000000000000000 RequestId: 80002190-0005-cf00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 1:51:09 PMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 10:37:11 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 1ad2cd269c6c32ae TraceId: 731bdf513dfe4b1913a2981d61d22e01 ParentId: 0000000000000000 RequestId: 80001b5e-0007-7800-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 10:32:56 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 05e17e26d146f807 TraceId: 69e190fef513ff8841ba6fb85cb61495 ParentId: 0000000000000000 RequestId: 800059d7-0005-de00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 10:31:44 AM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 26f22db53d9fad1c TraceId: 75cc07cbf05b4030d3df5254512a147a ParentId: 0000000000000000 RequestId: 800092a5-0008-ee00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7 ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
5/29/2026 6:16:03 AM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.Hermes.InstitutionalMailService.Api.Domain.Services.DirectoryActiveDomainService.Dispose() in C:\PROYECTOS_DIGITALWARE\NuevosProyectosDMS\OpheliaSuiteV2.Core.Hermes.InstitutionalMailService\Domain\Services\DirectoryActiveDomainService.cs:line 166 at OpheliaSuiteV2.Core.DataAccess.SQL.DomainService.Dispose() at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() a...
5/29/2026 4:04:36 AMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/29/2026 3:00:03 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 BackgroundService.ExecuteAsync. A task was canceled.
5/29/2026 2:57:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:57:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:57:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:56:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:55:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:55:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:54:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:54:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:53:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:53:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:52:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:51:12 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob EventId: 0 ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService EventId: 0 ValidateTrackingQueueService.Execute. Exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole...
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager10100Category: Microsoft.EntityFrameworkCore.Query EventId: 10100 An exception occurred while iterating over the results of a query for context type 'OpheliaSuiteV2.Core.Orion.Manager.DataAccess.DbContextOrion'. Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj...
5/29/2026 2:50:30 AMOpheliaSuiteV2.Core.Orion.Manager20004Category: Microsoft.EntityFrameworkCore.Database.Connection EventId: 20004 An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
5/29/2026 2:49:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:49:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:48:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:48:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:47:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:46:12 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:45:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:45:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:44:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:44:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:43:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:43:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:42:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:41:12 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:40:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:40:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:40:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob EventId: 0 ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
5/29/2026 2:40:30 AMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService EventId: 0 ValidateTrackingQueueService.Execute. Exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole...
5/29/2026 2:40:30 AMOpheliaSuiteV2.Core.Orion.Manager10100Category: Microsoft.EntityFrameworkCore.Query EventId: 10100 An exception occurred while iterating over the results of a query for context type 'OpheliaSuiteV2.Core.Orion.Manager.DataAccess.DbContextOrion'. Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999; ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj...
5/29/2026 2:40:30 AMOpheliaSuiteV2.Core.Orion.Manager20004Category: Microsoft.EntityFrameworkCore.Database.Connection EventId: 20004 An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
5/29/2026 2:39:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:39:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:38:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:38:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:37:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:37:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:37:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:36:58 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:36:43 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:36:28 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:36:13 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:35:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:35:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:34:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
5/29/2026 2:34:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
5/29/2026 2:14:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:13:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:13:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:12:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:12:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:11:57 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/29/2026 2:11:42 AMOpheliaSuiteV2.Core.BPMTimer0Category: OpheliaSuiteV2.Core.BPMTimer.Worker EventId: 0 IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Socket Error Code: 10060($274C)
5/28/2026 7:26:59 PMIIS AspNetCore Module V21034Could not load configuration. Exception message: Attribute 'processPath' is required.
5/28/2026 7:20:37 PM.NET Runtime1026Application: w3wp.exe CoreCLR Version: 8.0.23.53103 .NET Version: 8.0.0 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException: The method or operation is not implemented. at OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api.Domain.Services.SendGridDomainService.Dispose() in C:\AzureAgent\_work\42\s\OpheliaSuiteV2.Core.NotificationCenterCheckEmail.Api\Domain\Services\SendGridDomainService.cs:line 306 at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.DisposeAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Hosting.WebHost.DisposeServiceProviderAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Hosting.WebHost.DisposeAsync() at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, Str...
5/28/2026 6:02:07 PMOCS Inventory Service20Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>.
5/28/2026 5:18:27 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: f93ab097de973576 TraceId: f715bd97c9d0b7f82e939d15246e324f ParentId: 0000000000000000 RequestId: 8000300c-0008-9400-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
5/28/2026 5:05:22 PMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob EventId: 0 ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
5/28/2026 5:05:22 PMOpheliaSuiteV2.Core.Orion.Manager0Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService EventId: 0 ValidateTrackingQueueService.Execute. Exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolTh...
5/28/2026 5:05:22 PMOpheliaSuiteV2.Core.Orion.Manager10100Category: Microsoft.EntityFrameworkCore.Query EventId: 10100 An exception occurred while iterating over the results of a query for context type 'OpheliaSuiteV2.Core.Orion.Manager.DataAccess.DbContextOrion'. Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.Execu...
5/28/2026 5:05:22 PMOpheliaSuiteV2.Core.Orion.Manager20102Category: Microsoft.EntityFrameworkCore.Database.Command EventId: 20102 Failed executing DbCommand (300,021ms) [Parameters=[@companyCode='?' (DbType = Int16), @segContList1='?' (Size = 40), @segContList2='?' (Size = 40), @segContList3='?' (Size = 40), @segContList4='?' (Size = 40), @segContList5='?' (Size = 40), @segContList6='?' (Size = 40), @segContList7='?' (Size = 40), @segContList8='?' (Size = 40), @segContList9='?' (Size = 40), @segContList10='?' (Size = 40), @segContList11='?' (Size = 40), @segContList12='?' (Size = 40), @segContList13='?' (Size = 40), @segContList14='?' (Size = 40), @segContList15='?' (Size = 40), @segContList16='?' (Size = 40), @segContList17='?' (Size = 40), @segContList18='?' (Size = 40), @segContList19='?' (Size = 40), @segContList20='?' (Size = 40), @segContList21='?' (Size = 40), @segContList22='?' (Size = 40), @segContList23='?' (Size = 40), @segContLi...
5/28/2026 5:03:38 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 35e74462dd43d223 TraceId: 07639048e76a7e849bca80c385013bdf ParentId: 0000000000000000 RequestId: 800038a9-0005-c100-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
5/28/2026 4:58:31 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 5b9c227d3ba1e757 TraceId: 5f5fb317c4742de8b8d1e84f5601c513 ParentId: 0000000000000000 RequestId: 80001c08-0006-e900-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
5/28/2026 4:55:12 PM.NET Runtime1000Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService EventId: 0 SpanId: 34faab5de35afe97 TraceId: 16500e47b04f90eebbd22d2de317ab61 ParentId: 0000000000000000 RequestId: 80001063-0009-3c00-b63f-84710c7967bb RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api) ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess

Errores recientes - System

TimeCreatedProviderNameIdMessage
5/28/2026 11:17:34 AMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/28/2026 11:17:04 AMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/26/2026 12:45:27 PMMicrosoft-Windows-DistributedCOM10001Unable 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 12:25:04 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/26/2026 11:22:59 AMMicrosoft-Windows-DistributedCOM10001Unable 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 10:28:28 AMMicrosoft-Windows-DistributedCOM10001Unable 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 10:28:27 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 11:47:03 AMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/25/2026 11:46:35 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 11:46:35 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 11:46:34 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 11:46:34 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 11:46:33 AMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/25/2026 11:46:33 AMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/25/2026 6:23:29 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 6:23:28 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 6:23:28 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 6:23:28 AMMicrosoft-Windows-DistributedCOM10001Unable 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/25/2026 6:23:27 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:16:16 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:16:16 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:16:16 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:16:16 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:16:15 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:01:41 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:01:41 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:01:41 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:01:41 AMMicrosoft-Windows-DistributedCOM10001Unable 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 5:01:41 AMMicrosoft-Windows-DistributedCOM10001Unable 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:46:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:46:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:46:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:23:30 PMMicrosoft-Windows-TPM-WMI1801Updated 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: BaseBoardManufacturer:Intel Corporation;FirmwareManufacturer:VMware, Inc.;FirmwareVersion:VMW71.00V.21100432.B64.2301110304;OEMModelNumber:VMware7,1;OEMModelBaseBoard:440BX Desktop Reference Platform;OEMModelSystemFamily:;OEMManufacturerName:VMware, Inc.;OEMModelSKU:;OSArchitecture:amd64; BucketId: d23cb67dc3822dcd55f3389e1d18ef1d7106588149c6c8c8d2f98ff80600e0d8 BucketConfidenceLevel: Under Observation - More Data Needed UpdateType: For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
5/23/2026 11:18:22 PMiScsiPrt10Login request failed. The login response packet is given in the dump data.
5/23/2026 11:18:23 PMMicrosoft-Windows-WinRM10150The 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:18:23 PMMicrosoft-Windows-WinRM10150The 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:18:21 PMService Control Manager7000The luafv service failed to start due to the following error: This driver has been blocked from loading
5/23/2026 11:17:39 PMService Control Manager7024The New Relic Infrastructure Agent service terminated with the following service-specific error: The system cannot find the file specified.
5/23/2026 11:16:51 PMService Control Manager7043The Double-Take service did not shut down properly after receiving a preshutdown control.
5/23/2026 11:15:22 PMService Control Manager7023The Update Orchestrator Service service terminated with the following error: This operation returned because the timeout period expired.
5/23/2026 11:15:00 PMMicrosoft-Windows-DistributedCOM10001Unable 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:15:00 PMMicrosoft-Windows-DistributedCOM10001Unable 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:14:59 PMMicrosoft-Windows-DistributedCOM10001Unable 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:14:59 PMMicrosoft-Windows-DistributedCOM10001Unable 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 10:47:48 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/23/2026 10:47:48 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 9:19:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:19:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:19:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:19:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:19:56 PMMicrosoft-Windows-DistributedCOM10001Unable 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:18:22 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 9:18:22 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 9:12:19 PMMicrosoft-Windows-DistributedCOM10001Unable 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:12:19 PMMicrosoft-Windows-DistributedCOM10001Unable 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:12:19 PMMicrosoft-Windows-DistributedCOM10001Unable 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:12:19 PMMicrosoft-Windows-DistributedCOM10001Unable 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:10:08 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 9:10:08 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 8:33:53 PMMicrosoft-Windows-DistributedCOM10001Unable 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:33:53 PMMicrosoft-Windows-DistributedCOM10001Unable 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:33:52 PMMicrosoft-Windows-DistributedCOM10001Unable 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:33:52 PMMicrosoft-Windows-DistributedCOM10001Unable 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:33:52 PMMicrosoft-Windows-DistributedCOM10001Unable 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 7:38:49 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/22/2026 7:38:49 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/21/2026 5:20:58 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/21/2026 5:20:58 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/21/2026 5:20:36 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/21/2026 5:19:42 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/21/2026 5:19:42 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/17/2026 10:30:02 AMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/17/2026 10:30:02 AMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/16/2026 11:58:12 PMService Control Manager7000The Npcap Packet Driver (NPCAP) (Wi-Fi) service failed to start due to the following error: The system cannot find the file specified.
5/16/2026 5:41:17 AMMicrosoft-Windows-DistributedCOM10001Unable 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/16/2026 5:41:17 AMMicrosoft-Windows-DistributedCOM10001Unable 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/16/2026 5:41:17 AMMicrosoft-Windows-DistributedCOM10001Unable 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/16/2026 5:41:17 AMMicrosoft-Windows-DistributedCOM10001Unable 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/16/2026 5:41:16 AMMicrosoft-Windows-DistributedCOM10001Unable 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/15/2026 11:46:38 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/15/2026 11:46:38 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/15/2026 10:16:51 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/15/2026 10:16:51 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/15/2026 7:58:55 PMMicrosoft-Windows-DistributedCOM10001Unable 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/15/2026 7:58:55 PMMicrosoft-Windows-DistributedCOM10001Unable 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/15/2026 5:07:30 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/15/2026 5:07:30 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 5:13:29 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 5:13:28 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 5:13:28 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 5:13:27 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 5:13:27 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 4:08:53 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 4:08:53 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 3:57:41 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 3:57:41 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 1:16:00 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 1:06:28 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 1:06:28 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 12:35:00 PMMicrosoft-Windows-DistributedCOM10001Unable 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/14/2026 12:15:16 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/14/2026 12:15:16 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/13/2026 10:49:13 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/13/2026 10:01:59 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/13/2026 10:01:59 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/13/2026 5:47:53 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/13/2026 5:47:53 PMMicrosoft-Windows-DistributedCOM10016The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5/13/2026 10:07:02 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/13/2026 10:07:02 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/13/2026 10:05:48 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/13/2026 10:05:48 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/13/2026 9:50:11 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/13/2026 9:50:11 AMService Control Manager7006The ScRegSetValueExW call failed for Start with the following error: Access is denied.
5/11/2026 4:06:54 PMMicrosoft-Windows-DistributedCOM10001Unable to start a DCOM Server: {9BA05972-F6A8-11CF-A442-00A0C90A8F39} as Unavailable/Unavailable. The error: "0" Happened while starting this command: C:\Windows\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {9BA05972-F6A8-11CF-A442-00A0C90A8F39} -Embedding
5/11/2026 4:06:54 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/11/2026 4:06:36 PMMicrosoft-Windows-DistributedCOM10001Unable 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/11/2026 4:06:35 PMMicrosoft-Windows-DistributedCOM10001Unable 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/11/2026 4:06:24 PMMicrosoft-Windows-DistributedCOM10010The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
5/11/2026 4:05:03 PMMicrosoft-Windows-GroupPolicy1030The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
5/11/2026 3:58:02 PMMicrosoft-Windows-GroupPolicy1030The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.