Microsoft Windows Server 2016 Standard 10.0.14393 .Net Errors

[Itachiness]

I'm getting .Net Errors popping up in my eventlog for an application and it's affecting other applications as well.

I had this issue a few months ago and posted about it and got it resolved, I'm not sure why it's continuing to happen in this particular environment.

.Net Runtime Application Log Error
- System

- Provider

[ Name] .NET Runtime

- EventID 1026

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2025-05-22T01:26:59.028486400Z

EventRecordID 530296

Channel Application

Computer <HOSTNAME>

Security


- EventData

Application: CagService.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at CentraStage.Cag.Core.Agent.CsConnection.WebPortOk() at CentraStage.Cag.Core.Agent.CsConnection.MaintainConnection(System.Action`2<CentraStage.Cag.Core.Messaging.XmlRpcIncomingControlMessage,CentraStage.Cag.Core.Messaging.AddToOutgoingQueueDelegate>) at CentraStage.Cag.Core.Agent.MainLoop+DelegateTask.Execute() at CentraStage.Cag.Core.Agent.MainLoop.Loop() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()

 

[Windows Update Bot]

Hi @Itachiness,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Itachiness]

I attached the wrong CBS/Component logs, use these instead

 

[PeterJ]

Hello and welcome,

Please do following:

FRST Scan:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Attach the logfile Fixlog.txt to your next reply.

 

[Itachiness]

Attached is the fixlog

Still getting errors for the cagservice in event log. 3 recurring errors in this order.

Example:
1.
EventID: 1000
Faulting application name: CagService.exe, version: 4.4.2248.2248, time stamp: 0x681c99a5
Faulting module name: KERNELBASE.dll, version: 10.0.14393.8062, time stamp: 0x6813e95b
Exception code: 0xe0434352
Fault offset: 0x0000000000026ea8
Faulting process id: 0x590c
Faulting application start time: 0x01dbd3bf839a2e7e
Faulting application path: C:\Program Files (x86)\CentraStage\CagService.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 18a2ef96-dd15-4156-babf-ffc0fa9511b3
Faulting package full name:
Faulting package-relative application ID:

2.
EventID: 1026
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at CentraStage.Cag.Core.Agent.CsConnection.WebPortOk()
at CentraStage.Cag.Core.Agent.CsConnection.MaintainConnection(System.Action`2<CentraStage.Cag.Core.Messaging.XmlRpcIncomingControlMessage,CentraStage.Cag.Core.Messaging.AddToOutgoingQueueDelegate>)
at CentraStage.Cag.Core.Agent.MainLoop+DelegateTask.Execute()
at CentraStage.Cag.Core.Agent.MainLoop.Loop()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

3.
EventID: 0
Service cannot be started. System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at CentraStage.Cag.Core.Agent.MainLoop.QueueWait(DelegateTask t)
at CentraStage.Cag.Core.Agent.AgentEngine.Start(Boolean block, Boolean bogus)
at Service.CagService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

[PeterJ]

Perform following steps to repair a missing file.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Itachiness]

Looks like i'm still getting the same results, attached is the CBS log file.

 

[PeterJ]

Export registry as hive

• Click on the Start button and in the search box, type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  
  
• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, please upload to Gofile or WeTransfer and just provide the downloadlink here.

 

[Itachiness]

File attached.

 

[PeterJ]

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Itachiness]

SFCFix version 3.0.2.1 by niemiro.
Start time: 2025-06-04 12:36:55.847
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\username\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum

Successfully copied file C:\Users\twkaufman\AppData\Local\niemiro\Archive\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat to C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat.
Successfully copied file C:\Users\twkaufman\AppData\Local\niemiro\Archive\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum to C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum.

Successfully restored ownership for C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully restored permissions on C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully restored ownership for C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum
Successfully restored permissions on C:\Windows\servicing\packages\Microsoft-Windows-BITSExtensions-Server-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 18 datablocks.
Finish time: 2025-06-04 12:37:03.034
Script hash: l3cY85uDPifkdmtYhZIsjgM3vSdPZxncyWkttrPRL90=
----------------------EOF-----------------------



Still getting the same results.

 

[PeterJ]

Next fix.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Itachiness]

Sorry, i've been out so i've been really slow to respond.

Attached is the CBS logs

Here's the output:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2025-06-05 16:19:26.183
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\twkaufman\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\servicing\packages\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\packages

Successfully copied file C:\Users\<username>\AppData\Local\niemiro\Archive\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat to C:\Windows\servicing\packages\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat.
Successfully copied file C:\Users\<username>\AppData\Local\niemiro\Archive\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum to C:\Windows\servicing\packages\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum.

Successfully restored ownership for C:\Windows\servicing\packages\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully restored permissions on C:\Windows\servicing\packages\Microsoft-Windows-WinRM-IIS-Extensions-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat
Successfully restored ownership for C:\Windows\servicing\packages
Successfully restored permissions on C:\Windows\servicing\packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 19 datablocks.
Finish time: 2025-06-05 16:19:57.121
Script hash: EwYQbRCyeni6TQPArIeKle3yxMam2BhCpCC4745zO4s=
----------------------EOF-----------------------

Still seeing the same behavior

 

[PeterJ]

No problem on the delay.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.