Start with the symptom

Start by defining exactly what is failing, which server is affected and whether the problem affects one client or multiple systems.

Filter the correct log

Check the local configuration that controls the operation. Compare it with a known-good server or client where possible.

Review time and source

Run a direct test for the dependency. Capture the exact result so you can distinguish configuration, connectivity and application failures.

Correlate related events

Review the relevant server-side configuration and logs. Look for timestamps that match the reported failure.

Validate the underlying service

Validate security, permissions and service state before changing production configuration.

Document the resolution

After the fix, repeat the original test and document the working configuration so the procedure can be reused.

Useful commands

Run these checks from an elevated PowerShell session where appropriate. Replace example names with your environment.

Recent errors

Get-WinEvent -FilterHashtable @{LogName='System';Level=2} -MaxEvents 20 | Select TimeCreated,ProviderName,Id,Message

Service errors

Get-WinEvent -FilterHashtable @{LogName='System';StartTime=(Get-Date).AddHours(-4)} | Where-Object Message -match 'service' | Select -First 20 TimeCreated,Id,Message

Quick troubleshooting path

Use this sequence to isolate the failing dependency before changing production configuration.

Troubleshooting decision path for windows event viewer troubleshooting

What good troubleshooting looks like

Good infrastructure troubleshooting is evidence-driven. Capture the original state, test the dependency that can prove or disprove your hypothesis, make the smallest safe change and repeat the original test.

Example workflow
Symptom → hypothesis → direct test → result → controlled change → validation → documentation

Frequently asked questions

What should I check first?

Start with the exact symptom and validate the dependency closest to the failure, such as DNS, a port, a service, storage or an authentication path.

Should I change production configuration immediately?

No. Capture the current state first, test the suspected dependency and make one controlled change at a time.

How should I document the fix?

Record the symptom, commands used, result, configuration change and validation result so the procedure can be repeated.

Related TechRunbook guides

Windows Server Low Disk Space: Troubleshooting and Cleanup Checklist →PowerShell Server Health Check: Practical Windows Server Script Guide →
Operational rule: Capture the original symptom, test one dependency at a time, and validate the fix using the same test that exposed the problem.

Need more infrastructure resources?

Browse free TechRunbook guides, checklists and scripts.

Browse free IT resources →