After doing a fresh install or upgrade to NFA 25.4.4 - 25.4.8, you may run into an issue where the website doesn't launch and you see, "Too Many Redirects 302 Error's" in your browser.
The Event Logs (Application) will show an error like the below:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 6/7/2026 5:21:03 PM
Event time (UTC): 6/7/2026 9:21:03 PM
Event ID: 5fb86b6ca3214decbde3c89ee2498b8d
Event sequence: 139
Event occurrence: 66
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RA-1-00000000000
Trust level: Full
Application Virtual Path: /RA
Application Path: D:\NetQoS\Reporter\NetQoS.ReporterAnalyzer.WebSite\
Machine name: <nfaservername>
Process information:
Process ID: 5968
Process name: w3wp.exe
Account name: IIS APPPOOL\ReporterAnalyzerWebSite
Exception information:
Exception type: Win32Exception
Exception message: The message received was unexpected or badly formatted
Request information:
Request URL: https://<nfaservername>:443/ra/ErrorInfo.aspx
Request path: /ra/ErrorInfo.aspx
User host address: x.x.x.x
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\ReporterAnalyzerWebSite
Thread information:
Thread ID: 7
Thread account name: IIS APPPOOL\ReporterAnalyzerWebSite
Is impersonating: False
Stack trace:
NFA 25.4.4 - 25.4.8
Windows Server
Due to a change implemented in the .NET Connector in recent versions, if an NFA Console is installed on a server with a lot of security protocols enabled, this crash may occur.
If the application event logs on your Windows Server, match the exception message, The message received was unexpected or badly formatted, then proceed to install the attached patch. The patch is for NFA 25.4.4. and 25.4.8 only. If you see these symptoms and you are on another version of NFA, please open a support ticket.
If you are on NFA 25.4.4 or 25.4.8, the patch will be attached below. This fix will be included in NFA 25.4.9.
If the error message above is not present, yet you are still seeing 302 error while trying to load NFA. You can try to to the servers IIS (Internet Information Services) web server application and expand out the left hand side pane and go to advanced settings for the ReporterAnalyzerWebSite and set Local User Profile to true and recycle the application pool.