Contact Us

Backup

Veeam

Veeam Backup & Replication v9.5 and Older backup proxy is missing C++ runtime components legacy error

/

If your backup proxy is running an older OS, such as Windows Server 2008, you will receive the error ”Backup proxy is missing C++ runtime components.” This can be resolved by downloading an updated version of Visual C++. This issue may also occur when security hardening and the registry key CWDIllegalInDllSearch is used. Manual downloads can be found below. The redistributable package varies by VMware vSphere version. VMware vSphere version: 5.5 & 6.0 VMware vSphere version 6.5 & 6.7 More information on the warning can be found in the Veeam KB. If you would like assistance resolving the issue, please email our team of Certified Veeam Engineers Support@Managecast.com

Office 365 Backup, Veeam

Veeam for Microsoft 365 Mailbox does not have a valid Microsoft 365 license warnings

/

Veeam Backup for Microsoft 365 can only backup mailboxes that are licensed*. If a mailbox is selected to backup and does not have a licensed assigned, Veeam will report a warning stating the “Mailbox does not have a valid Microsoft 365 license.” There are two options for resolving the “Mailbox does not have a valid Microsoft 365 license” warning. Option 1: Assign a valid license to the mailbox that you would like to backup. Option 2: If the mailbox does not need to be backed up, then you can exclude the mailbox. Below are the steps to exclude a mailbox: If you are backing up your entire organization: If you have specific objects selected to backup: * Shared and resource mailboxes are the exception, and do not require a license to backup. If the warning persist, or would like any other Veeam assistance, please reach out to Support@Managecast.com

Veeam

Veeam Explorer for Microsoft Exchange Timeouts

/

A possible issue when restoring a large number of items with the Veeam Explorer for Microsoft Exchange can be operations timing out. Especially when using the advanced search feature in large mailboxes. Error messages related to these timeouts can pop-up during the restore with the following message: Connection to server was unexepectedly close. See log file for details. Error: This request operation sent to net.tcp://127.0.0.1:59148/ArchiverExchangeServiceOrg did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. In the Veeam Explorer for Exchange log files (C:\ProgramData\Veeam\Backup\ExchangeExplorer\Logs) these errors may also be present: Error: The message could not be transferred within the allotted timeout of 00:01:00. There was no space available in the reliable channel’s transfer window. The time allotted to this operation may have been a portion of a longer timeout. Error: Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall. Error: A blocking operation was interrupted by a call to WSACancelBlockingCall To resolve this issue, the timeout can be increased by editing the Exchange Explorer config.xml file. To do this, follow these steps: Make sure that the Exchange explorer is closed and no restore sessions are running. If you are performing the restore from a Veeam for Microsoft 365 server, make sure no jobs are running and stop the Veeam Services: Next, open a text editor and edit the file: C:\ProgramData\Veeam\Backup\ExchangeExplorer\Config.xml Add the following text between the tags in the file: <WCF OperationTimeout=”3600″ />. Don’t modify any other lines in this file. Example: Finally, save the file and start the Veeam for Microsoft 365 services again. After following these steps try the restore again. The time-out issues should now be resolved.

Office 365 Backup, Veeam

Veeam for Microsoft 365 “User ‘USERNAME’ does not have a valid Microsoft 365 license with SharePoint plan enabled” Warning

/

If a user is set to back up a SharePoint but doesn’t have a SharePoint plan, you’ll start seeing warnings pop up in your Veeam for Microsoft 365 backups. There are two options for resolving the “User ‘USERNAME’ does not have a valid Microsoft 365 license with SharePoint plan enabled” warning. Option 1: Contact Microsoft to add a SharePoint plan to the current users’ license. Option 2: If the SharePoint site does not need to be backed up, or is not licensed to, then you can exclude the SharePoint for the user. Below are the steps to exclude a SharePoint for a specific user: If you are backing up your entire organization: If you have specific objects selected to backup: If the warning persist, please reach out to Managecast and we are happy to help resolve this and any other Veeam issues.

Office 365 Backup, Veeam

Veeam M365 “Cannot change web part export mode to ‘All’, because custom scripting is disabled for site” Warnings

/

