Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • https://kb.netapp.com/Legacy/SnapManager/Transport_Protocol_is_not_set_to_connect_the_storage_system_percentage-1_when_SME_verification_runs_in_MCC_switchover_mode
      When there is a Metrocluster Switchover, SnapDrive looks for the credentials for the surviving SVM, typycally if svm is called svm1, the surviving svm will be svm-mc. Somehow this only happens during ...When there is a Metrocluster Switchover, SnapDrive looks for the credentials for the surviving SVM, typycally if svm is called svm1, the surviving svm will be svm-mc. Somehow this only happens during SME (SnapManager for Exchange) verification process: we have observed the issue so far only when performing remote backup and verification, not local, but you can't exclude that we may see the issue in other circusmtances.
    • https://kb.netapp.com/Legacy/SnapManager/SnapManager_for_Exchange_is_unable_to_connect_to_the_DAG_or_individual_server
      When attempting to connect to the DAG or an individual server in SME, the following error message is displayed: The following error message is displayed in the SME Debug logs: [Remote PowerShell Cmdle...When attempting to connect to the DAG or an individual server in SME, the following error message is displayed: The following error message is displayed in the SME Debug logs: [Remote PowerShell Cmdlet Error]:Connecting to remote server SERVER_NAME.domain_name.com failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer.
    • https://kb.netapp.com/Legacy/SnapManager/SnapManager_for_Exchange_is_unable_to_see_database_after_Exchange_Security_update_KB5001779
      SME unable to see database after Exchange security update (KB5001779) and debug log shows error: [Remote PowerShell Cmdlet Error]
    • https://kb.netapp.com/Legacy/SnapManager/SME_backup_failed_with_The_writer_failed_due_to_an_error_that_might_not_occur_if_another_snapshot_copy_is_created
      Applies to SnapManager for Exchange 7.x Issue SnapManager for Exchange backup failed with below error: Error Code: 0xc00413ca SnapManager detected the following Exchange writer error. Please retry Sna...Applies to SnapManager for Exchange 7.x Issue SnapManager for Exchange backup failed with below error: Error Code: 0xc00413ca SnapManager detected the following Exchange writer error. Please retry SnapManager operation. VSS_E_WRITERERROR_RETRYABLE: The writer failed due to an error that might not occur if another snapshot copy is created.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapManager_for_Exchange_backup_failure_due_to_Asynchronous_call_DoSnapshotSet_timed_out
      Please wait... [19:01:56.685] Operation pending, please wait...(1) [19:11:54.964] Operation pending, please wait...(119) [19:11:55.978] Asynchronous call DoSnapshotSet timed out! [19:11:55.978] The ca...Please wait... [19:01:56.685] Operation pending, please wait...(1) [19:11:54.964] Operation pending, please wait...(119) [19:11:55.978] Asynchronous call DoSnapshotSet timed out! [19:11:55.978] The call for DoSnapshotSet was cancelled. [19:11:55.978] Failed to perform VSS snapshot, aborting... [19:11:56.181] Backup is aborted. Information SnapManager for Exchange 200 SnapManager VSS asynchronous DoSnapshotSet operation timed out after 600 seconds.
    • https://kb.netapp.com/Legacy/SnapManager/SnapManager_for_Exchange_backups_are_failing_with_Error_code__0xc004023b_The_required_protocol_is_not_licensed
      Applies to SnapManager for Exchange (SME) 7.2.x SnapDrive for Windows (SDW) 7.1.5 Issue SnapManager for Exchange backup fails with: Error code: 0xc004023b, The required protocol is not licensed when c...Applies to SnapManager for Exchange (SME) 7.2.x SnapDrive for Windows (SDW) 7.1.5 Issue SnapManager for Exchange backup fails with: Error code: 0xc004023b, The required protocol is not licensed when checking licenses. The license is installed on the storage and there is no server side license configured.