Contact Us

Error

Office 365 Backup, Veeam

Veeam for Microsoft 365 Not allowed to access Non IPM folder Error

/

Microsoft constantly pushes out changes, and sometimes these changes break things for 3rd party vendors. After a recent change, we had started seeing the error message “Failed to get folder properties. Not allowed to access Non IPM folder” across several backups. The Microsoft change to the properties of the TeamsMessagesData folder caused Veeam to be unable to retrieve the data over the EWS APIs. Luckily, the fix for this a quick and easy! Note: This requires you to be on Veeam for Microsoft 365 6.1.0.1015 or Newer. Implementing the change on prior versions will NOT resolve the issue. We recommend upgrading to a supported version before applying the following fix. Recent Veeam for Microsoft 365 releases cover this issue. Please follow these steps: If you continue to experience issues or would like assistance with any other issues you may be experience, please reach out to Support@Managecast.com.

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.

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

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.

Veeam

Veeam Error “There is not enough space on the disk.”

/

The generic “There is not enough space on the disk” error message is a fairly common and easy issue to investigate and resolve. The error is caused by the backup repository destination storage running out of space for the backup to run. The storage where the backups run differs from standalone agents and backups through your Veeam Backup & Replication console. If you are seeing the error message for a Standalone Veeam Agent backup: If you are seeing the error message for a VM or Machine on Veeam Backup & Replication Console: There may be additional reasons that may be preventing your backups from running. Please reach out to Support@Managecast.com to help troubleshoot and get your backups running successfully.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 SharePoint “The remote server returned an error: (429)”

/

The nuisance error, “The remote server returned an error: (429)” in Veeam Backup for Microsoft 365 indicates that you have exceeded the request rate limit imposed by Microsoft. This occurs when too many requests are made to Microsoft within a specific time frame. We commonly see this during the initial Veeam for M365 backup and the error resolves itself during the automatic retry, which is enabled by default. If you would like to make changes on the backend in Microsoft, such as editing Retry-After headers or decorating traffic, you may refer to this Microsoft Article on how to avoid getting throttled in SharePoint. If the (429) error persist, please reach out to us at Support@Managecast.com. We’re happy to assist in troubleshooting and resolving your issue.

Veeam

Veeam Backup “given key was not present in the dictionary” error

/

We have run into an issue when a job starts reporting the “The given key was not present in the dictionary” error. This seems to occur when a backup is interrupted multiple times. When this isn’t caused by the metadata being corrupted, we’ve been able to be resolve the error by removing the chain, re-importing, and re-mapping the job: 1. Connect to the tenant Veeam backup console.2. Open Home – > Backup Copy Jobs.3. Find your cloud job that processes the backup you want to modify, right-click the job and select Disable. The option can be greyed-out if the job is not scheduled to run at some particular time.4. Open the Home –> Backups –> Cloud view.5. Press and hold the [CTRL] key (please do not release it) and right-click the backup you want to modify.6. Select the Remove from configuration option.7. Open the Backup Infrastructure -> Backup Repositories view.8. In the inventory pane, find the cloud repository where the affected backup is stored, right-click it and select Rescan.During the rescan operation, in the statistics window, you will see that the backup was imported.The modified backup should appear in the Home –> Backups –> Cloud node in the tenant Veeam backup console.9. Open Home –> Backup Copy and find the cloud job associated with this backup.10. Right-click the job, select Edit, proceed to the Storage step of the wizard and select Map backup.11. Select the cloud backup from the cloud repository. Then, click OK to finish mapping.12. Save the settings and enable the job. Then run it or wait for the job to run upon schedule. If this does not resolve the issue, it may point to metadata corruption as the culprit. For further troubleshooting, please reach out to Support@Managecast.com to help get your backups running again.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “Failed to find Team mailbox owner account”

/

The “Failed to find Team mailbox owner account” error can be caused by the owner of the mailbox being moved, or if the owner no longer has a licensed assigned. Resolving either of these will also resolve your M365 issues. Here are the steps to resolving the cause to either issue: If the owner was removed from the mailbox: Assigned owner does not have a license: As these are two of the most common causes of the “Failed to find Team mailbox owner account” error, there may be other issues causing the error. If your issues persist, please reach out to Support@Managecast.com for assistance. Additional Microsoft information on assigning a Team mailbox owner can be found HERE, and assigning a license can be found HERE.

  • (513) 735 - 6868
  • sales@managecast.com
  • 8354 Princeton Glendale Rd #108
    West Chester, OH 45069
Facebook X-twitter Youtube Linkedin

Powered by Veeam

Veeam Solutions

DRaaS

Resellers & Partners

Support

Blog

About

Scroll to Top