To Be A CyberMan: The 0365 email/ADFS Troubleshooting - Http status 500 error
To Be A CyberMan: The O365 email/ADFS
Troubleshooting - Http status 500 error
0x00: Preview Knowlege
ADFS: Active Directory Federation Services (ADFS)
is a Microsoft Single Sign-On (SSO) solution. It provides users with
authenticated access to applications that are not capable of using Integrated
Windows Authentication (IWA) through Active Directory (AD).

Reference:
https://docs.microsoft.com/en-us/windows-server/identity/active-directory-federation-services
0x01: Symptoms
Some users reported they were not able to log into the
email from Web console, the error shows: HTTP status 500:internal server error

0x02: Troubleshooting
- We tested some accounts email, The issue only affected some of the user's web-based Outlook applications. So we sent the email to our outlook service provider, got confirmation that the outlook service is working.
- From the error message, we can see the error
is the internal server, for the O365 outlook, we are using an internal
ADFS authentication server. So we checked the adfs proxy/adfs servers.
- We checked the ADFS log Events, found some errors.

- The ADFS service was stopped. Restarting it just
gave errors as below:
Error 352, ADFS
A SQL operation in the AD FS
configuration database with connection string Data
Source=np:\\.\pipe\microsoft##wid\tsql\query;Initial
Catalog=AdfsConfigurationV3;Integrated Security=True failed.
- According to the error, we did some research,
found the resolution.
Reference:
https://sysandev.blogspot.com/2019/04/a-sql-operation-in-ad-fs-configuration.html
https://ninjanichols.com/2013/02/ad-fs-2-0-service-fails-to-start/
0x03: Resolution
- restart “Windows Internal Database” service.
- restart the “AD FS 2.0 Windows Service”.

0x04: More information
- Can check the ADFS token signing certificates on the office365 side, make sure it is not expired. Some times it will only update on the ADFS side and failed to get to Office365.
- Check the Event Logs on ADFS Server to get more error
information.
- Can try this one as well:
- Open PowerShell as an Administrator
on the primary ADFS server
- run Connect-Msolservice and connect using an Azure
administrator account
- run Update-MsolFederatedDomain –DomainName xxxx.com
- restart ADFS service
To Be A CyberMan: The O365 email/ADFS Troubleshooting - Http status 500 error
0x00: Preview Knowlege
ADFS: Active Directory Federation Services (ADFS) is a Microsoft Single Sign-On (SSO) solution. It provides users with authenticated access to applications that are not capable of using Integrated Windows Authentication (IWA) through Active Directory (AD).
Reference:
https://docs.microsoft.com/en-us/windows-server/identity/active-directory-federation-services
0x01: Symptoms
Some users reported they were not able to log into the email from Web console, the error shows: HTTP status 500:internal server error
0x02: Troubleshooting
- We tested some accounts email, The issue only affected some of the user's web-based Outlook applications. So we sent the email to our outlook service provider, got confirmation that the outlook service is working.
- From the error message, we can see the error is the internal server, for the O365 outlook, we are using an internal ADFS authentication server. So we checked the adfs proxy/adfs servers.
- We checked the ADFS log Events, found some errors.
- The ADFS service was stopped. Restarting it just gave errors as below:
Error 352, ADFS
A SQL operation in the AD FS configuration database with connection string Data Source=np:\\.\pipe\microsoft##wid\tsql\query;Initial Catalog=AdfsConfigurationV3;Integrated Security=True failed.
- According to the error, we did some research, found the resolution.
Reference:
https://sysandev.blogspot.com/2019/04/a-sql-operation-in-ad-fs-configuration.html
https://ninjanichols.com/2013/02/ad-fs-2-0-service-fails-to-start/
0x03: Resolution
- restart “Windows Internal Database” service.
- restart the “AD FS 2.0 Windows Service”.
0x04: More information
- Can check the ADFS token signing certificates on the office365 side, make sure it is not expired. Some times it will only update on the ADFS side and failed to get to Office365.
- Check the Event Logs on ADFS Server to get more error information.
- Can try this one as well:
- Open PowerShell as an Administrator on the primary ADFS server
- run Connect-Msolservice and connect using an Azure administrator account
- run Update-MsolFederatedDomain –DomainName xxxx.com
- restart ADFS service
Comments
Post a Comment