Chrome download warning

Chrome may flag the ReportForge installer as a suspicious download. This happens because ReportForge is a new application that has not yet built download reputation with Google Safe Browsing.

1
Click the arrow on the download bar at the bottom of Chrome.
2
Choose Keep to save the file.

This warning will disappear as more users download the application without reporting issues.


SmartScreen warning

Expected behavior

This is expected behavior — ReportForge is a new application and has not yet built reputation with Windows SmartScreen. It does not indicate a security risk.

1
When you see Windows protected your PC, click More info.
2
Click Run anyway.
3
The installer proceeds normally. This warning only appears on the first run.

Template errors

No placeholders found

Your template needs at least one {{placeholder}} marker in a cell. Check that you used double curly braces and that there are no extra spaces inside the braces.

Invalid file format

ReportForge only supports .xlsx files. If your file is .xls (legacy format), open it in Excel and save as .xlsx (File → Save As → Excel Workbook).

Password-protected file

Remove the password in Excel: File → Info → Protect Workbook → Encrypt with Password → clear the password field → save the file. Then re-import.

Template file is too large

Templates are limited to 50 MB. Remove unused sheets or embedded images to reduce the file size.


Data source errors

Garbled or unreadable characters

The file encoding may not be UTF-8. Re-export from your application with UTF-8 encoding, or open in a text editor and save as UTF-8.

No data rows found

The file has column headers but no data below them. Ensure your CSV contains at least one data row.

Could not detect delimiter

The file may not be a valid CSV. Open it in a text editor to verify it uses commas, semicolons, or tabs as separators.

Column no longer exists

A mapped column was renamed or removed from the CSV. Re-import the data source or update the mapping to use the correct column name.


Generation errors

File is in use

Close the template or data source file in Excel or any other application, then try again.

Cannot write to output folder

Check that you have write permissions to the output folder. You can change the output folder in Settings (Ctrl+,).

Not enough disk space

Free up space on your drive and try again.

PDF creation failed

The Excel report was generated successfully, but PDF conversion failed. The .xlsx file is available in the output folder. Try generating again without PDF, or check the logs for details.


Scheduling issues

Schedule not triggering

ReportForge must be running (including in the system tray) for schedules to execute. Check:

  • Is the app open or minimized to tray?
  • Is the schedule enabled?
  • Is the correct time/day configured?

Folder watch not detecting files

Verify the watched folder path still exists. Check that you have read permissions to the folder. New files must be fully written before ReportForge picks them up — if a file is still being copied, it may not be detected immediately.


Application issues

App does not start

Try deleting the log files at %AppData%\ReportForge\Logs and restarting. If the issue persists, try reinstalling ReportForge — your data is preserved in %AppData%\ReportForge.

Database locked

Another instance of ReportForge may be running. Check the system tray for the ReportForge icon and close any extra instances.

Database appears corrupted

ReportForge creates automatic backups. When prompted, select a backup to restore from. Some recent changes may be lost, but your template and data source files are preserved separately.


Logs and diagnostics

ReportForge stores log files at: %AppData%\ReportForge\Logs

Logs are rotated daily and kept for 30 days. When contacting support, include:

  • A description of the issue
  • The steps to reproduce it
  • The most recent log file

Database backups are stored at %AppData%\ReportForge\Backups.


Contact support

For issues not covered here, email support@boringworx.com. We respond within 24 hours on business days. Include:

  • What you were trying to do
  • What happened instead
  • The relevant log file if possible