Common Causes of Error 500 in MET/TEAM

Error 500 in MET/TEAM is a generic error message for a variety of connection and configuration issues. More specific error messages can be obtained to ascertain the cause, but first try these top causes of the error. If none of these settings resolve your error, contact Fluke Technical Support.

1. The account used to authenticate between the MET/TEAM website and the METTEAM database does not have sufficient rights.
   First we need to use IIS to determine what account is authenticating:
   
   The value listed for #5 above is the 'account' used to authenticate into SQL.   
    
   1. If the value listed for #5 is like the example above, the "LocalSystem" account for the computer hosting the MET/TEAM database is being used, then the instructions in "NT AUTHORITY\SYSTEM Account does not have sysadmin rights in SQL Server", step 3 below applies.  
      NOTE:  If the MET/TEAM website is hosted on a different computer than than the SQL instance, the 'user' in the steps below will be the [DOMAIN]\[MACHINE_NAME]$ as shown here:  
       
   2. If the value listed in #5 above is NOT "LocalSystem" it is most likely a "Service Account" and that service account needs to be setup in the SQL instance as a 'Login' with "User Mapping" to the 'metteam' database with the "db_owner" role.  Even better is if the "Service Account" can be configured with the "Server Role" of "sysadmin".
      NOTE:  If "LocalSystem" works but the service account results in error 500 then follow these steps:
      Open IIS
      Click on the METTEAM website in tree on left
      In the middle pane, double icon click to edit "Authentication"
      Right click on "Anonymous Authentication" and select "Edit..."
      Select the option to use "Application pool identity" instead of "Specific user" which is set to "IUSR".
      Click OK
      Restart the METTEAM application pool and website and retest, all should be good.
      Same steps can be followed for Customer Portal.
      
       
   3. NT AUTHORITY\SYSTEM Account does not have sysadmin rights in SQL Server
      
      This is the single most common cause of Error 500 when launching MET/TEAM.  
      
      Open SQL Server Management Studio to verify this setting:
      
      
2. SQL Server instance not set up to allow remote connections
   
   This can be checked from SQL Server Management Studio (SSMS) as well.  Right-click on the instance name and select "properties".  Next, click on "Connections" and make sure the check box "Allow remote connections to this server" is checked.
    
3. SQL Server service not running after server reboot
   
   This is especially common when your network has strict IT requirements that cause slow computer bootup times.
   
   Ensure that your SQL Server service shows "Running" in the Status Column. Click "Start" on the left hand side to start it if needed.
   
   
    
4. Application Pool for MET/TEAM in IIS not started
   
   
    
5. Identity of Application Pool in IIS is not LocalSystem
   
   Check this setting. If it is not LocalSystem, refer to step 1.2 above or contact Fluke Technical Support (SoftwareSupport@Flukecal.com) if assistance is needed.
   
   
    
6. Receive Error 500 after using Find pages
   
   Another possible cause of Error 500 can be if you are able to log into MET/TEAM but the find screens show incorrect data and when selecting a record, the 'detail' pages fail to load with a 500 error, look at this article:
   Mismatched Find Results and resulting display error
    
7. You see the error:  "The certificate chain was issued by an authority that is not trusted" due to enhanced encryption being used between MET/TEAM's website and the SQL database
   
   If the newest MET/TEAM log file (typically located in C:\inetpub\wwwroot\METTEAM\Logs\) or your error screen has: "The certificate chain was issued by an authority that is not trusted", there is an issue with the MET/TEAM connection string because it doesn't explicitly specify a value for encryption property.  Refer to this Microsoft article:    "The certificate chain was issued by an authority that is not trusted" error after upgrading SNAC applications 
   The article above references this article which explains more options:  DSN and Connection String Keywords and Attributes 
   
   We have seen that adding the following to your existing connection string resolves the issue:
        ;TrustServerCertificate=true
   
   However, it is best to review the articles above and configure as to best meet your needs and policies.
   
    
8. You see the error:  "Could not load file or assembly 'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies"
   
   If the newest MET/TEAM log file (typically located in C:\inetpub\wwwroot\METTEAM\Logs\) or your error screen has: "Could not load file or assembly 'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies", you will need to download and install this package from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=34600 
   
   
9. After upgrading to METTEAM 3.1.0 or newer while using HTTPS
   
   Refer to the article METTEAM 3.1.0 Upgrade Issue With HTTPS