Generate Support Data

If you are working with Globalscape Technical Support on a specific issue with EFT, you can generate a report of key EFT and system data to send to Globalscape Support. Before sending, be sure to view and, if needed, edit the report.

If the EFT computer does not have Internet access, you can still generate the support data file, and then copy the file onto another computer from which you can upload it to Support's technical portal. If EFT detects that DMZ Gateway is present, it will attempt to use the DMZ Gateway; otherwise, EFT attempts direct connection. You cannot upload the Support data via DMZ Gateway's HTTP proxy.

You can install the EFT administration interface on another computer that has Internet access, from which you can view and manage EFT, provided that computer can access the EFT computer remotely.

The Generate Support Data wizard automates the process of gathering key EFT and system configuration information to assist with support cases.

To generate support data

  1. On the main menu, click Help > Generate support data. The Generate Support Data wizard appears.

  2. Click View/Edit. The file names all of the files and data that will be gathered, including file paths, registry keys, event log items, etc. will appear in an XML file. The file opens in your default TXT reader, such as Notepad.

    3. The following data will be collected by default:

    • Gathers all of the EFT SQLite DB files.

    • Generates system info

    • Gathers Windows application and system event logs (but ONLY for EFT application)

    • HKLM registry backup

    • Complete list of installed software

    • EFT log files (going back 1 day, by default)

    • FTP.cfg, .aud, and .bak files, if present

  3. This file also determines the number of days to collect data. By default, only 1 day of data is collected. You can edit the file to change the value. For example, to gather more than 1 day's worth of log files, in the text file that youe generated, edit the following line:

    4. //Collect EFT logs for the last 1 day. Change the number to collect more logs

    "logDays": 1,

    And change the value (1) to the number of days data to gather. Be aware that the larger the number, the longer it will take to generate the ZIP file.

  4. In Output path, specify the default path in which to save the generated dataset. The default is [root drive]:\EFT_[ComputerName].zip

  5. Click privacy policy to open and read the Globalscape Privacy Policy and then select the I've read and consent to Globalscape's privacy policy check box.  

  6. Click Generate. (Generate is disabled until privacy consent check box is selected.)

  7. The Status area displays data collection in progress. For example:

    8. Starting collection process...

    Collecting data...this may take a few minutes

    Error in parsing manifest file (missing, corrupted?) <-if error, sample

    Error due to timeout (600 seconds). Files locked or unavailable? <-if error, sample

    Done

  8. Click Next.

  9. If you were asked to submit the generated file to Support, then provide the case number and the password you were given from Support in the Case and Pass boxes.

    • If EFT does not have Internet access, you can generate the support data file, copy the file onto another computer that does have Internet access, then upload it as requested by Support.

  10. Submit is disabled until the Case and Pass boxes are filled. Click Submit to send the data.

    11. If EFT detects that DMZ Gateway is present, it will attempt to use the DMZ Gateway; otherwise, EFT attempts direct connection.

  11. A message appears whether connection succeeded or failed. Click Finish or click Back to try again.

Rest endpoints are also available:

  • GET - returns the default template

  • GET - returns the bundle generation status

  • DELETE - cancels the bundle generation

  • POST - Generates telemetry bundle with the specified template

  • GET - Returns the list of telemetry bundles

  • GET - returns the telemetry bundle

  • DELETE - Deletes the telemetry bundle

  • /server/telemetry/template

  • /server/telemetry/status/{telemetryBundleName}

  • /server/telemetry/bundles

  • /server/telemetry/bundles/{telemetryBundleName}