Skip to main content

Resolve online backup batch file encoding errors

Learn how to fix online backups that fail when the backup batch file is saved with the wrong encoding and cannot read the required Progress path settings.

H
Written by Huzayfah Patel

📌 Note: Use these steps if a manual test of the online backup batch file shows an error similar to the example below.

C:\Windows\system32>´╗┐set DLC=c:\progress\OpenEdge12x64
'´╗┐set' is not recognized as an internal or external command.

Identify the Cause of the Backup Failure

If you see the error shown above during a manual test of the online backup batch file, the path settings for probkup.bat are not being read correctly.

The required lines should appear as plain text in the batch file:

set DLC=c:\progress\OpenEdge12x64
set PATH=%DLC%\BIN;%PATH%
set LIB=%DLC%\LIB;%LIB%

These lines set the path needed for probkup.bat.

If the file has been saved using UTF-8 encoding, special characters may be introduced at the start of the file. This prevents the batch file from reading the commands correctly and stops it from calling or recognising probkup.bat for the databases.

Save the Batch File Using ANSI Encoding

  1. Find the online backup .bat file.

  2. Right-click the file, then open it in Notepad using Edit.

  3. Click File, then click Save As.

  4. In the Save as type list, select All Files.

  5. Enter the file name with the .bat extension, for example progressonlinebackup.bat.

  6. In the Encoding dropdown, change the value from UTF-8 to ANSI.

  7. Save the file.

Test the New Batch File

  1. Run the new .bat file manually.

  2. Confirm that the path settings now read correctly and that the batch file can recognise probkup.bat.

  3. Check that the backup process now runs as expected.

Update Task Scheduler

  1. Open Task Scheduler.

  2. Find the scheduled task used for the online backup.

  3. Check that the task is pointing to the new progressonlinebackup.bat file.

  4. Save the task if you make any changes.

💡 Best Practices

  • Save backup batch files as ANSI if they contain standard batch commands that must be read as plain text.

  • Test the updated .bat file manually before relying on the scheduled task.

  • Confirm that Task Scheduler points to the correct replacement file after you save the new version.

Did this answer your question?