Windows 2019 AD Server crashes at startup

J

JDH

Member
Joined
Jul 5, 2022
Posts
6
Hi,

I've got an issue with a Physical AD server that crashes at startup. It seems to happened first time after à power shutdown during the OS shutdown.
Since this event, the server crashes at startup with the following errors (sorry for the french OS) :

Code: 
Internal error: An Active Directory Domain Services error has occurred.
 
Additional Data
Error value (decimal):
-501
Error value (hex):
fffffe0b
Internal ID:
407f3
Code: 
Impossible d’initialiser les services de domaine Active Directory.
 
Le service d’annuaire ne peut pas récupérer après cette erreur.
 
Action utilisateur
Restaurez le service d’annuaire local à partir du média de sauvegarde.
 
Données supplémentaires
Valeur de l’erreur :
-501 JET_errLogFileCorrupt, Log file is corrupt

Then it reboots with following events

Code: 
L’ordinateur a redémarré après une vérification d’erreur. La vérification d’erreur était : 0xc00002e2 (0xffffe60b21359110, 0xffffffffc0000001, 0x0000000000000000, 0x0000000000000000). Un vidage a été enregistré dans : C:\Windows\MEMORY.DMP. ID de rapport : ce6202cb-f0b1-40c8-b8b7-e5a7b5f38510.

Code: 
svchost (3464,R,98) PeerDistRepubCacheJetInstance: The log file at "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistRepub\edb.log" is corrupt with reason 'ValidSegmentAfterEmpty'. Last valid segment was 131, current segment is 133. The expected checksum was 1487431815566269919 (0x14a46b5b02711ddf) and the actual checksum was 1487431815566269919 (0x14a46b5b02711ddf). The read completed with error-code 0 (0x00000000).  If this condition persists then please restore the logfile from a previous backup.
Code: 
svchost (3464,R,98) PeerDistRepubCacheJetInstance: Des données endommagées ont été détectées pendant la récupération logicielle dans le fichier journal C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistRepub\edb.log. L’enregistrement de somme de contrôle qui a échoué se trouve à la position . Les données ne correspondant pas au schéma de remplissage du fichier journal sont apparues pour la première fois dans le secteur isec 133 reason ValidSegmentAfterEmpty. Ce fichier journal ayant été endommagé, il est inutilisable.
Code: 
svchost (3464,R,98) PeerDistRepubCacheJetInstance: La récupération/restauration de la base de données a échoué en raison d’une erreur inattendue -501.
Code: 
Impossible de démarrer un serveur DCOM : {9C38ED61-D565-4728-AEEE-C80952F0ECDE}. L’erreur
« 0 »
s’est produite lors du démarrage de la commande :
C:\Windows\System32\vdsldr.exe -Embedding

Also since this event, the Acronis Backup Software installed on this server doesn't work any more (does not start, nor backup, UI unreachable).

According the messages, it seems the AD database is somehow corrupted but I'm not the expert here.
Last, both DISM /CheckHealth and SFC fails : They just hangs, seemingly not starting at all.

So far, I didn't run the SysnativeBSODCollectionApp as it was not explicitly recommended for this OS but I can do it on demand.

Hereafter some details about the system :

  • System Manufacturer : DELL
  • Tower Server
  • Exact model number : PowerEdge T340
  • OS : Windows Server 2019 Essential
  • x64 (64bit)
  • What was original installed OS on system : Same
  • Preinstalled OEM version
  • Age of system : 3 years
  • Age of OS : 3 years
  • Have you re-installed the OS : No
  • CPU : Intel(R) Xeon(R) E-2124 CPU @ 3.30GHz
  • RAM : 16GB DDR4 Syn 2666 MT/s
  • Video Card : None
  • Power Supply : DELL 495W
  • Is driver verifier enabled or disabled : Yes, Dell Support Assist
  • What security software are you using : WithSecure Elements EPP for Servers Premium (formerly F-Secure Business)
  • Are you using proxy, vpn, ipfilters or similar software : No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) : No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? NO

Thanks in advance for your help
 
Hi,

Thanks for your answer.
Not tested this solution but actually, I'm not sure this would help as the root cause is different. There were no changes in the AD off our environment, nor demote of any AD server, but only a mains power loss during operation, then a failed reboot.
After the two first errors shown in the list of my first post, the system enter in a verification mode, then somehow manages to boot correctly.
It seems to happen at each restart now.

After the second and correct restart, most of the services are running correctly (Active Directory included). DCDiag is then reporting as healthy. The main issue we have there is that the Acronis backup software doesn't work at all and that both SFC and DISM don't work either.

The Directory Services Repair Mode might definitively help but this is the kind of solution that we would like to avoid as the system is running in production and it is the only server in the domain.

PS : No offense, but I don't understand why this topic has been moved as I believed a BSOD occurred during the startup of the system (I'm not on site, thus can't really observe the boot).
 
JDH said:
Is driver verifier enabled or disabled : Yes, Dell Support Assist
Click to expand...
If enabled, open an elevated command prompt and disable.

In the prompt type verifier /reset hit enter and reboot. Tell us about the dialogue with Dell Support Assist.

You can also post the SysnativeBSODCollectionApp results.
 
Not sure that Dell Support Assist acts like a driver verifier as I get this :

Code: 
C:\Users\Administrateur>verifier /query
No drivers are currently verified.

Anyway, I'm currently running the SysnativeBSODCollectionApp and will post the result asap
 
3 days after, the SysnativeBSODCollectionApp is stuck at "Waiting for system infos"...
I've stopped the process and zipped the datas already collected, you will find it attached.
 

Attachments

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

Back
Top