| TimeCreated | ProviderName | Id | Message |
|---|
| 5/29/2026 10:37:11 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 1ad2cd269c6c32ae
TraceId: 731bdf513dfe4b1913a2981d61d22e01
ParentId: 0000000000000000
RequestId: 80001b5e-0007-7800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 10:32:56 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 05e17e26d146f807
TraceId: 69e190fef513ff8841ba6fb85cb61495
ParentId: 0000000000000000
RequestId: 800059d7-0005-de00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 10:31:44 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 26f22db53d9fad1c
TraceId: 75cc07cbf05b4030d3df5254512a147a
ParentId: 0000000000000000
RequestId: 800092a5-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 3:00:03 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/29/2026 2:57:57 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/29/2026 2:57:42 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/29/2026 2:57:13 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/29/2026 2:56:58 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/29/2026 2:56:43 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:56:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:56:13 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:55:57 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/29/2026 2:55:42 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/29/2026 2:54:57 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/29/2026 2:54:42 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/29/2026 2:53:57 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/29/2026 2:53:42 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/29/2026 2:52:57 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/29/2026 2:52:42 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/29/2026 2:52:13 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/29/2026 2:51:58 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/29/2026 2:51:43 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/29/2026 2:51:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:51:12 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/29/2026 2:50:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:50:42 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService
EventId: 0
ValidateTrackingQueueService.Execute.
Exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole... |
| 5/29/2026 2:50:30 AM | 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): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj... |
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 20004 | Category: Microsoft.EntityFrameworkCore.Database.Connection
EventId: 20004
An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
|
| 5/29/2026 2:49:57 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/29/2026 2:49:42 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/29/2026 2:48:57 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/29/2026 2:48:42 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/29/2026 2:47:57 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/29/2026 2:47:42 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/29/2026 2:47:13 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/29/2026 2:46:58 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/29/2026 2:46:43 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/29/2026 2:46:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:46:12 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:45:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:45:42 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/29/2026 2:44:57 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/29/2026 2:44:42 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/29/2026 2:43:57 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/29/2026 2:43:42 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/29/2026 2:42:57 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/29/2026 2:42:42 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/29/2026 2:42:13 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/29/2026 2:41:58 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/29/2026 2:41:43 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/29/2026 2:41:28 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/29/2026 2:41:12 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:42 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService
EventId: 0
ValidateTrackingQueueService.Execute.
Exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole... |
| 5/29/2026 2:40:30 AM | 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): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj... |
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 20004 | Category: Microsoft.EntityFrameworkCore.Database.Connection
EventId: 20004
An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
|
| TimeCreated | ProviderName | Id | Message |
|---|
| 5/29/2026 1:51: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/29/2026 10:37:11 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 1ad2cd269c6c32ae
TraceId: 731bdf513dfe4b1913a2981d61d22e01
ParentId: 0000000000000000
RequestId: 80001b5e-0007-7800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 10:32:56 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 05e17e26d146f807
TraceId: 69e190fef513ff8841ba6fb85cb61495
ParentId: 0000000000000000
RequestId: 800059d7-0005-de00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 10:31:44 AM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 26f22db53d9fad1c
TraceId: 75cc07cbf05b4030d3df5254512a147a
ParentId: 0000000000000000
RequestId: 800092a5-0008-ee00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: a0211063-7e73-4421-a40b-1fd59dc5b9d7
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/29/2026 6:16:03 AM | .NET 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/29/2026 4:04:36 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/29/2026 3:00:03 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
BackgroundService.ExecuteAsync. A task was canceled.
|
| 5/29/2026 2:57:57 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/29/2026 2:57:42 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/29/2026 2:57:13 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/29/2026 2:56:58 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/29/2026 2:56:43 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:56:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:56:13 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:55:57 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/29/2026 2:55:42 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/29/2026 2:54:57 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/29/2026 2:54:42 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/29/2026 2:53:57 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/29/2026 2:53:42 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/29/2026 2:52:57 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/29/2026 2:52:42 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/29/2026 2:52:13 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/29/2026 2:51:58 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/29/2026 2:51:43 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/29/2026 2:51:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:51:12 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/29/2026 2:50:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:50:42 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService
EventId: 0
ValidateTrackingQueueService.Execute.
Exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole... |
| 5/29/2026 2:50:30 AM | 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): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=4; handshake=2; [Login] initialization=0; authentication=0; [Post-Login] complete=14004;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj... |
| 5/29/2026 2:50:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 20004 | Category: Microsoft.EntityFrameworkCore.Database.Connection
EventId: 20004
An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
|
| 5/29/2026 2:49:57 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/29/2026 2:49:42 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/29/2026 2:48:57 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/29/2026 2:48:42 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/29/2026 2:47:57 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/29/2026 2:47:42 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/29/2026 2:47:13 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/29/2026 2:46:58 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/29/2026 2:46:43 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/29/2026 2:46:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:46:12 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:45:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:45:42 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/29/2026 2:44:57 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/29/2026 2:44:42 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/29/2026 2:43:57 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/29/2026 2:43:42 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/29/2026 2:42:57 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/29/2026 2:42:42 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/29/2026 2:42:13 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/29/2026 2:41:58 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/29/2026 2:41:43 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/29/2026 2:41:28 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/29/2026 2:41:12 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:57 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:42 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Services.ValidateTrackingQueueService
EventId: 0
ValidateTrackingQueueService.Execute.
Exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boole... |
| 5/29/2026 2:40:30 AM | 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): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=7; [Login] initialization=0; authentication=0; [Post-Login] complete=13999;
---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj... |
| 5/29/2026 2:40:30 AM | OpheliaSuiteV2.Core.Orion.Manager | 20004 | Category: Microsoft.EntityFrameworkCore.Database.Connection
EventId: 20004
An error occurred using the connection to database 'OpheliaSuite' on server 'SRVCLSGDEA\SGDEAPRY,1633'.
|
| 5/29/2026 2:39:57 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/29/2026 2:39:42 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/29/2026 2:38:57 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/29/2026 2:38:42 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/29/2026 2:37:57 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/29/2026 2:37:42 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/29/2026 2:37:13 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/29/2026 2:36:58 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/29/2026 2:36:43 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
TaskWithTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:36:28 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlertTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:36:13 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/29/2026 2:35:57 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/29/2026 2:35:42 AM | OpheliaSuiteV2.Core.BPMTimer | 0 | Category: OpheliaSuiteV2.Core.BPMTimer.Worker
EventId: 0
AlarmTimerJob: Error TSDmrAncestro.ProgramLogin: Error on data reading from the connection:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Socket Error Code: 10060($274C)
|
| 5/29/2026 2:34:57 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/29/2026 2:34:42 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/29/2026 2:14:42 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/29/2026 2:13:57 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/29/2026 2:13:42 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/29/2026 2:12:57 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/29/2026 2:12:42 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/29/2026 2:11:57 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/29/2026 2:11:42 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/28/2026 7:26:59 PM | IIS AspNetCore Module V2 | 1034 | Could not load configuration. Exception message:
Attribute 'processPath' is required. |
| 5/28/2026 7:20:37 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/28/2026 6:02:07 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/28/2026 5:18:27 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: f93ab097de973576
TraceId: f715bd97c9d0b7f82e939d15246e324f
ParentId: 0000000000000000
RequestId: 8000300c-0008-9400-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
|
| 5/28/2026 5:05:22 PM | OpheliaSuiteV2.Core.Orion.Manager | 0 | Category: OpheliaSuiteV2.Core.Orion.Manager.Jobs.ValidateTrackingQueueJob
EventId: 0
ValidateTrackingQueueJob.Execute. Error al obtener seguimietos encolados perdidos.
|
| 5/28/2026 5:05:22 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/28/2026 5:05:22 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... |
| 5/28/2026 5:05:22 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
Failed executing DbCommand (300,021ms) [Parameters=[@companyCode='?' (DbType = Int16), @segContList1='?' (Size = 40), @segContList2='?' (Size = 40), @segContList3='?' (Size = 40), @segContList4='?' (Size = 40), @segContList5='?' (Size = 40), @segContList6='?' (Size = 40), @segContList7='?' (Size = 40), @segContList8='?' (Size = 40), @segContList9='?' (Size = 40), @segContList10='?' (Size = 40), @segContList11='?' (Size = 40), @segContList12='?' (Size = 40), @segContList13='?' (Size = 40), @segContList14='?' (Size = 40), @segContList15='?' (Size = 40), @segContList16='?' (Size = 40), @segContList17='?' (Size = 40), @segContList18='?' (Size = 40), @segContList19='?' (Size = 40), @segContList20='?' (Size = 40), @segContList21='?' (Size = 40), @segContList22='?' (Size = 40), @segContList23='?' (Size = 40), @segContLi... |
| 5/28/2026 5:03:38 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 35e74462dd43d223
TraceId: 07639048e76a7e849bca80c385013bdf
ParentId: 0000000000000000
RequestId: 800038a9-0005-c100-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
|
| 5/28/2026 4:58:31 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 5b9c227d3ba1e757
TraceId: 5f5fb317c4742de8b8d1e84f5601c513
ParentId: 0000000000000000
RequestId: 80001c08-0006-e900-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
|
| 5/28/2026 4:55:12 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: 34faab5de35afe97
TraceId: 16500e47b04f90eebbd22d2de317ab61
ParentId: 0000000000000000
RequestId: 80001063-0009-3c00-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio BEGINPROCESS_RESPUESTAPQRSD https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/BPM.BeginProcess/Api/BeginProcess
|
| 5/28/2026 3:16:26 PM | .NET Runtime | 1000 | Category: Microsoft.EntityFrameworkCore.Query
EventId: 10100
SpanId: b29b972bf99985e6
TraceId: 60f210e43b3a24d0ea4398e54ddeb511
ParentId: 506ea13e253b25a5
RequestId: 8000205c-0002-4000-b63f-84710c7967bb
RequestPath: /RadicateApiNew_EF/Api/Radicate/RequestRadicateAsync
ActionId: 90703612-e81d-487e-9ac6-561443026d99
ActionName: OpheliaSuiteV2.CoreEF.Hermes.RadicateApi.Controllers.RadicateController.RequestRadicateAsync (OpheliaSuiteV2.CoreEF.Hermes.RadicateApi)
An exception occurred while iterating over the results of a query for context type 'OpheliaSuiteV2.CoreEF.Hermes.RadicateApi.DataAccess.DMSDbContext'.
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 Microsof... |
| 5/28/2026 3:16:26 PM | .NET Runtime | 1000 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: b29b972bf99985e6
TraceId: 60f210e43b3a24d0ea4398e54ddeb511
ParentId: 506ea13e253b25a5
RequestId: 8000205c-0002-4000-b63f-84710c7967bb
RequestPath: /RadicateApiNew_EF/Api/Radicate/RequestRadicateAsync
ActionId: 90703612-e81d-487e-9ac6-561443026d99
ActionName: OpheliaSuiteV2.CoreEF.Hermes.RadicateApi.Controllers.RadicateController.RequestRadicateAsync (OpheliaSuiteV2.CoreEF.Hermes.RadicateApi)
Failed executing DbCommand (30,007ms) [Parameters=[@__caseId_0='?' (DbType = Guid)], CommandType='Text', CommandTimeout='30']
-- Repository:RequestFilesRepository-GetAllAsync
SELECT TOP(1) [r].[FileNumber]
FROM [RequestFiles] AS [r]
WHERE [r].[CaseId] = @__caseId_0
|
| 5/28/2026 2:55:27 PM | .NET Runtime | 1000 | Category: OpheliaSuiteV2.Core.WSAdmin.Api.Domain.Services.ConfigurationRestServiceDomainService
EventId: 0
SpanId: c252c7e2da755683
TraceId: 32a1fcfd49bef7afa1470b518bb83361
ParentId: 0000000000000000
RequestId: 80000544-0002-2800-b63f-84710c7967bb
RequestPath: /WSApi/api/ConfigurationRestService/ResolveRestService
ActionId: c8b928c2-dc3e-499f-b0ca-7e339047a76e
ActionName: OpheliaSuiteV2.Core.WSAdmin.Api.Controllers.ConfigurationRestServiceController.ResolveRestService (OpheliaSuiteV2.Core.WSAdmin.Api)
ERROR consumiendo el servicio REGLA_APROBADOR https://fiduprevisorafidugestor.digitalwaresaas.com.co:8082/HadesApi/api/BRM/ExecuteRuleDynamic
|
| 5/28/2026 1:06:45 PM | Application Error | 1000 | Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xcfdb13d8
Faulting module name: KERNELBASE.dll, version: 10.0.17763.8755, time stamp: 0x44e2a81a
Exception code: 0xe0434352
Fault offset: 0x0000000000041b39
Faulting process id: 0x984
Faulting application start time: 0x01dceecbce205a5d
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 0afe0561-e6ec-4c80-853d-22b46c29e938
Faulting package full name:
Faulting package-relative application ID: |
| 5/28/2026 1:06:45 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: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1... |
| 5/28/2026 12:06:24 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: ed526d584402e1cf
TraceId: 37eb77172ede678463af5207df574002
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1RIR
RequestId: 0HNLSJVPN1RIR:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (9,784ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SEG... |
| 5/28/2026 12:06:07 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: ed526d584402e1cf
TraceId: 37eb77172ede678463af5207df574002
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1RIR
RequestId: 0HNLSJVPN1RIR:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (13,908ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 12:05:50 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: ed526d584402e1cf
TraceId: 37eb77172ede678463af5207df574002
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1RIR
RequestId: 0HNLSJVPN1RIR:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (3,139ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SEG... |
| 5/28/2026 12:05:45 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: ed526d584402e1cf
TraceId: 37eb77172ede678463af5207df574002
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1RIR
RequestId: 0HNLSJVPN1RIR:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (17,398ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 12:05:28 PM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: ed526d584402e1cf
TraceId: 37eb77172ede678463af5207df574002
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1RIR
RequestId: 0HNLSJVPN1RIR:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (21,117ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 12:02:58 PM | .NET Runtime | 1000 | Category: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware
EventId: 1
SpanId: 25b1e1d0fc60b7ea
TraceId: b7665fcd58aa3ab2bd88685315d21b7c
ParentId: 2fceec720819bacc
RequestId: 80001117-0003-7100-b63f-84710c7967bb
RequestPath: /RadicateApiNew_EF/api/Radicate/RequestRadicateAsync
An unhandled exception has occurred while executing the request.
Exception:
System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure' to the 'UseSqlServer' call.
---> Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another requ... |
| 5/28/2026 11:47:00 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 2973007a5f20dcd1
TraceId: a7a26789aa8e87cfa9733d6e7c408660
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1OBD
RequestId: 0HNLSJVPN1OBD:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (12,098ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:37:31 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (76,129ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:35:59 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (39,047ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:35:12 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (40,578ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:34:28 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (61,520ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:33:26 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (7,452ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SEG... |
| 5/28/2026 11:33:18 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: 0ba08d29fd823aa0
TraceId: 3f6d6492646b38068a8a881599f7d4b3
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000005
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (25,384ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:32:51 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (12,226ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:32:23 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (14,927ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:32:01 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (14,855ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SE... |
| 5/28/2026 11:31:43 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (6,396ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[SEG... |
| 5/28/2026 11:31:35 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (237,606ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[S... |
| 5/28/2026 11:27:38 AM | OpheliaSuiteV2.Core.Orion.Manager | 20102 | Category: Microsoft.EntityFrameworkCore.Database.Command
EventId: 20102
SpanId: d3014d2c4b691645
TraceId: 2c72573ef24b0370a47c1536eb605f9e
ParentId: 0000000000000000
ConnectionId: 0HNLSJVPN1LIA
RequestId: 0HNLSJVPN1LIA:00000003
RequestPath: /omanager.OManager/UpdateTrackingErrorState
Failed executing DbCommand (115,713ms) [Parameters=[@p='?' (Size = 4000), @p4='?' (Size = 1), @p5='?' (Size = 50), @p6='?' (Size = 300), @p7='?' (DbType = DateTime2), @8__locals1_companyCode='?' (DbType = Int16), @8__locals1_caseCode='?' (Size = 40), @8__locals1_trackingCode='?' (Size = 40)], CommandType='Text', CommandTimeout='300']
UPDATE [w]
SET [w].[SEG_ERRO] = @p,
[w].[SEG_ESTE] = @p4,
[w].[SEG_IPAD] = @p5,
[w].[AUD_USUA] = @p6,
[w].[AUD_UFAC] = @p7
FROM [WF_SEGUI] AS [w]
WHERE [w].[EMP_CODI] = @8__locals1_companyCode AND [w].[CAS_CONT] = @8__locals1_caseCode AND [w].[S... |
| TimeCreated | ProviderName | Id | Message |
|---|
| 5/28/2026 11:17:34 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/28/2026 11:17:04 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/26/2026 12:45: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/26/2026 12:25:04 PM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/26/2026 11:22:59 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/26/2026 10:28:28 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/26/2026 10:28:27 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/25/2026 11:47:03 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/25/2026 11:46:35 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/25/2026 11:46:35 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/25/2026 11:46:34 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/25/2026 11:46:34 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/25/2026 11:46:33 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/25/2026 11:46:33 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/25/2026 6:23:29 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/25/2026 6:23:28 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/25/2026 6:23:28 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/25/2026 6:23:28 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/25/2026 6:23:27 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:16: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/24/2026 5:16: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/24/2026 5:16: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/24/2026 5:16: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/24/2026 5:16:15 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:01:41 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:01:41 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:01:41 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:01:41 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/24/2026 5:01:41 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/23/2026 11:46: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/23/2026 11:46: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/23/2026 11:46: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/23/2026 11:23:30 PM | Microsoft-Windows-TPM-WMI | 1801 | Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here.
DeviceAttributes: BaseBoardManufacturer:Intel Corporation;FirmwareManufacturer:VMware, Inc.;FirmwareVersion:VMW71.00V.21100432.B64.2301110304;OEMModelNumber:VMware7,1;OEMModelBaseBoard:440BX Desktop Reference Platform;OEMModelSystemFamily:;OEMManufacturerName:VMware, Inc.;OEMModelSKU:;OSArchitecture:amd64;
BucketId: d23cb67dc3822dcd55f3389e1d18ef1d7106588149c6c8c8d2f98ff80600e0d8
BucketConfidenceLevel: Under Observation - More Data Needed
UpdateType:
For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018. |
| 5/23/2026 11:18:22 PM | iScsiPrt | 10 | Login request failed. The login response packet is given in the dump data. |
| 5/23/2026 11:18:23 PM | Microsoft-Windows-WinRM | 10150 | The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured.
User Action
Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command:
winrm get winrm/config/service
Additional Data
Listener transport: HTTP
Listener address: * |
| 5/23/2026 11:18:23 PM | Microsoft-Windows-WinRM | 10150 | The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured.
User Action
Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command:
winrm get winrm/config/service
Additional Data
Listener transport: HTTP
Listener address: * |
| 5/23/2026 11:18:21 PM | Service Control Manager | 7000 | The luafv service failed to start due to the following error:
This driver has been blocked from loading |
| 5/23/2026 11:17:39 PM | Service Control Manager | 7024 | The New Relic Infrastructure Agent service terminated with the following service-specific error:
The system cannot find the file specified. |
| 5/23/2026 11:16:51 PM | Service Control Manager | 7043 | The Double-Take service did not shut down properly after receiving a preshutdown control. |
| 5/23/2026 11:15:22 PM | Service Control Manager | 7023 | The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired. |
| 5/23/2026 11:15: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/23/2026 11:15: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/23/2026 11:14:59 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/23/2026 11:14:59 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/23/2026 10:47:48 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/23/2026 10:47:48 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: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. |