Windows Server 2016 Standard 64-bit - unable to update since 2022/09

For some reason the TiWorker.exe process is crashing! And it seems it has to due with the Distributed File System Replication (DFSR) as mentioned before. Tomorrow I will do some research into this.

Rich (BB code): 
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_TiWorker.exe_661068f8211651f21f08ccdbb21c9e54c6daee_84d9be36_22c19e44

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f7fb24f-a8d4-412f-bfcf-9cf8ee7571ec
Report Status: 4
Hashed bucket: 
Cab Guid: %23

DFSRs (4116) \\.\C:\System Volume Information\DFSR\database_728C_4C86_8C4C_46B7\dfsr.db: The database engine stopped the instance (0). 
 
Dirty Shutdown: 0 
 
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.063, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.062, [10] 0.000, [11] 0.031, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.
 
Hi,

Please open an elevated command prompt, run the following command and copy and paste the result in your next post.
Code: 
fltmc filters
 
Hi,

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code: 
reg save "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" "%userprofile%\Desktop\Services.hiv"
  • Once done, a file will appear on your desktop, called Services.hiv.
  • ZIP this file and attach it to your next reply.
 
Hi,

The System Event log shows several issues about some volumes, do you recognize these volumes and are you aware of any issues with them?

Rich (BB code): 
An error was detected on device \Device\Harddisk3\DR3 during a paging operation.
Filter Manager failed to attach to volume '\Device\Harddisk3\DR4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
Filter Manager failed to attach to volume '\Device\Harddisk3\DR5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
Filter Manager failed to attach to volume '\Device\HarddiskVolume16'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.

Please run also the following tool.

Download and run DevNodeClean from Microsoft
  • Download
    55d04c7d453ca-Command_prompt_icon_%28windows%29.png
    DevNodeClean to your desktop.
  • Create a folder on your systemdrive called "C:\Tools\DevNodeClean"
  • Extract the folders x68 and x64 from devnodeclean.zip into the directory "C:\Tools\DevNodeClean"
  • Open an elevated command prompt and navigate to this folder with the command cd C:\Tools\DevNodeClean\x64.
  • Note! If the 64-bit version gives an error message, use the 32-bit (x86) version.
  • Copy and paste the following command into the prompt and press enter.
Code: 
DevNodeClean /n > "%userprofile%\desktop\DevNodeClean.txt"
  • Once done, a file will appear on your desktop, called DevNodeClean.txt.
  • Attach DevNodeClean.txt in your next reply.
 
This are the drives in the server right now. There was an attempt to install another 2 HD but the IT Tech didn't have the controller so we are still waiting in order to increase storage capacity. He tried and connected to the available slots for testing something but that was one time one or two months ago. Meanwhile I'm going to perform your suggestion and post the results on the next post.

1709733781323.png
 
Which drives are connected on the EP420i RAID controller, I guess some Seagate drives. And how many free space is available on them.
 
Data, for instance:
ERP - CentralGest Files and DB
DOCS - shared folder for documents

It was like this long before the update problem.

1709736911283.png
1709737004319.png
 
Ah, I see, I just translated it and means (Data)...

Are you able to provide the S.M.A.R.T data of the drives which are connected to the EP420i controller.
 
What I've also noticed is this. I was unable to detect the duplicate name even following the instructions. Could it have something to do with the issue ?
1709739517966.png
 
Jose Eduardo said:
What I've also noticed is this. I was unable to detect the duplicate name even following the instructions. Could it have something to do with the issue ?
Click to expand...

I noticed these error's as well and the following. However, some things are still a mystery to me.

Rich (BB code): 
The Connected Devices Platform Service service terminated with the following error: 
Unspecified error

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
 and APPID 
{F72671A9-012C-4725-9D2F-2A4D32D65169}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.

A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
 
Well I don't know if you still want to insist in persue of a cure for the update. It looks that there a couple of issues that are very weird and I really can't understand why the system stops even an offline update. It's annoying and I'm really sorry for making you waist your time like this.
 
This is an odd issue, but interesting to investigate further to find the cullprit. I can't unterstand the failed offline update with DISM either for now.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top