Contact Us

Author name: Managecast Technologies

Linux, Veeam

Veeam Backup and Replication Linux VM “Failed to check fingerprint” Error

/

If you’ve recently upgraded to Veeam Backup & Replication 12.1 and have begun seeing your Linux jobs fail with the “Failed to check fingerprint” error, there is no need to worry! This issue is easily resolved with a few clicks. The cause of the error comes from the change to the format used by Veeam to store the Linux SSH fingerprints. If the config database is stored in an SQL 2019 or 2022 instance, the conversion process fails to process blank current_fingerprint values and sets them to NULL, causing the error in Veeam. To resolve the issue, you must manually validate each fingerprint for each machine: If these changes have not resolved the Failed to check fingerprint error, or have any other backup questions, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Invalid Serialized Stream, Unknown Opcode Found:4 error

/

A recent Microsoft change to the Serialized Property of Exchanges items have caused “Invalid ‘serialized stream, unknown opcode found: 4’” errors across Veeam for Microsoft 365 users. This issue has been resolved with new hotfixes for users on versions 7.0.0.4551 and 7.1.0.1401. Below are the KB links to download the hotfix that pertains to your environment: Hotfix for 7.0.0.4551 P20231218 Hotfix for 7.1.0.1401 P20231218 To install the hotfix, follow these quick steps: If you continue to experience the error, would like assistance with the hotfix, or have any other backup replated questions, please reach out to Support@Managecast.com.

Veeam

Veeam How to Manually Updating Suspicious File List in Limited Network Environment

/

It isn’t uncommon to come across an environment that has limited to no access to the internet. This can be for many reasons such as security or regulations. In these instances, your Veeam console won’t have the ability to reach out to the Veeam database to update the SuspiciousFiles.xml, which logs known malware extensions. Here areas steps to download and update the xml file manually: Additional Veeam information can be found in KB4514. If you have any questions or would like any assistance, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 What’s unsupported after the deprecation of basic authentication?

/

After Microsoft’s decision to deprecate basic authentication in favor of modern authentication, there are a few things that will change when switching from basic to modern. Below are items that are not supported through modern app-only authentication, and support that has been added in newer releases: Further information on what is/is not supported when switching to modern authentication can be found here KB3146. If you would like assistance, or have any further questions on what is supported, please email Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “objects types are unsupported in the modern app-only authentication mode”

/

After Microsoft’s deprecation of basic authentication, item’s that were excluded that aren’t supported in modern app-only authentication mode will raise a warning. The warning will specify, “Found # excluded objects. Some of the objects specified for exclusion will be ignored during processing because such objects types are unsupported in the modern app-only authentication mode.” If you are unsure what is no logner supported, you can check HERE. To resolve this warning: If you continue to experience issues with your M365 job, or any Veeam issue, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 “Download request retry timeout exceeded” error

/

Recently we have begun seeing the “Failed to backup item: FILEPATH, Download request retry timeout exceeded” error appear in jobs backing up OneDrive. Recent changes on the Microsoft side have begun preventing OneNote notebooks from being able to be downloaded. This prevents Veeam from being able to request and download the file to backup. We have an active case open with Veeam while they work with Microsoft to resolve this issue. We will update this post once Veeam and Microsoft have provided a public workaround or hotfix. Information on the issue can also be found here in KB4529. For additional assistance, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Microsoft 365 XML document and Specific SharingMessage type not recognised errors

/

During early December we began noticing two errors pop up. The messages “There is an error in XML document” and “The specific type was not recognized: name: ‘SharingMessage’” were caused by a minor Microsoft change. The changes were to the structure of the XML message received from M365 referencing the SharingMessageType property received from EWS. This change to the structure was unable to be processed by Veeam when the change occurred. However, Veeam has already pushed out patches to resolve the issue. Here are the two patches provided by Veeam: Veeam Backup for Microsoft 365 7.0 Cumulative Patch 7.0.0.4551 (P20231218) Veeam Backup for Microsoft 365 7a Cumulative Patch 7.1.0.1401 P20231218. Any newer version downloaded and installed will have the patch included. If you continue to run into any issues, have any questions, or need any other assistance, please reach out to Support@Managecast.com

Replication, Veeam

Veeam Replication Latest Available Restore Point is Already Replicated

/

The replication warning “Latest available restore point is already replicated” appears when the replication job that’s sourced from a backup/backup copy attempts to run, but there is no new restore point to grab new data from. Here are a few reasons that may cause new data not to be available to replicate: These are some of the most common reasons we find that cause the “already replicated’ warning to occur. Veeam, replication, and virtualization are complex, so there are many reasons this may occur. If you are still seeing the warning pop up, please reach out to Support@Managecast.com for further assistance.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Item has been changed during the backup warning

/

The warning “Item has been changed during the backup” occurs when a file is in use during a Veeam Backup for Microsoft 365 backup, Veeam will skip the file and try to backup it up during the next run. Here are a few tips to help get your file backing up. These are common steps we follow to help get items backing up after the warning has occurred. If your issues continue to occur, or would like assistance for any other issues, please reach out for assistance at Support@Managecast.com.

Veeam

Veeam Backup & Replication v10 and Newer Windows backup proxy is missing C++ runtime components error

/

Veeam will display the error message “Backup proxy is missing C++ runtime components” for a different reason depending if you are on a current supported version, or an older unsupported version. If you are still running an unsupported version of Veeam (9.5 and older) please see THIS blog post for steps to resolve the C++ issue. For newer versions of Veeam, this issue is caused when the VDDK libraries on the VMware Backup Proxy fail to load. This occurs when the Veeam Transport Service is missing components on the backup proxy. Repairing the Veeam Backup Transport should resolve the error. Before taking the following steps, please ensure no jobs are running. Once the install has finished, you may re-enable your jobs, and retry any job that was reporting the error. This is the most common reason we see the C++ runtime component occurring but may not resolve every C++ error. If you are continuing to experience issues, please contact Support@Managecast.com for further assistance.

Scroll to Top