Member Avatar for TomSojer

Guys i have a problem i don't know how to fix so i'm bagging for help!!!

On server 2003 standard acive directory i installed SQL expres embeded and wsus 3.0 with sp1. Since then i had errors in my log concerned with WMI service. Also i have trend micro installed that uses WMI. Can anyone tell me how to fix WMI without reinstalling 2003 or damaging any of those server instances. Complete procedure plz!!!

  • 2 Contributors
  • 4 Replies
  • 109 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by TomSojer

Dani AI

Generated

Short, practical WMI-repair checklist for Server 2003 — non-destructive first, more aggressive only if needed. This is offered as follow-up to (who reported WMI/service errors after adding server components) and to answer ’s prompt for concrete steps. Perform these in a maintenance window and with a System State backup before you change anything.

First checks and precautions:

  • Take a System State backup (or at least an image) so you can restore if something goes wrong.
  • Stop or disable any third‑party software that registers WMI providers (antivirus, WSUS/SQL services, management agents) before making repository changes.
  • Look at WMI logs at %windir%\system32\wbem\Logs\ to confirm the scope of failures and note any provider names.

Safe verification and repair (run from an elevated command prompt):

net stop winmgmt /y
winmgmt /verifyrepository
winmgmt /salvagerepository

If salvagerepository reports it cannot fix the repository, proceed carefully — either try winmgmt /resetrepository or rename the Repository folder and let WMI rebuild:

ren %windir%\system32\wbem\Repository Repository.old
net start winmgmt
for %i in (%windir%\system32\wbem\*.dll) do regsvr32 /s %i
for %i in (%windir%\system32\wbem\*.mof) do mofcomp %i

(If you place these in a batch file, use %%i instead of %i.)

Post-repair checks and follow-up:

  • Use wbemtest or wmimgmt.msc to connect to root\cimv2 and run a basic query.
  • Re-enable third‑party services. If an AV/management product still fails, repair or reinstall it so its WMI providers re-register.
  • Run sfc /scannow and check Event Viewer again. If Active Directory errors persist after WMI is healthy, run dcdiag/repadmin and address replication issues separately.
    If the repository rebuild breaks functionality you can’t recover, restore the System State backup and escalate to vendor support.

Recommended Answers

All 4 Replies

Member Avatar for DimaYasny

what errors are you getting? when exactly did they start appearing?

Member Avatar for TomSojer

error ID 1809 ursenv in aplication log and ID 1374,1377 NTDS inter-site messaging in directory service log.

Member Avatar for DimaYasny

have you tried googling those errors, or do you expect others to do that for you?

Member Avatar for TomSojer

yup i did but i didn't found anything useful to solve that.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.