When setting up your Veeam for Microsoft 365 backups, you may select to backup WebParts. If Custom Scripts are not enabled, you will likely run into the warning “Cannot change web part export mode to ‘All’, because custom scripting is disabled for site.” By default, both the “Allow users to run custom script on personal sites” and “Allow users to run custom script on self-service created sites” options are set to “Prevent.” Here are quick steps to get your web parts backing up successfully: Additional information can be found here at Veeam and Microsoft. If you’d like assistance resolving your Veeam for M365 warnings, please reach out to Managecast. We’re happy to assist in troubleshooting and resolving your issue.

Office 365 Backup, Veeam

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

/

The code (429) in Veeam Backup for Microsoft 365 indicates that you have exceeded the rate limit imposed by Microsoft. It occurs when too many requests are made to Microsoft within a specific time frame. Here are some recommendations in handling the (429) throttling issue: • Upgrade Veeam. Veeam has released Veeam Backup for Microsoft 365 7.0.0.3007 which addresses the (429) warning. • Allow retries. (429) warnings normally clear up on a retry. Retries should be enabled by default. If retries are not enabled, you may turn these on in the last tab of the job settings. • Temporarily disable EWS Throttling Policy. Additional information can be found here at Veeam and Microsoft. If the (429) error persist, please reach out to Managecast. We’re happy to assist in troubleshooting and resolving your issue.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “Failed to find group owner account” error and how to resolve it

/

The “Failed to find group owner account” error occurs when a Microsoft 365 group does not have an assigned owner. To fix this error, you can follow these steps: Additional information can be found in the Veeam Article KB3105 If you continue to experience issues with your Veeam M365 backups, please reach out to Managecast and we can assist in resolving your issues.

Office 365 Backup, Veeam

What are the Veeam M365 OneDrive was not found/ Personal site was not found warnings and how to resolve or exclude?

/

Veeam will only backup user OneDrive and Personal site’s only when they have an assigned license. Veeam will present a warning if the Microsoft account does not have a OneDrive or Personal site enabled. You can exclude the Site/OneDrive in Veeam with the following steps depending on how you have set up your backups: 1. Log onto your Veeam M365 Console. 2. Select the job experiencing the warning and Select Edit. 3a. If you are backing up your entire organization, navigate to the Select objects to exclude tab. 4a. Click the Add button to open the users list, select the user(s) that is experiencing the warning, and select click Add. 5a. Select the user and Click the Edit button. Check the OneDrive and/or Site to exclude, hit OK, and save the job settings. 3b. If you have specific users selected to backup, navigate to the Select objects to back up tab 4b. Select the user from the list and click the Edit button. Uncheck the OneDrive and/or Site to exclude, hit OK, and save the job settings. If your warnings are not resolved after making these changes, please reach out to Managecast, and we will be happy to help troubleshoot the issue.

DRaaS, Veeam

Resolving Veeam Cloud Connect Replication Network Detection Warnings.

/

Veeam Cloud Connect Replication can sometimes complete with one of the following warnings: These warnings can occur with Linux virtual machines, when the virtual machine has multiple network adapters, or when the networking configuration is not set up correctly. No static IP addresses detected for VM, please specify default gateway settings manually. This warning means that Veeam was unable to assign an IP address to the target replica VM. This is typically due to the source being a Linux VM. The following information is from the Veeam documentation and explains this behavior, including a registry key for a workaround. One or more source networks possible were mapped to the same cloud network. Simultaneous partial failover of VMs on these networks may cause issues. This warning means that Veeam wasn’t able to detect the gateway address of the source VM causing it to be unable to automatically determine which failover network to map the production network to. The solutions for this include: Links: Please reach out to Managecast if the warnings persist and we can help troubleshoot and resolve the issue.

Veeam

Veeam Code: 1072 The specified service has been marked for deletion.

/

Veeam error code 1072 is related to Volume Shadow Copy Service (VSS) issues on your Windows VM or physical machine. The error message indicates that the VSS writer component has been marked for deletion and cannot be used. Here are some steps you can take to fix the Veeam code: 1072 VSS marked for deletion issue: 1. Restarting the VM. 2. Restart the VSS service 3. Check for other failed VSS writers Please reach out to Managecast if your errors persist and we can assist in troubleshooting and resolving the issue.

  • (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