Configuration Check (REDCap 15.1.0)
This page will test your current REDCap configuration to determine if any errors exist that might prevent it from functioning properly.
Basic tests
TEST 1: Establish basic REDCap file structure
Search for necessary files and folders that should be located in the main REDCap folder (i.e. "C:\inetpub\wwwroot\redcap").
SUCCESSFUL! - All necessary files and folders were found.
Search for necessary files and folders that should be located in the main REDCap folder (i.e. "C:\inetpub\wwwroot\redcap").

TEST 2: Connect to the table named "redcap_config"
SUCCESSFUL! - The table "redcap_config" in the MySQL database named redcap_db
was accessed successfully.

TEST 3: Check REDCap database table structure
SUCCESSFUL! - Your REDCap database structure is correct!

TEST 4: Check if PHP cURL extension is installed
SUCCESSFUL! - The cURL extension is installed.

TEST 5: Checking communication with REDCap Consortium server (https://redcap.vumc.org/consortium/)
(used to report weekly site stats and connect to Shared Library)
Communicating with server... please wait
(used to report weekly site stats and connect to Shared Library)

TEST 6: Check if REDCap Cron Job is running
ERROR: Cron job not running!
It appears that your REDCap cron job has either not been set up or is not running at the proper interval. Please see the Cron Jobs page in the Control Center for details on setting it up. This cron job is very important and must be running on a regular basis at the prescribed interval in order for certain background tasks to be performed correctly.
Go to Cron Jobs page

It appears that your REDCap cron job has either not been set up or is not running at the proper interval. Please see the Cron Jobs page in the Control Center for details on setting it up. This cron job is very important and must be running on a regular basis at the prescribed interval in order for certain background tasks to be performed correctly.
Go to Cron Jobs page
Secondary tests








128M
(i.e., 128 MB) or higher, preferably to the maximum value of 1G
(i.e., 1 GB). Setting it to the max value of 1G will not have any negative side effects. To change this setting, open your my.cnf (or my.ini) configuration file for MySQL and modify the line for max_allowed_packet to set it as the following: max_allowed_packet=1G
. Then restart MySQL, and then reload this page.


Your database configuration settings do not appear to be optimal. For better database performance and stability, consider making the changes below to your database configuration settings in your
my.cnf
(Linux/Unix) or my.ini
(Windows) configuration file. TIP: Remember to restart the MySQL service after making any edits to the configuration, otherwise they won't take effect.Recommendations for the REDCap database server:
- tmp_table_size (current value=526385152) and max_heap_table_size (current value=16777216) are not the same. They should be set to the same value.
- Too many sorts are causing temporary tables. Consider increasing sort_buffer_size and/or read_rnd_buffer_size.

Location: C:\Windows\TEMP

Location: C:\inetpub\wwwroot\redcap\temp\

Location: C:\inetpub\wwwroot\redcap\edocs\

It is HIGHLY recommended that you change your location where user-uploaded files are stored. Currently, they are being stored in REDCap's "edocs" directory, which is the default location and is completely accessible to the web. Although it is extremely unlikely that anyone could successfully retrieve a file from that location on the server via the web, it is still a potential security risk, especially if the documents contain sensitive information.
It is recommend that you go to the File Upload Settings page in the Control Center and set a new path for your user-uploaded documents (i.e. "Enable alternate internal storage of uploaded files rather than default 'edocs' folder"), and set it to a path on your web server that is NOT accessible from the web. Once you have changed that value, go to the 'edocs' directory and copy all existing files in that folder to the new location you just set.

Location: C:\inetpub\wwwroot\redcap\modules\
Internal Service Check: Checking communication with the REDCap survey end-point
Communicating with server... please wait

External Service Check: Checking communication with Twilio telephony API services
Communicating with server... please wait

External Service Check: Checking communication with Mosio SMS API services
Communicating with server... please wait

External Service Check: Checking communication with SendGrid email API services
Communicating with server... please wait

External Service Check: Checking communication with PROMIS assessment API services
Communicating with server... please wait

External Service Check: Checking communication with REDCAP.LINK URL shortening API services
Communicating with server... please wait

External Service Check: Checking communication with Field Bank NLM services
Communicating with server... please wait

Security improvement - SUGGESTION:It appears that you are running REDCap over SSL/HTTPS (which you *should* if this is a production server). For better security, it is recommended that you enable the session.cookie_secure option in your web server's PHP.INI file. To enable "session.cookie_secure option", simply open your web server's PHP.INI file for editing and change the value of "session.cookie_secure" option to "On", or if it does not exist yet, add the following line in the
Then reboot your web server. Doing this is not required, but it is recommended since it improves the overall security of the REDCap system.
[Session]
section of PHP.INI:session.cookie_secure = On
Then reboot your web server. Doing this is not required, but it is recommended since it improves the overall security of the REDCap system.
(Optional) If clustering or replication is implemented on your database server, in which it might be required that every database table
has an auto-incremented Primary Key, you may execute the SQL in the box below to add Primary Keys to all REDCap database tables.
Please keep in mind that these queries might take minutes or possibly hours to execute depending on the size of your database.
Note: We do not recommend running the SQL below unless you think you truly need it.