Outlook Error Codes

How to Fix Outlook Sign-In Error 1001 on RDSH Servers

Kushani NimanthikaKushani Nimanthika Oct 21, 2026 869 views

Question details

Users are experiencing sign-in error 1001 when accessing Microsoft Outlook on Remote Desktop Session Host (RDSH) servers and need a fix that avoids profile rebuilds.

How to Fix Outlook Sign-In Error 1001 on RDSH Servers
Product
Microsoft Outlook
Device & OS
Windows Server
Scenario
Users attempting to authenticate and sign in to Microsoft Outlook within an RDSH server environment.
Observed behavior
Outlook fails to sign in and returns error code 1001, often due to corrupted profile data, cached credentials, or network interference.
Before you start

Gather your current Outlook version details, identify the exact date the issue started, and verify if any recent system updates or network changes were applied to your servers.

Solution 1Recommended

Clear Cached Credentials and Authentication Tokens

Resolve error 1001 by clearing corrupted authentication tokens centrally, avoiding the need to fully recreate every user profile.

Because recreating the entire Outlook profile works, the root cause is often isolated to corrupted local credential caches or stale authentication tokens. Clearing these specific folders can resolve the error with much less administrative effort.

1
Log out the affected user

Ensure the user experiencing the error is completely logged out of their RDSH session.

2
Navigate to the Identity Cache

Open File Explorer as an administrator and navigate to the user's local AppData folder at %localappdata%\Microsoft\IdentityCache.

3
Delete cached files

Delete the contents of the IdentityCache folder. Next, navigate to %localappdata%\Microsoft\OneAuth and clear its contents as well.

4
Restart and test Outlook

Have the user log back into the RDSH server and launch Outlook. They should be prompted for a fresh authentication, resolving error 1001.

Clear Cached Credentials and Authentication Tokens
Automation Tip: For large RDSH environments, consider writing a logon script to centrally remediate these cache folders rather than fixing them manually per user.
Free Microsoft Office alternative

Try WPS Office for a Reliable and Lightweight Experience

If Microsoft Office errors are disrupting your server environment, consider switching to WPS Office. It provides a highly compatible, lightweight alternative for document processing without the heavy profile management overhead.

  1. 1. Download the Installer: Visit the official WPS website and download the free WPS Office installation package.
  2. 2. Install on your Server: Run the installer on your system and follow the quick setup wizard.
  3. 3. Open and Use: Launch WPS Office to immediately start creating and editing documents with full Microsoft format compatibility.
Free and lightweight Office suiteFully compatible with Microsoft Word, Excel, and PowerPoint formatsLower resource consumption on remote desktop environmentsFamiliar user interface for seamless migration
microsoft office alternative - wps office

Frequently Asked Questions

What causes Outlook Error 1001 on RDSH servers?

Error 1001 typically occurs due to network connectivity disruptions, corrupted Microsoft 365 authentication tokens, or misconfigured cached credentials within the user's roaming profile.

Do I have to recreate every user's Outlook profile to fix this?

No. While rebuilding the profile does resolve the issue, you can often fix it much faster by simply clearing the corrupted Microsoft Identity Cache and OneAuth folders for the affected user.

Can antivirus software cause Outlook sign-in errors?

Yes, overly strict antivirus or firewall settings can block communication with Microsoft 365 authentication endpoints, resulting in unexpected sign-in failures like error 1001.