Precision, Performance, Confidence. ™

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, the instructions in "NT AUTHORITY\SYSTEM Account does not have sysadmin rights in SQL Server" below apply.  
      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".

    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 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.

  3. Application Pool for MET/TEAM in IIS not started

  4. Reports not updated after moving to MET/TEAM version 2.2

    If you experience the error when running a report after upgrading to MET/TEAM version 2.2, ensure that you ran the Report Update Tool, located on the MET/TEAM server desktop.

  5. Application Pool Advanced Settings show "Enable 32-Bit Application" set to True when using MET/TEAM version 2.2

    MET/TEAM Version 2.2 is limited to the 64-bit version of Crystal Reports, so this must be set to False.

  6. Identity of Application Pool in IIS is not LocalSystem

    Check this setting. If it is not LocalSystem, contact Fluke Technical Support.

  7. Another possible cause of Error 500 if you are able to log into MET/TEAM but the find screens show incorrect data and the 'detail' pages fail to load with a 500 error, look at this article:
    Mismatched Find Results and resulting display error
  8. If you get a 500 error when opening a report, first check that the report folders (C:\inetpub\wwwroot\METTEAM\Reporting\System and C:\inetpub\wwwroot\METTEAM\Reporting\Reports by default) are: a) Shared b) that the Users had full control of read/write access. 
  9. If your report is still giving a 500 error on opening the report from the MET/TEAM interface, check that the Connection string stored on the METTEAM website in IIS does not have a slash after the server name within the string. 
  10. If your reports still fail to open and give a 500 error, you might need to re-run the Crystal Reports installer. In this scenario, you will see this error page if you edited your Web.config file for verbose error pages: CR_Runtime.JPG Search for your MET/TEAM install media, and search the install media for this string: {1C779D9F-912E-44AE-8A96-085070E9B53E} and {70AA3A62-9421-49FD-B4FF-EB18A215784E} and run those files. Then "restart" the websites and pools in IIS. 
  11. If your error screen says: "Could not load file or assembly 'System.Web.WebPages.Razor, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies"You will need to download and install this package from Microsoft: Razor_Assembly.JPG



Have more questions? Submit a request


Please sign in to leave a comment.