Veeam

Office 365 Backup, Veeam

Veeam for Microsoft 365 “Item may have a virus reported by the virus scanner plug-in” warning

Veeam will report when an “Item may have a virus reported by the virus scanner plug-in.” This warning is caused when Veeam for M365 attempts to backup an item that the built-in Microsoft 365 virus protection has flagged as possibly being infected. If you were to attempt to download the file that is reporting the malware/virus you should be met with a “This file is compromised” message: It is recommended that you get your security team involved to investigate if the item has been compromised. Additionally, removing the infected item will clear up the warning in Veeam for M365. Additionally information on Microsoft built-in virus protection can be found HERE. If the item that is reporting as potentially having a virus is downloadable and found to be a healthy file, please reach out to Support@Managecast.com and we can assist in investigating the issue.

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.

Veeam

Veeam Backup & Replication Virtual Machine is unavailable and will be skipped from processing

A common Veeam Backup and Replication warning we see is when a virtual machine becomes unavailable. Veeam will report the “Virtual Machine VMNAME is unavailable and will be skipped from processing” error for a few reasons. Some common reasons for the error could be: Depending on the cause of the VM becoming unavailable will determine what actions you can take to get the VM backing up. These are just a few common reasons and solutions for VMs becoming unavailable. If you would like further assistance with your backups please feel free to reach out to Support@Managecast.com.

Veeam

Veeam “Unable to connect to SMTP server because of invalid credentials or connection settings”

From time to time, there are changes and updates to your SMTP server that may adversely affect you nightly reports. Your jobs will start throwing Sending e-mail report warnings that Veeam is “Unable to connect to SMTP server because of invalid credentials or connection settings” and/or “the remote certificate is invalid according to the validation procedure.” Resolving the SMTP warning is quick and easy as long as you know where to look. Here are the quick steps to checking and re-accepting the SMTP certificate: There may be other reasons that could be interrupting the communication between your Veeam backup server and the SMTP server. If you would like further assistance please contact Support@Managecast.com.

Veeam

Veeam VSPC Management Agent not reporting

From time to time, we will come across a management agent that either refuses to connect, or installs and does not report the Veeam Backup and Replication information. Below are a few troubleshooting steps we try to get these running and reporting correctly. ·        Ensure the Checkbox to allow the Veeam Backup & Replication to send the logs is checked under the Service Provider settings ·        Restart the Veeam Management Agent service ·        Uninstall and Reinstall the Veeam Management Agent using a new installer generated from the VSPC ·        Check that the management agent port, default port 6180, is not being blocked ·        In some occasions, the WMI Server may need to be reinstalled. This can be down by running the command “C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.WmiServer.exe”/install This does not encompass all of the possible reasons that your management agent may not be connecting. If you would like assistance in resolving this, or any other Veeam issues, please reach out to our team of Certified Veeam Engineers Support@Managecast.com

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.

Scroll to Top