No hay datos.
No hay datos.
| TimeCreated | ProviderName | Id | Message |
|---|
| 5/20/2026 5:11:15 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/20/2026 5:10:52 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 7:53:44 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 10:30:38 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/19/2026 1:34:43 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 10:52:47 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 8:42:10 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/18/2026 1:14:50 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 3:45:30 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 6:34:12 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 1:17:31 AM | VstsAgentService | 100 | 2026-05-17 06:17:31Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/17/2026 1:11:24 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/17/2026 1:11:01 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/16/2026 3:12:22 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/16/2026 12:47:34 AM | VstsAgentService | 100 | 2026-05-16 05:47:34Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/15/2026 9:31:05 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 9:22:10 PM | VstsAgentService | 100 | 2026-05-16 02:22:10Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/15/2026 3:19:39 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 3:19:16 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 3:13:28 PM | Microsoft-Windows-RestartManager | 10006 | Application or service 'Trend Micro Deep Security Agent' could not be shut down. |
| 5/15/2026 11:13:21 AM | VstsAgentService | 100 | 2026-05-15 16:13:21Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/15/2026 10:55:59 AM | VstsAgentService | 100 | 2026-05-15 15:55:59Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/15/2026 9:31:01 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 9:30:38 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 7:35:51 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/15/2026 7:00:50 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/14/2026 4:28:01 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/14/2026 7:01:21 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/14/2026 7:00:58 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/13/2026 1:46:52 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/12/2026 9:55:00 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/12/2026 9:54:38 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/12/2026 10:00:43 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/11/2026 5:31:54 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/11/2026 2:58:14 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/10/2026 9:09:12 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/10/2026 10:42:20 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/10/2026 6:42:15 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/10/2026 2:30:35 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.IO.IOException: The handle is invalid.
at System.ConsolePal.WindowsConsoleStream.Write(ReadOnlySpan`1 buffer)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.WriteLine(String value)
at System.IO.TextWriter.SyncTextWriter.WriteLine(String value)
at System.Console.WriteLine(String value)
at OpheliaSuiteV2.Core.DataAccess.MongoDb.DbClient.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.Disp... |
| 5/10/2026 1:46:42 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/9/2026 4:21:35 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/9/2026 1:43:25 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/9/2026 11:44:57 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/9/2026 11:44:35 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/8/2026 7:59:36 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/8/2026 7:59:14 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/8/2026 11:30:05 AM | VstsAgentService | 100 | 2026-05-08 16:30:05Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/8/2026 10:27:09 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/8/2026 10:02:51 AM | VstsAgentService | 100 | 2026-05-08 15:02:51Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 5/8/2026 7:24:29 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/8/2026 7:24:07 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/8/2026 4:59:51 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/8/2026 1:24:42 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/7/2026 11:25:44 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/7/2026 11:25:21 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/6/2026 9:24:55 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/6/2026 9:24:32 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/6/2026 2:13:47 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/6/2026 2:13:25 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/6/2026 2:13:02 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/6/2026 1:33:02 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/5/2026 4:50:47 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/5/2026 3:18:41 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/5/2026 3:18:19 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/5/2026 2:17:54 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/4/2026 11:45:44 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/4/2026 6:46:53 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/3/2026 1:12:21 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/2/2026 8:12:08 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/2/2026 5:17:08 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/1/2026 11:12:14 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/1/2026 11:11:52 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/1/2026 11:11:29 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/1/2026 5:14:12 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 5/1/2026 1:18:44 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/30/2026 9:45:15 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/30/2026 9:44:53 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)>. |
| 4/30/2026 1:04:07 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/29/2026 3:04:28 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/29/2026 7:58:44 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/28/2026 11:43:24 PM | VstsAgentService | 100 | 2026-04-29 04:43:24Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 4/28/2026 10:59:06 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/28/2026 11:04:53 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)>. |
| 4/28/2026 11:04:31 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/28/2026 11:04:08 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/27/2026 7:46:05 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/27/2026 7:45:42 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/27/2026 10:12:20 AM | VstsAgentService | 100 | 2026-04-27 15:12:20Z: Agent connect error: The SSL connection could not be established, see inner exception.. Retrying until reconnected. |
| 4/27/2026 3:12:50 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/27/2026 3:12:28 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/27/2026 3:12:05 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 8:03:38 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:53:31 PM | VstsAgentService | 100 | 2026-04-26 19:53:31Z: Agent connect error: The SSL connection could not be established, see inner exception.. Retrying until reconnected. |
| 4/26/2026 9:27:47 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 7:47:45 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)>. |
| 4/26/2026 7:13:21 AM | VstsAgentService | 100 | 2026-04-26 12:13:21Z: Agent connect error: The SSL connection could not be established, see inner exception.. Retrying until reconnected. |
| 4/26/2026 5:17:47 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 3:18:05 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 3:03:03 AM | VstsAgentService | 100 | 2026-04-26 08:03:03Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 4/26/2026 2:39:29 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:29:23 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:17:00 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:10:01 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:06:28 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 2:05:12 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/26/2026 1:39:01 AM | Microsoft-Windows-User Profiles Service | 1552 | User hive is loaded by another process (Registry Lock) Process name: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.8642_none_56cfd5f3992f328d\TiWorker.exe, PID: 2320, ProfSvc PID: 2356. |
| 4/26/2026 1:37:33 AM | Microsoft-Windows-Perflib | 1000 | Access to performance data was denied to user "SYSTEM" (value from GetUserName() for the running thread) as attempted from module "C:\Program Files\NSClient++\nscp.exe" (value from GetModuleFileName() for the binary that issued the query). |
| 4/26/2026 1:37:26 AM | Application Error | 1000 | Faulting application name: DoubleTake.exe, version: 8.5.1.72, time stamp: 0x63287f1b
Faulting module name: DoubleTake.exe, version: 8.5.1.72, time stamp: 0x63287f1b
Exception code: 0xc0000005
Fault offset: 0x000000000008605a
Faulting process id: 0x11f8
Faulting application start time: 0x01dcb9f29b93022a
Faulting application path: C:\Program Files\Carbonite\Replication\DoubleTake.exe
Faulting module path: C:\Program Files\Carbonite\Replication\DoubleTake.exe
Report Id: e5bb045a-d443-4e06-abf6-bea4ff4ac9b3
Faulting package full name:
Faulting package-relative application ID: |
| 4/26/2026 1:24:43 AM | Double-Take | 4070 | An error occurred while reading data for connection 12. All data needs to be remirrored. See the log for details. |
| 4/26/2026 1:13:45 AM | Double-Take | 4070 | An error occurred while reading data for connection 12. All data needs to be remirrored. See the log for details. |
| 4/26/2026 1:00:03 AM | VstsAgentService | 100 | 2026-04-26 06:00:00Z: Agent connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected. |
| 4/26/2026 12:53:28 AM | Double-Take | 4070 | An error occurred while reading data for connection 12. All data needs to be remirrored. See the log for details. |
| 4/26/2026 12:38:50 AM | Double-Take | 4070 | An error occurred while reading data for connection 12. All data needs to be remirrored. See the log for details. |
| 4/25/2026 5:58:20 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/25/2026 4:36:38 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/25/2026 3:28:46 AM | VstsAgentService | 100 | 2026-04-25 08:28:46Z: Agent connect error: The SSL connection could not be established, see inner exception.. Retrying until reconnected. |
| 4/24/2026 12:04:36 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)>. |
| 4/23/2026 7:30:11 PM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| 4/23/2026 3:00:27 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)>. |
| 4/23/2026 3:00:04 AM | OCS Inventory Service | 20 | Service encounter error <OCS Inventory NG Agent encounter an error (exit code is 4 => Failed to talk with Communication Server)>. |
| TimeCreated | ProviderName | Id | Message |
|---|
| 5/19/2026 7:34:35 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/19/2026 7:34:34 PM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/17/2026 12:03:40 PM | Service Control Manager | 7032 | The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the MongoDB Server (MongoDB6) service, but this action failed with the following error:
An instance of the service is already running. |
| 5/17/2026 12:02:40 PM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 6:15:08 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/17/2026 6:15:07 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/17/2026 6:15:07 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/17/2026 6:15:07 AM | Microsoft-Windows-DistributedCOM | 10001 | Unable to start a DCOM Server: {995C996E-D918-4A8C-A302-45719A6F4EA7} as Unavailable/Unavailable. The error:
"0"
Happened while starting this command:
C:\Windows\System32\rundll32.exe C:\Windows\System32\shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7} -Embedding |
| 5/17/2026 3:40:06 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:39:02 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:37:59 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:36:55 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:35:52 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:34:49 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:33:45 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:32:42 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:31:38 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:30:35 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:29:31 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:28:28 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:27:25 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:26:21 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:25:18 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:24:14 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:23:11 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:22:08 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:21:04 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:20:01 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:18:57 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:17:54 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:16:50 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:15:47 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:14:43 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:13:40 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:12:37 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:11:33 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:10:30 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:09:27 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:08:23 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:07:20 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:06:16 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:05:13 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:04:10 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:03:07 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:02:03 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 3:01:00 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:59:57 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:58:53 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:57:50 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:56:47 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:55:44 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:54:40 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:53:37 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:52:34 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:51:30 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:50:27 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:49:24 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:48:21 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:47:17 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:46:14 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:45:11 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:44:07 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:43:04 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:42:01 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:40:57 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:39:54 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:38:51 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:37:47 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:36:44 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:35:41 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:34:38 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:33:35 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:32:31 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:31:28 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:30:25 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:29:21 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:28:18 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:27:15 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:26:11 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:25:08 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:24:05 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:23:01 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:21:58 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:20:54 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:19:51 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:18:48 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 2:17:43 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/17/2026 12:33:49 AM | 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 9:58:52 AM | Service Control Manager | 7031 | The MongoDB Server (MongoDB6) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. |
| 5/15/2026 3:16:28 PM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/15/2026 3:16:28 PM | Service Control Manager | 7006 | The ScRegSetValueExW call failed for Start with the following error:
Access is denied. |
| 5/15/2026 10:21:40 AM | Microsoft-Windows-DistributedCOM | 10010 | The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. |
| 5/14/2026 4:16:53 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 4:10:53 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 4:04:52 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:58:52 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:51:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:44:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:37:51 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:30:50 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:25:50 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:20:49 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:14:48 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:08:47 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 3:01:47 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 2:55:46 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 2:48:46 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 2:41:46 PM | Microsoft-Windows-GroupPolicy | 1030 | The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. |
| 5/14/2026 2:35:45 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/14/2026 2:30:45 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/14/2026 2:24:44 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/14/2026 2:17:44 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/14/2026 2:10:43 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/14/2026 2:05:43 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/14/2026 1:59:43 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/14/2026 1:53:42 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/14/2026 1:46:42 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/14/2026 1:40:41 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/14/2026 1:33:41 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/14/2026 1:28:41 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. |