Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/How_to_troubleshoot_Error_1007_Could_not_communicate_with_the_controller_in_bay_A_or_B_to_complete_this_request
      Applies to When attempting to communicate with the controllers via SMcli command, or using the Script Editor Window in SANtricity, the following error is observed: Error 1007 - Could not communicate w...Applies to When attempting to communicate with the controllers via SMcli command, or using the Script Editor Window in SANtricity, the following error is observed: Error 1007 - Could not communicate with the controller in bay A to complete this request. Possible causes can be but are not limited to: network or connection problems (max TCP out sessions, etc.) no power to the host or storage array Proceed below with the recommended steps to attempt to alleviate the issue.
    • https://kb.netapp.com/Legacy/SaaS_Backup/Temporary_removal_of_permissions_on_specific_SP_personal_sites
      Applies to SaaS Backup for Microsoft Office 365 Office 365 Groups Microsoft OneDrive for Business (OD4B) Issue Temporary remove user from SharePoint Primary Site Collection Administrator for OD4B comp...Applies to SaaS Backup for Microsoft Office 365 Office 365 Groups Microsoft OneDrive for Business (OD4B) Issue Temporary remove user from SharePoint Primary Site Collection Administrator for OD4B component not possible. User UPN name could not be found to use scripting for the operation
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapshots_are_not_transferring_to_destination_automatically_or_manually
      Source snapshot was being created with a _tmp extension and not replicated to destination. Snapshot was not being renamed snapshot_daily.x as other volume snapshots were. sourcecluster::> snapshot sho...Source snapshot was being created with a _tmp extension and not replicated to destination. Snapshot was not being renamed snapshot_daily.x as other volume snapshots were. sourcecluster::> snapshot show -vserver <vsname> -volume <volname> -fields create-time sourcecluster::> snapshot show -vserver <vsname2> -volume <volname2> -fields create-time <vsname2> <volname2> <snap>_daily.0 Thu Jun 02 21:32:05 2022 <vsname2> <volname2> <snap>_daily_tmp Mon Jun 06 21:32:11 2022