As administrators of Sage CRM, we naturally focus on CRM configuration, metadata, and user setup. But many of the issues that affect CRM performance, login behaviour, or stability originate lower down, in the Windows Server environment.

This article highlights a set of simple, built in Windows utilities that can quickly resolve common issues affecting:

• General Windows behaviour
• Internet Information Services
• Connectivity to Microsoft SQL Server

These are safe, practical checks that every CRM system administrator should be comfortable running.

Important: Always Run Command Prompt as Administrator

When running any of the commands below:

1. Open the Start Menu
2. Search for cmd
3. Right click Command Prompt
4. Select Run as administrator

If you do not run the command window with elevated privileges, many checks will either fail silently or not execute correctly.

1. System File Checker

sfc /scannow

What it does

Scans and repairs corrupted Windows system files.

Why it matters

If core Windows components used by IIS, authentication, or networking become corrupted, you may see:

• IIS not starting
• CRM pages partially rendering
• Random login failures
• Unexpected server behaviour

How to use it

Open Command Prompt as Administrator and run:

sfc /scannow

If corruption is repaired, reboot the server.

2. DISM Component Repair

If SFC reports that it cannot fix some files, use:

DISM /Online /Cleanup-Image /RestoreHealth

This repairs the underlying Windows image.

After it completes, run sfc /scannow again.

This is particularly useful when Windows updates or servicing stack components have become inconsistent.

3. Restart IIS Cleanly

Because Sage CRM runs under IIS, application pool instability can cause:

• 500 errors
• Session drops
• Login issues
• Pages not loading correctly

Instead of rebooting the server you can do an iisreset or recycle only the Sage CRM application pool inside IIS Manager.

While many administrators use:

• iisreset

In practice, it is often better to separate the stop and start actions:

• iisreset /stop
  iisreset /start

This ensures that all IIS services are properly stopped before being restarted.

Experience shows that a single iisreset command can occasionally cause IIS and Tomcat processes to become tangled during restart. Separating the stop and start phases allows services to shut down cleanly before coming back online.

Important: This disconnects active users.

4. Check SQL Connectivity

If CRM cannot reach Microsoft SQL Server, users may experience login or application errors.

You can perform simple checks from the CRM server.

Test network connectivity
ping SQLSERVERNAME

Test SQL connection
sqlcmd -S SQLSERVERNAME\INSTANCENAME -U sa -P <password>

If SQL authentication or connectivity fails at this level, the issue is not CRM configuration.

If users encounter the well known:

“You may need to recreate views manually”

and you suspect a SQL login or connectivity issue, see these detailed articles on the Sage Community Hub:

 You may need to recreate view manually error
You may need to recreate views manually 

These explain why the message is usually a symptom of database access problems rather than an issue with views themselves.

5. Check Disk Health

Disk problems can affect:

• SQL write operations
• IIS log creation
• CRM document storage
• Overall server stability

Run:

chkdsk C: /f

You may need to reboot to complete repairs.

Also monitor:

• Free space on SQL data and log drives
• IIS log growth
• Temp directory usage
• Low disk space causes subtle and unpredictable failures.

6. Use Event Viewer as Your First Stop

Before making changes, always check:

• Windows Logs → Application
• Windows Logs → System

Look for:

• SQL login failures
• IIS worker process crashes
• .NET runtime errors
• Disk warnings
• Authentication failures

Very often the root cause is clearly recorded here.

A Sensible Health Routine for Sage CRM Servers

For production systems:

Weekly

• Check disk space
• Review Event Viewer
• Confirm SQL service is running

Monthly

• Review Windows updates
• Recycle IIS during maintenance
• Check SQL error logs
• During troubleshooting
• Test SQL connectivity first
• Review Event Viewer
• Restart affected services
• Run SFC and DISM if system corruption suspected

Final Thoughts

These are not advanced diagnostics or deep architectural interventions. They are simple, built in Windows tools that solve a surprising number of real world issues.

Over many years of working with Sage CRM systems in customer environments, I have found that many reported “CRM problems” are in fact:

• Windows health issues

• IIS instability

• SQL connectivity quirks

• Disk or service related interruptions

A calm, methodical use of these utilities often resolves issues quickly and avoids unnecessary configuration changes or reinstallation work.

I hope these tips and tricks prove useful in your own environments. They are not theoretical recommendations, but practical lessons learned from experience supporting Sage CRM systems in production.

If you have additional server health checks that have helped you stabilise a CRM installation, please share them on the Sage Community Hub so we can continue learning from one another.