| TimeCreated | ProviderName | Id | Message |
| 5/23/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/22/2026 10:29:27 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ac13d685ae2fa3cb
TraceId: f24a2e41e37057de7df69d1e79e3b830
ParentId: 0000000000000000
RequestId: 800089ca-0005-b900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: e5104c5c-5d0e-4290-8b5b-4b14cb95378e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio IMPERIUMREPORT https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/ReportingCore/api/ReportDesignerV1/GetExportedReportBase64
|
| 5/22/2026 11:28:28 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ccaa6964b63c3f8d
TraceId: a7971e89531e5faef012331fbc930e63
ParentId: 0000000000000000
RequestId: 8000fa11-0001-bf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: e5104c5c-5d0e-4290-8b5b-4b14cb95378e
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/22/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/21/2026 3:16:43 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 4c1be9797b675b54
TraceId: 90a6941f935ee652d5f08d569ab70fe1
ParentId: 0000000000000000
RequestId: 8000b329-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: df927ef1-6dd2-4d95-a92e-24305be08b41
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/21/2026 2:32:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9f91debe6df62c8c
TraceId: ac18d7ad8a3b9f319d056da81fbdb0d0
ParentId: 0000000000000000
RequestId: 80009d6d-0002-ce00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: df927ef1-6dd2-4d95-a92e-24305be08b41
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/21/2026 3:00:04 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/20/2026 11:25:46 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 54941d45c60bfac2
TraceId: 6928abc07a8c2c3c1a209a394bb2519b
ParentId: 0000000000000000
RequestId: 8000e199-0001-bc00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/20/2026 3:00:05 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:46 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/20/2026 2:45:01 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/20/2026 2:44:46 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/19/2026 6:47:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: a107f2ce28d90066
TraceId: 914c4ebafd4b9ca9ec714737aaafe5e0
ParentId: 0000000000000000
RequestId: 8000eeda-0001-8f00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 6:46:53 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ed41621a3adba5dc
TraceId: fe95a750184e3965f60b98934e1151e6
ParentId: 0000000000000000
RequestId: 8000870b-0006-e000-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 6:22:41 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 748a70843d47f229
TraceId: 59274d7e2846acdd3e0b276eb97f943f
ParentId: 0000000000000000
RequestId: 8000f2e4-0007-f600-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 5:11:55 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: a34996695722f401
TraceId: ddac81063c72dcacbbcad3eb9590b8ba
ParentId: 0000000000000000
RequestId: 80007b25-000a-ff00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 4:16:32 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: fd62be1a6db5885d
TraceId: 07f606c80d01cc1ff5fe9262ed1fc823
ParentId: 0000000000000000
RequestId: 80004949-000b-dc00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 4:15:19 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: d04a26c062b52641
TraceId: 3d4e1ae009daa6f183c500cde39078cc
ParentId: 0000000000000000
RequestId: 80007af0-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:48:33 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 40118d12067b87f7
TraceId: 96f27f15039fbc5f9a4c060e87b58f3e
ParentId: 0000000000000000
RequestId: 8001fab1-0004-f700-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:18:29 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: f581c78cb26398f8
TraceId: 0949f688935ea39dc8045874461e30b0
ParentId: 0000000000000000
RequestId: 80004e20-0005-bf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:06:40 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 258863a7aac25029
TraceId: 6ae56701ab78c47acf2dd29bf689b719
ParentId: 0000000000000000
RequestId: 8000c864-0007-dd00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:05:02 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 6c4f459a01fd1458
TraceId: e0f72f68ea5a75f86b258bf539799e04
ParentId: 0000000000000000
RequestId: 8000bf47-0007-cf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 2:42:54 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 4c7c043e5d4464d8
TraceId: 060f999a64069f860bb257291bd45e2a
ParentId: 0000000000000000
RequestId: 80007875-0003-3f00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:00:08 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/19/2026 12:30:43 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/18/2026 3:06:05 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/17/2026 3:00:01 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/16/2026 12:12:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: dcd5f1c10b0610fd
TraceId: a966cad3b3da5f864d659908d1cd00c3
ParentId: 0000000000000000
RequestId: 800079b2-000a-f200-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/16/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/15/2026 11:50:24 PM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Invalid pointer operation
|
| 5/15/2026 5:02:29 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 1a589208005427a5
TraceId: a89c7d6a89bc3e2c6f808be0baab8ca7
ParentId: 0000000000000000
RequestId: 80010e18-0001-b900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:56:46 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 568e90065ff38600
TraceId: 1c514ddedf6f98b6def906ea1332f31f
ParentId: 0000000000000000
RequestId: 80002a54-0005-bb00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:55:12 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 2b7d5b1de164c1e9
TraceId: af0b5e2838e7deea6462fee4f4382b5c
ParentId: 0000000000000000
RequestId: 80004841-0002-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:54:39 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: b297c63ce7e6afc3
TraceId: 92b2cd53526002341881845b8db601b5
ParentId: 0000000000000000
RequestId: 80004819-0002-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:46:22 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: c79f41276581f0d6
TraceId: 395c3617f4e6fcb26d5355903208a6a8
ParentId: 0000000000000000
RequestId: 80009689-0004-e800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:44:31 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: b060feb7e77e9e11
TraceId: 6ddf8ce438da93bd8d7cc753e673e9cd
ParentId: 0000000000000000
RequestId: 80006910-0006-e100-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:30:34 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 99386d8b10563aa0
TraceId: 5f1206891937a6b9e5bcffc0db18e214
ParentId: 0000000000000000
RequestId: 80009314-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:21:41 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 0a32ee1e460b8e38
TraceId: df36d7b40a24d46db68539eba58892ce
ParentId: 0000000000000000
RequestId: 8000915a-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:21:35 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9a508302a42bb318
TraceId: 7b406fb234ad1be3ee02527413860958
ParentId: 0000000000000000
RequestId: 800194cd-0004-f700-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:20:56 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 031a3608f7191b29
TraceId: 686533f5106127127045ea0e9aff9475
ParentId: 0000000000000000
RequestId: 8000679d-0001-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 2:46:01 PM | .NET Runtime | 1026 | Application: 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.InvalidOperationException: There is already an open DataReader associated with this Connection which must be closed first.
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at Microsoft.Data.SqlClient.SqlInternalTransaction.Rollback()
at Microsoft.Data.SqlClient.SqlInternalTransaction.Dispose(Boolean disposing)
at Microsoft.Data.SqlClient.SqlInternalTransaction.Dispose()
at Microsoft.Data.SqlClient.SqlTransaction.Dispose(Boolean disposing)
at Microsoft.EntityFrameworkCore.Storage.RelationalTransaction.Dispose()
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.Dispose()
at OpheliaSuiteV2.Core.DataAccess.SQL.... |
| 5/15/2026 1:23:14 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 96ae6145a318fad4
TraceId: 42e05f2b3647b4066af23266c0821d1b
ParentId: 0000000000000000
RequestId: 800486f4-0006-fd00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 12:06:55 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 834255f904cf4764
TraceId: 3294baace1ab6ca1d93f1e55b4ffbcb2
ParentId: 0000000000000000
RequestId: 8000801e-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 12:03:52 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: f9c57ebc9374e793
TraceId: ae957c8860bee84884537d029867936a
ParentId: 0000000000000000
RequestId: 80018aab-0007-ea00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 11:57:37 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9c997c195c250517
TraceId: 84e2cb8de486c8744e72471efd96f420
ParentId: 0000000000000000
RequestId: 8000ed4c-0009-e800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 3:13:54 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:13:39 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:12:39 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: 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/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 10100 | Category: 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... |
| TimeCreated | ProviderName | Id | Message |
| 5/23/2026 9:51:29 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/23/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/23/2026 2:51:46 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/23/2026 12:52:26 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/22/2026 10:29:46 PM | .NET Runtime | 1026 | Application: 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/22/2026 10:29:27 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ac13d685ae2fa3cb
TraceId: f24a2e41e37057de7df69d1e79e3b830
ParentId: 0000000000000000
RequestId: 800089ca-0005-b900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: e5104c5c-5d0e-4290-8b5b-4b14cb95378e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio IMPERIUMREPORT https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/ReportingCore/api/ReportDesignerV1/GetExportedReportBase64
|
| 5/22/2026 8:47:33 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/22/2026 8:47:11 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/22/2026 8:09:21 PM | .NET Runtime | 1026 | Application: 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/22/2026 11:28:28 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ccaa6964b63c3f8d
TraceId: a7971e89531e5faef012331fbc930e63
ParentId: 0000000000000000
RequestId: 8000fa11-0001-bf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: e5104c5c-5d0e-4290-8b5b-4b14cb95378e
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/22/2026 5:31:15 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/22/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/21/2026 7:51:58 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/21/2026 6:10:06 PM | .NET Runtime | 1026 | Application: 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/21/2026 5:29:33 PM | .NET Runtime | 1026 | Application: 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/21/2026 4:57:10 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/21/2026 3:16:43 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 4c1be9797b675b54
TraceId: 90a6941f935ee652d5f08d569ab70fe1
ParentId: 0000000000000000
RequestId: 8000b329-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: df927ef1-6dd2-4d95-a92e-24305be08b41
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/21/2026 2:32:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9f91debe6df62c8c
TraceId: ac18d7ad8a3b9f319d056da81fbdb0d0
ParentId: 0000000000000000
RequestId: 80009d6d-0002-ce00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: df927ef1-6dd2-4d95-a92e-24305be08b41
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/21/2026 1:51:47 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/21/2026 12:10:32 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/21/2026 12:10:09 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/21/2026 9:49:04 AM | .NET Runtime | 1026 | Application: 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/21/2026 5:03:40 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/21/2026 3:00:04 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/21/2026 12:12:50 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 12:33:52 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 12:29:22 PM | .NET Runtime | 1026 | Application: 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/20/2026 11:25:46 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 54941d45c60bfac2
TraceId: 6928abc07a8c2c3c1a209a394bb2519b
ParentId: 0000000000000000
RequestId: 8000e199-0001-bc00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/20/2026 10:48:11 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 7:21:51 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 7:21:28 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 4:48:20 AM | .NET Runtime | 1026 | Application: 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/20/2026 3:00:05 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:55 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Login failed for user 'ophelia'.
Cannot open database "OpheliaSuite" requested by the login. The login failed.
|
| 5/20/2026 2:45:46 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/20/2026 2:45:01 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
IntermetiateEventTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/20/2026 2:44:46 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
StartEventWithTimerJob : Error TSDmrAncestro.ProgramLogin: Cannot connect to server on host 'SRVCLSGDEA': Connection timed out
|
| 5/20/2026 12:03:09 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/19/2026 11:41:47 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 9:38:37 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 6:47:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: a107f2ce28d90066
TraceId: 914c4ebafd4b9ca9ec714737aaafe5e0
ParentId: 0000000000000000
RequestId: 8000eeda-0001-8f00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 6:46:53 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: ed41621a3adba5dc
TraceId: fe95a750184e3965f60b98934e1151e6
ParentId: 0000000000000000
RequestId: 8000870b-0006-e000-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 6:22:41 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 748a70843d47f229
TraceId: 59274d7e2846acdd3e0b276eb97f943f
ParentId: 0000000000000000
RequestId: 8000f2e4-0007-f600-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 6:03:00 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/19/2026 5:11:55 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: a34996695722f401
TraceId: ddac81063c72dcacbbcad3eb9590b8ba
ParentId: 0000000000000000
RequestId: 80007b25-000a-ff00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 4:16:32 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: fd62be1a6db5885d
TraceId: 07f606c80d01cc1ff5fe9262ed1fc823
ParentId: 0000000000000000
RequestId: 80004949-000b-dc00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 4:15:19 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: d04a26c062b52641
TraceId: 3d4e1ae009daa6f183c500cde39078cc
ParentId: 0000000000000000
RequestId: 80007af0-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:48:33 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 40118d12067b87f7
TraceId: 96f27f15039fbc5f9a4c060e87b58f3e
ParentId: 0000000000000000
RequestId: 8001fab1-0004-f700-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:18:29 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: f581c78cb26398f8
TraceId: 0949f688935ea39dc8045874461e30b0
ParentId: 0000000000000000
RequestId: 80004e20-0005-bf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:06:40 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 258863a7aac25029
TraceId: 6ae56701ab78c47acf2dd29bf689b719
ParentId: 0000000000000000
RequestId: 8000c864-0007-dd00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 3:05:02 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 6c4f459a01fd1458
TraceId: e0f72f68ea5a75f86b258bf539799e04
ParentId: 0000000000000000
RequestId: 8000bf47-0007-cf00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 2:42:54 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 4c7c043e5d4464d8
TraceId: 060f999a64069f860bb257291bd45e2a
ParentId: 0000000000000000
RequestId: 80007875-0003-3f00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: f03234ba-4e02-46bc-8cc4-3df9aadd2496
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/19/2026 2:08:51 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/19/2026 1:34:07 PM | VstsAgentService | 100 | 2026-05-19 18:34:07Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/19/2026 12:57:45 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 12:57:23 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 7:29:12 AM | .NET Runtime | 1026 | Application: 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/19/2026 5:05:31 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 5:05:08 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 3:48:06 AM | .NET Runtime | 1026 | Application: 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/19/2026 3:00:08 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/19/2026 2:39:57 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 12:30:43 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/18/2026 2:12:06 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 2:11:43 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 2:11:20 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 8:59:20 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/18/2026 7:02:18 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/18/2026 3:06:05 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/18/2026 2:28:57 AM | .NET Runtime | 1026 | Application: 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/18/2026 12:02:41 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 10:47:55 PM | .NET Runtime | 1026 | Application: 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/17/2026 7:30:49 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 5:04:39 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/17/2026 4:15:42 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 3:40:07 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 3:39:44 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 3:00:01 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/16/2026 11:55:09 PM | MsiInstaller | 11714 | Product: SolarWinds Agent 2026.1.1.3077 -- Error 1714. The older version of SolarWinds Agent 2026.1.1.3077 cannot be removed. Contact your technical support group. System Error 1612. |
| 5/16/2026 10:16:33 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/16/2026 9:28:44 PM | .NET Runtime | 1026 | Application: 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/16/2026 7:40:53 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/16/2026 5:47:43 PM | .NET Runtime | 1026 | Application: 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/16/2026 12:12:47 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: dcd5f1c10b0610fd
TraceId: a966cad3b3da5f864d659908d1cd00c3
ParentId: 0000000000000000
RequestId: 800079b2-000a-f200-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/16/2026 8:21:06 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/16/2026 3:28:34 AM | VstsAgentService | 100 | 2026-05-16 08:28:34Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/16/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/16/2026 12:31:05 AM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/15/2026 11:50:24 PM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Invalid pointer operation
|
| 5/15/2026 8:36:59 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/15/2026 5:02:29 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 1a589208005427a5
TraceId: a89c7d6a89bc3e2c6f808be0baab8ca7
ParentId: 0000000000000000
RequestId: 80010e18-0001-b900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:56:46 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 568e90065ff38600
TraceId: 1c514ddedf6f98b6def906ea1332f31f
ParentId: 0000000000000000
RequestId: 80002a54-0005-bb00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:55:12 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 2b7d5b1de164c1e9
TraceId: af0b5e2838e7deea6462fee4f4382b5c
ParentId: 0000000000000000
RequestId: 80004841-0002-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:54:39 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: b297c63ce7e6afc3
TraceId: 92b2cd53526002341881845b8db601b5
ParentId: 0000000000000000
RequestId: 80004819-0002-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:46:22 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: c79f41276581f0d6
TraceId: 395c3617f4e6fcb26d5355903208a6a8
ParentId: 0000000000000000
RequestId: 80009689-0004-e800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:44:31 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: b060feb7e77e9e11
TraceId: 6ddf8ce438da93bd8d7cc753e673e9cd
ParentId: 0000000000000000
RequestId: 80006910-0006-e100-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d3c4f10e-5664-4366-a5e1-db38779e4da7
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/15/2026 4:30:34 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 99386d8b10563aa0
TraceId: 5f1206891937a6b9e5bcffc0db18e214
ParentId: 0000000000000000
RequestId: 80009314-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:28:35 PM | .NET Runtime | 1026 | Application: 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/15/2026 4:21:41 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 0a32ee1e460b8e38
TraceId: df36d7b40a24d46db68539eba58892ce
ParentId: 0000000000000000
RequestId: 8000915a-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:21:35 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9a508302a42bb318
TraceId: 7b406fb234ad1be3ee02527413860958
ParentId: 0000000000000000
RequestId: 800194cd-0004-f700-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:20:56 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 031a3608f7191b29
TraceId: 686533f5106127127045ea0e9aff9475
ParentId: 0000000000000000
RequestId: 8000679d-0001-c900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 4:19:06 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/15/2026 2:46:01 PM | .NET Runtime | 1026 | Application: 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.InvalidOperationException: There is already an open DataReader associated with this Connection which must be closed first.
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at Microsoft.Data.SqlClient.SqlInternalTransaction.Rollback()
at Microsoft.Data.SqlClient.SqlInternalTransaction.Dispose(Boolean disposing)
at Microsoft.Data.SqlClient.SqlInternalTransaction.Dispose()
at Microsoft.Data.SqlClient.SqlTransaction.Dispose(Boolean disposing)
at Microsoft.EntityFrameworkCore.Storage.RelationalTransaction.Dispose()
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.Dispose()
at OpheliaSuiteV2.Core.DataAccess.SQL.... |
| 5/15/2026 2:16:10 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 1:23:14 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 96ae6145a318fad4
TraceId: 42e05f2b3647b4066af23266c0821d1b
ParentId: 0000000000000000
RequestId: 800486f4-0006-fd00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 12:28:39 PM | .NET Runtime | 1026 | Application: 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/15/2026 12:06:55 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 834255f904cf4764
TraceId: 3294baace1ab6ca1d93f1e55b4ffbcb2
ParentId: 0000000000000000
RequestId: 8000801e-0000-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 12:03:52 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: f9c57ebc9374e793
TraceId: ae957c8860bee84884537d029867936a
ParentId: 0000000000000000
RequestId: 80018aab-0007-ea00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 11:57:37 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 9c997c195c250517
TraceId: 84e2cb8de486c8744e72471efd96f420
ParentId: 0000000000000000
RequestId: 8000ed4c-0009-e800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: d72f2d0f-1fc7-4b25-a079-08345287307d
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/15/2026 3:13:54 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:13:39 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:12:39 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: 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/15/2026 3:00:02 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/14/2026 10:43:54 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: 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/14/2026 3:55:27 PM | OpheliaSuiteV2.Core.Orion.Manager | 10100 | Category: 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... |
| TimeCreated | ProviderName | Id | Message |
| 5/22/2026 9:19:56 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:19:56 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:19:56 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:19:56 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:19:56 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:18:22 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:12:19 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:12:19 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:12:19 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 9:10:08 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 8:33:53 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 8:33:52 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 8:33:52 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 8:33:52 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/22/2026 7:38:49 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/21/2026 5:20:58 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/21/2026 5:20:36 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/21/2026 5:19:42 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 AM | Microsoft-Windows-DistributedCOM | 10016 | The 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 AM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Service Control Manager | 7000 | The 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 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/16/2026 5:41:17 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/16/2026 5:41:17 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/16/2026 5:41:17 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/16/2026 5:41:16 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/15/2026 11:46:38 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/15/2026 7:58:55 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/15/2026 5:07:30 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 5:13:28 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 5:13:28 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 5:13:27 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 5:13:27 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 4:08:53 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 1:06:28 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/14/2026 12:15:16 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/13/2026 10:01:59 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 PM | Microsoft-Windows-DistributedCOM | 10016 | The 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 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/13/2026 10:07:02 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/13/2026 10:05:48 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/13/2026 10:05:48 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/13/2026 9:50:11 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/13/2026 9:50:11 AM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/11/2026 4:06:54 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable 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 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/11/2026 4:06:36 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/11/2026 4:06:35 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/11/2026 4:06:24 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/11/2026 4:05:03 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:51:02 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:46:01 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:41:01 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:36:00 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:31:00 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:24:59 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:19:59 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:13:58 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:08:58 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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:02:57 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:57:57 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:51:56 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:45:56 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:39:56 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:32:55 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:27:55 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:21:55 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:14:54 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:09:54 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 2:02:54 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:55:53 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:49:53 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:42:52 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:36:52 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:30:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:25:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:19:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:13:50 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:07:50 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 1:00:50 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:55:49 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:49:49 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:42:48 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:35:48 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:29:48 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:22:47 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:17:47 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:11:47 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 12:04:46 PM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:58:46 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:51:46 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:44:45 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:39:45 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:32:44 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:25:44 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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 11:20:44 AM | Microsoft-Windows-GroupPolicy | 1030 | The 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. |