Error 500 When Running METTEAM Reports
- Reports were not updated after upgrading MET/TEAM. Versions 2.2.0, 2.3.0 and 3.0.0 each had their own report update tool and depending on your starting and ending version, one or two of these tools must be run.
If you experience the error when running a report after upgrading MET/TEAM, ensure that you ran the appropriate Report Update Tools, which should be located on the MET/TEAM server's desktop.
NOTE if you started below version 2.2.0, the 2.2.0 report update tool must be run while you are on version 2.2.0. This is true regardless of the 'ending' version you stop at. Do NOT run either the 2.3.0 or 3.0.0 report update tools before the 2.2.0 tool because they will fail.
The 2.3.0 version of the report update tool is only needed if you are stopping at one of the 2.3.0 versions of MET/TEAM. If you are continuing to upgrade to version 3.0.0 or higher, then the 2.3.0 version of the report update tool can be skipped.
If your ending version is above 3.0.0, the 3.0.0 version of the report update tool must be used. Report Update Tool (V3.x) zip
- System Defaults not set in MET/TEAM
Follow the steps in the article Location of reports in MET/TEAM and Customer Portal to verify that the correct folder location is set for your reports in the METTEAM System Defaults. - Application Pool Advanced Settings show "Enable 32-Bit Application" set to True when using MET/TEAM versions 2.2.0 and below.
- NOTE: In MET/TEAM versions 2.2.1 we started using the 64-bit version of Crystal Reports.
- Application Pool Advanced Settings show "Enable 32-Bit Application" set to FALSE when using MET/TEAM versions newer than 2.2.0.
- Report folders do not have proper permissions
The account under which the website is running as defined in IIS for the MET/TEAM application pool, must have read/write/full control access to the reporting directory and its sub directories.
- The Connection String stored in the METTEAM website has a slash after the SQL instance name
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.
Good:
Bad:
- Crystal Reports Runtime is not properly installed
If your reports still fail to open and gives 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:
Open your MET/TEAM install media, and search the install media for the strings below, depending on version, and run the files in these folders:
MET/TEAM 2.2.1 ISO:
{1C779D9F-912E-44AE-8A96-085070E9B53E} and {70AA3A62-9421-49FD-B4FF-EB18A215784E}
MET/TEAM 2.3.0 ISO:
{2ee52e5b-7d14-410d-be16-2d807265f9e3} and {12dcc8db-98c0-4a0f-aa28-1df85f4198d5}
When finished, "restart" the websites and application pools in IIS.
- Ensure the correct connection object is installed on the server. This is dependent on your current version of MET/TEAM,
METTEAM 2.3.0 requires SQL Server Native Client 2012 (11.0) to make connections between the report engine on the METTEAM server and SQL server. If METTEAM is installed on a separate server from the SQL Server or you are using SQL Server 2008 R2, you will want to check to see if SQL Server 2012 Native Client is installed on the server hosting the MET/TEAM website.
In Programs and Features (Apps and Features in Windows 10 and Server 2016) on the METTEAM server, look to see if Microsoft SQL Server 2012 Native Client is installed.
If it is not, download it from Microsoft's website and install it onto the METTEAM application server.
NOTE: If TLS 1.2 enabled, SQL Server Native Client 2012 (11.0) version 11.4 or higher is required. If you do NOT have version 11.4 or higher, we recommend updating with the "Microsoft's website" link above.
METTEAM 3.0.0 and later requires Microsoft OLE DB Driver for SQL Server (also located in the share "\\{MET/TEAM server name here}\METTEAM\Installers\CrystalReportsSupport\msoledbsql.msi)
See "Your report's connection did not get updated " section below for more info.
- "Missing Parameter Values" Error 500
If the Error 500 page says "Missing Parameter Values" you will need to check and fix all of the listed parameters in the report and any sub-reports in that rpt. Don't forget to save the report after fixing the parameter.
- SQL Server Browser service is not running
If the MET/TEAM database is located on a SQL instance that is NOT on the same computer as the MET/TEAM website, then be sure the "SQL Server Browser" service is running on the SQL computer.
Blank Data
You recently upgraded to METTEAM 2.3.0 and now several reports show no data
If your report has a GUID parameter and does not show data even after running the Report Update Tool, it is likely that you need to update the selection formula as noted in the Report Update Tool Readme.
- In your report, go to Report-->Selection Formulas-->Record...
- Look for a UID parameter (denoted with a '?') in your selection formula (?nCallSheetUID, ?nAssetUID, etc). For example:
- The above example shows nCallSheetUID as a the parameter
- The UID parameter needs quoted brackets around it to make it:
"{" + {?nCallSheetUID} + "}" ={vw_CallSheetsWithAttCheck.nCallSheetUID} - Save a copy of the report and run it to test it out
- If you still get blank fields, go to Report-->Selection Formulas-->Groups and check for the same issue.
Your report's connection did not get updated to match your current version of MET/TEAM
It is possible that the connection for your report did not get updated. To check this refer to the article below:
How to set datasource location in a MET/TEAM report