"Invalid byte 1 of 1" error when opening the backup client - SAFE Backup

"Invalid byte 1 of 1" error when opening the backup client - SAFE Backup

Guide for the steps to take if, when opening the backup client, you get a message that says "Invalid byte 1 of 1-byte UTF-8 sequence".



This is caused by corruption in the .acb or .obm folder.

Open file explorer and navigate to the .acb (single user) or .obm (business user) folder in the C drive. This will be in C drive, Users, then the user folder the account runs on.



You now want to move the .acb or .obm folder out of this location - cut and paste into the desktop will be sufficient for this step. 

Now log back into the backup client, it will now open as usual. Please also give the backup service a restart, a guide for that can be found here.

The .acb or .obm folder will have recreated itself in the user folder so please feel free to delete the old one.



    • Related Articles

    • Can't login to Backup Server! - SAFE Backup

      If you try to login to the Backup Client and get this error message: Can’t connect to Backup Server! (java.net.ConnectException: Connection timed out: connect) It my be a network issue client side (for example if they have changed their DNS) please ...

    • How to Fix a Simple Mode Error with SQL Backup - SAFE Backup

      If you are backing up SQL databases and transaction logs at the same times, you may see the following error: "[Microsoft][ODBC SQL Server Driver][SQL Server]The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP ...

    • Error: failed to initialize RemoteBDB.Cloud - SAFE Backup

      You may receive an error on your backup report for the following, or similar: Failed to initialize RemoteBDB.Cloud. Error=[BlockDBConfig.readConfig] unknown default path for creating new journal file config: 0 , caused by [RuntimeException] ...

    • Invalid volume, Shadow Copy creation is assumed - SAFE Backup

      If you get this warning within your backup set: "Invalid volume G:\ (Shadow Copy creation is assumed)" (could be a different drive letter) please follow these steps to fix. First make sure you are on our most current client so post 8.3.0.30 Go to ...

    • View the debug.log files – SAFE Backup

      You will only really need to view this in the case of a missed backup, as this log will tell you when the next backup will run. To view the scheduler log, open file explorer and go to the C drive, open Users and select the user account that the ...