Database Management
SQL Sentry Portal 500 error
This article contains two separate error 500 messages. Please pay attention to which one relates to your case. Error 1: {"Message": "Object reference not set to an instance of an object. ", "StatusCode": 500, "StackTrace":""} Error 2: Error: API error: 500: Internal Server Error at fp.CreateAsync
First published date
7/1/2021 9:38 PM
Last published date
2/10/2025 4:45 AM
Overview
When attempting to connect to a newly installed version of SQL Sentry Portal users can at times run into an error message stating the following:
Error 1:
Error 1:
{"Message": "Object reference not set to an instance of an object. ", "StatusCode": 500, "StackTrace":""}
Error 2:
API error: 500: Internal Server Error Error: API error: 500: Internal Server Error at fp.CreateAsync (http://customerPortalURL:Port/main.c2c3c8404acfb2cdfb6f.js:2:4044713) at yg.get (http://customerPortalURL:Port/main.c2c3c8404acfb2cdfb6f.js:2:4183299) at async Wg (http://customerPortalURL:Port/main.c2c3c8404acfb2cdfb6f.js:2:4233304)
Product section
SQL Sentry (SQLS)
Cause
Error 1:
The issue is typically environmental because the domain name is not being translated into the appropriate IP address.
Error 2:
This looks to stem from an additional Portal Configuration Connection that isn't properly set up. In the offending example, the customer had two connections set up in Portal. One of them was blank with only a server name for the connection. Portal tried to load both connections when starting up and failed on this one.
The issue is typically environmental because the domain name is not being translated into the appropriate IP address.
Error 2:
This looks to stem from an additional Portal Configuration Connection that isn't properly set up. In the offending example, the customer had two connections set up in Portal. One of them was blank with only a server name for the connection. Portal tried to load both connections when starting up and failed on this one.
Resolution
Error 1:
First attempt to clear out any issues lingering issues due to old or corrupted connection information in the Portal Configuration Utility (PCU).
Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties, including, without limitation, any implied warranties of merchantability or fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.
You can do this by running the following command in PowerShell with your machine's server.domain.com filled into the command.
NSLookUp server.domain.com
For good measure, I might also try to do the following test in PowerShell with your machine's server.domain.com filled into the command.
Test-NetConnection -ComputerName server.domain.com -Port 9991
If all else fails, then the user can use the IP Address of the Portal Service Host to connect to the site. Once the connection is established, a simple URL redirect can be written to specify the user decided URL rather than IP Address. (Information on configuring this can be found in our help documentation. https://docs.sentryone.com/help/sentryone-portal-on-premises#iis-reverse-proxy-configuration-optional- )
Error 2:
The easiest way is to simply select the extra connection within the Portal Configuration Utility and press the Delete button. If that doesn't work for any reason, follow the steps from Error 1 regarding deleting the monitorportal.s1.config file and re-setting up the connection.
First attempt to clear out any issues lingering issues due to old or corrupted connection information in the Portal Configuration Utility (PCU).
- Log into the machine hosting Portal.
- If it is open, close the Monitoring Portal Configuration Utility.
- Delete the monitorportal.s1.config file in C:\ProgramData\SolarWindsSQL Sentry\monitorportalconfig.
- Launch the Monitoring Portal Configuration Utility.
- Add a new connection with the IP set to 0.0.0.0 and the Encrypt Network Traffic, Trust Server Certificate, and Multi Subnet unchecked.
- Click Verify & Save.
Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties, including, without limitation, any implied warranties of merchantability or fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.
You can do this by running the following command in PowerShell with your machine's server.domain.com filled into the command.
NSLookUp server.domain.com
For good measure, I might also try to do the following test in PowerShell with your machine's server.domain.com filled into the command.
Test-NetConnection -ComputerName server.domain.com -Port 9991
If all else fails, then the user can use the IP Address of the Portal Service Host to connect to the site. Once the connection is established, a simple URL redirect can be written to specify the user decided URL rather than IP Address. (Information on configuring this can be found in our help documentation. https://docs.sentryone.com/help/sentryone-portal-on-premises#iis-reverse-proxy-configuration-optional- )
Error 2:
The easiest way is to simply select the extra connection within the Portal Configuration Utility and press the Delete button. If that doesn't work for any reason, follow the steps from Error 1 regarding deleting the monitorportal.s1.config file and re-setting up the connection.