01.04.2017 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

//01.04.2017 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

01.04.2017 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

Vom 31.03.2017 bis zum 01.04.2017 wurden 24 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 31.03.2017 vom Typ: Troubleshooting
Titel: VDP File Level Restore fails to restore a multiple primary partition virtual machine with the error: Extended partitions are not supported

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Registering the VDP 5.1 appliance with vCenter Server fails with the error: Specified user either is not a dedicated VDP user or does not have sufficient vCenter privileges to administer VDP

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Upgrading from a Dell customized VMware ESXi 5.0 ISO to a later version fails at 26%

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Recreating a missing VMFS datastore partition in VMware vSphere 5.0/5.1/5.5

Am 31.03.2017 vom Typ: Troubleshooting
Titel: vSphere Data Protection 5.5.1 User Interface times out with the error: Failed to acquire all licenses

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Required Security Hotfix – Horizon DaaS Platform 6.1.6

Am 31.03.2017 vom Typ: Troubleshooting
Titel: How to reset Inventory Service database for vCenter Server

Am 31.03.2017 vom Typ: Informational
Titel: VMware vSphere 5.x and 6.x support with NetApp MetroCluster

Am 31.03.2017 vom Typ: Best Practices
Titel: Opening disk on second scsi controller using VixDiskLib_Open fails with error: You do not have access rights to this file

Am 31.03.2017 vom Typ: Troubleshooting
Titel: VMware vSphere Data Protection – File Level Restore (FLR) fails on Windows 2012 Guest Operating System

Am 31.03.2017 vom Typ: Informational
Titel: Upgrading vRealize Network Insight to version 3.3

Am 31.03.2017 vom Typ: Troubleshooting
Titel: SNMP monitoring of VMware ESXi hosts running MSCS virtual machines fail with timeout errors

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Cannot choose a restore destination when running a VDP restore operation

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Connecting to vSphere Data Protection over the vCenter Server plugin fails

Am 31.03.2017 vom Typ: Informational, Troubleshooting
Titel: Using the Exchange DAG Cluster Configuration Tool for VMware vSphere Data Protection (VDP) fails

Am 31.03.2017 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Check Information

Am 31.03.2017 vom Typ: Troubleshooting
Titel: OVF deployment fails with the error: „task was canceled by a user“

Am 31.03.2017 vom Typ: Alerts
Titel: vAPI endpoint status changes to yellow in vCenter Server

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Virtual machine power off during snapshot consolidation

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Upgrading to vCenter Server 6.0 Update 2a fails on VCSServiceManager with error code ‚1603‘

Am 31.03.2017 vom Typ: Troubleshooting
Titel: After migrating vCenter Server 6.0 from an Embedded Platform Services Controller to External Platform Services Controller the Performance Chart Service fails with the error: Unable to Initialize servlet

Am 31.03.2017 vom Typ: Troubleshooting
Titel: „esxupdate error code 15“ error after patching an ESXi host

Am 31.03.2017 vom Typ: Troubleshooting
Titel: ESXi host fails with PSOD when using Intel Xeon Processor E5 v4, E7 v4, and D-1500 families

Am 31.03.2017 vom Typ: Troubleshooting
Titel: Unable to connect to remote vSphere Replication Server 6.0

Ausführliche Auflistung:

Titel: VDP File Level Restore fails to restore a multiple primary partition virtual machine with the error: Extended partitions are not supported

Knowledgebase Nr: 2052950

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 5.1.x

Link zum Artikel: 2052950

Beschreibung:
A VMware Data Protection (VDP) File Level Restore (FLR) task fails to restore a virtual machine with multiple primary partititions on the same disk. After a virtual machine FLR, the restore point is mounted but restore point folders are not accessible. The /usr/local/avamar/var/flr/server_logs/flr-server.log file contains an entry similar to:[MM – DEBUG] 2013/05/30 11:19:43 TID=6470 MID=133146: Error Code already saved. Ret: 1048605, Error: Extended partitions are not supported
… Für weitere Details den Link zum Artikel anklicken

Titel: Registering the VDP 5.1 appliance with vCenter Server fails with the error: Specified user either is not a dedicated VDP user or does not have sufficient vCenter privileges to administer VDP

Knowledgebase Nr: 2040066

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 5.1.x

Link zum Artikel: 2040066

Beschreibung:
Cannot register the vSphere Data Protection (VDP) appliance with vCenter Server Using Administrator credentials when attempting to register the VDP appliance with vCenter Server fails You see the error:Specified user either is not a dedicated VDP user or does not have sufficient vCenter privileges to administer VDP. Please update your user role and try again Non-English vSphere Client shows a red cross mark with no error message while attempting registration of the VDP appliance.
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading from a Dell customized VMware ESXi 5.0 ISO to a later version fails at 26%

Knowledgebase Nr: 2036167

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2036167

Beschreibung:
Cannot upgrade ESXi 5.0.x hosts installed using the Dell custom image to ESXi 5.1 or ESXi 5.5 Upgrading the ESXi 5.0 host fails at 26% of remediation Upgrading the ESXi 5.0 host installed using the Dell custom image fails and reverts to the previous build In the ESXi console, you see these errors:Could not obtain module order from esx image db : Error (see log for more info): File path of/etc/vmware/oem.xml is claimed by Multiple overlay VIBs:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Recreating a missing VMFS datastore partition in VMware vSphere 5.0/5.1/5.5

Knowledgebase Nr: 2046610

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x

Link zum Artikel: 2046610

Beschreibung:
A datastore has become inaccessible. A VMFS partition table is missing.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSphere Data Protection 5.5.1 User Interface times out with the error: Failed to acquire all licenses

Knowledgebase Nr: 2063208

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 5.5.x

Link zum Artikel: 2063208

Beschreibung:
When editing a backup job with vSphere Data Protection (VDP) 5.5.1 or when viewing the Configuration tab of the VDP appliance, you see the error:Failed to acquire all licenses When acknowledging the popup, the VDP UI times out and does not allow you to edit the backup job. The VDP Advanced license assignment section of the Configuration tab fails to populate with data. In the /usr/local/avamar/var/vdr/server_logs//vdr-server.log file, of the VDP appliance, you see entries similar to: ERROR…
… Für weitere Details den Link zum Artikel anklicken

Titel: Required Security Hotfix – Horizon DaaS Platform 6.1.6

Knowledgebase Nr: 2149500

Aktualisiert: 31.03.2017

Für Produkte: VMware Horizon DaaS On Premise Platform 6.1.x

Link zum Artikel: 2149500

Beschreibung:
All users with Horizon DaaS Platform 6.1.6 appliances should install this hotfix on those appliances as soon as possible. For information about the hotfix for 6.1.5 appliances, see Required Security Hotfix – Horizon DaaS Platform 6.1.5 (2149588). The hotfix is required to address a known security vulnerability. For more information about the issue, see the VMware security advisory.
… Für weitere Details den Link zum Artikel anklicken

Titel: How to reset Inventory Service database for vCenter Server

Knowledgebase Nr: 2146264

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2146264

Beschreibung:
This article provide steps to reset the Inventory Service database for vCenter Server installed on Microsoft Windows. This involves creating the fresh Inventory Service database and re-registering Inventory Service with Component Manager.
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSphere 5.x and 6.x support with NetApp MetroCluster

Knowledgebase Nr: 2031038

Kategorie: Informational

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 2031038

Beschreibung:
This article provides information about deploying a vSphere Metro Storage Cluster (vMSC) across two datacenters or sites using the NetApp MetroCluster Solution with vSphere 5.0, 5.1, or 5.5 and 6.x for ESXi 5.0, 5.1, or 5.5, and 6.x. This article applies for FC, iSCSI, and NFS implementations of MetroCluster on Clustered Data ONTAP 8.3.
… Für weitere Details den Link zum Artikel anklicken

Titel: Opening disk on second scsi controller using VixDiskLib_Open fails with error: You do not have access rights to this file

Knowledgebase Nr: 2075069

Kategorie: Best Practices

Aktualisiert: 31.03.2017

Für Produkte: Virtual Disk Development Kit 5.1, Virtual Disk Development Kit 5.5

Link zum Artikel: 2075069

Beschreibung:
When using Virtual Disk Development Kit (VDDK) during a backup, if the hot-add of backed up disks exhaust the targets in the first SCSI and overflows to other SCSI controllers, the backup may fail with this error: You do not have access rights to this file.
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSphere Data Protection – File Level Restore (FLR) fails on Windows 2012 Guest Operating System

Knowledgebase Nr: 2144629

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 6.0.x, VMware vSphere Data Protection 6.1.x

Link zum Artikel: 2144629

Beschreibung:
VMware vSphere Data Protection – File Level Restore (FLR) fails on Windows 2012 Guest operating system running on GUID Partition Table (GPT) disks. In the /usr/local/avamar/var/mc/server_log/mcserver.log file, you see error similar to: com.avamar.mc.cr.BrowserVm.browse FINE: flr browse result: The flag incomplete=“1″.
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading vRealize Network Insight to version 3.3

Knowledgebase Nr: 2149264

Kategorie: Informational

Aktualisiert: 31.03.2017

Für Produkte: VMware vRealize Network Insight 3.x

Link zum Artikel: 2149264

Beschreibung:
This article provides steps to upgrade vRealize Network Insight to version 3.3.
… Für weitere Details den Link zum Artikel anklicken

Titel: SNMP monitoring of VMware ESXi hosts running MSCS virtual machines fail with timeout errors

Knowledgebase Nr: 2105674

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Link zum Artikel: 2105674

Beschreibung:
SNMP monitoring of VMware ESXi hosts fail with timeout errors. The ESXi host is running a virtual machine participating in an MSCS using shared RDMs and SCSI Reservations across other hosts. In /var/log/vmkernel.log on the ESXi host contains errors similar to:<YYYY-MM-DD>T<TIME>Z cpu3:11251)ScsiDeviceIO: 2331: Cmd(0x412400f25540) 0x1a, CmdSN 0x42f3b from world 0 to dev „naa.6000d31000780c000000000000000022“ failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Running the…
… Für weitere Details den Link zum Artikel anklicken

Titel: Cannot choose a restore destination when running a VDP restore operation

Knowledgebase Nr: 2114162

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 5.8.x, VMware vSphere Data Protection 6.0.x

Link zum Artikel: 2114162

Beschreibung:
Unable to choose the restore destination when running a VMware vSphere Data Protection restore operation. When performing a restore operation with vSphere Data Protection (VDP) 5.8 or VDP 6.0, the dropdown list for the destination is empty.
… Für weitere Details den Link zum Artikel anklicken

Titel: Connecting to vSphere Data Protection over the vCenter Server plugin fails

Knowledgebase Nr: 2146234

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 6.0.x, VMware vSphere Data Protection 6.0.x, VMware vSphere Data Protection 6.1.x

Link zum Artikel: 2146234

Beschreibung:
Connecting to the vSphere Data Protection over the vCenter Server plug-in fails. You see entries similar to:“Cannot navigate to the desired location.“Error details: An error occured while activating extension com.vmware.vdp2.mainapplication.Invalid domain view id: com.vmware.vdp2.mainapplication“Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
… Für weitere Details den Link zum Artikel anklicken

Titel: Using the Exchange DAG Cluster Configuration Tool for VMware vSphere Data Protection (VDP) fails

Knowledgebase Nr: 2103583

Kategorie: Informational, Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vSphere Data Protection 5.8.x

Link zum Artikel: 2103583

Beschreibung:
Exchange client setup for Exchange 2013 DAG Cluster fails. In the av_cluster_config_wizard.log file, you see entries similar to:av_cluster_config_wizard INFO<0000>: Starting backup agent ‚VMware VDP Backup Agent resource for OKUDA‘ was unsuccessfulav_cluster_config_wizard ERROR<0000>: Cannot start the cluster resource agentVMware VDP Backup Agent resource for OKUDA‘ due to the following reason: Unknown Windows operating system show event Windows System event ID 1194: Cluster…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Check Information

Knowledgebase Nr: 2114803

Kategorie: Informational, Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vSAN 6.0.x, VMware vSAN 6.1.x, VMware vSAN 6.2.x

Link zum Artikel: 2114803

Beschreibung:
This article provides an overview and serves as a homepage for the VMware vSAN health check Knowledge Base articles.
… Für weitere Details den Link zum Artikel anklicken

Titel: OVF deployment fails with the error: „task was canceled by a user“

Knowledgebase Nr: 2117310

Aktualisiert: 31.03.2017

Link zum Artikel: 2117310

Beschreibung:
Deploying OVF template from a vSphere datastore fails. In the vSphere Web Client, you see this message:OVF deployment failed: SHA1 digest of file <VMname>.vmdk does not match manifest Under the tasks for Deploy OVF template, the status reports:The task was canceled by a user Cause This issue occurs because when uploading a VMDK file from your computer to vSphere storage using the datastore browser, the MD5 checksum changes. Therefore, the checksum in the SHA1 digest does not match….
… Für weitere Details den Link zum Artikel anklicken

Titel: vAPI endpoint status changes to yellow in vCenter Server

Knowledgebase Nr: 2144715

Kategorie: Alerts

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 6.0.x, VMware vCenter Server Appliance 6.0.x

Link zum Artikel: 2144715

Beschreibung:
vCenter Server alarm reports this warning when using vCenter Server Appliance 6.0: vmware-vapi-endpoint service reports yellow status continually In the endpoint.log file, you see entries similar to:Unexpected error while initializing endpoint runtime state org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named ’some-bean-name‘ is definedNote: The endpoint log files are located at: vCenter Server Appliance – /var/log/vmware/vapi/endpoint Windows vCenter Server -…
… Für weitere Details den Link zum Artikel anklicken

Titel: Virtual machine power off during snapshot consolidation

Knowledgebase Nr: 2144095

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2144095

Beschreibung:
When Changed Block Tracking (CBT) is enabled and ESXi hosts in the environment are running ESXi 5.1 or later, you experience these symptoms: When attempting a snapshot consolidation, virtual machines running on block storage power off. Virtual machines state that an error occurred during the quiesce process. The vmware.log file for the virtual machine in question reports entries similar to:2016-01-27T13:53:31.687Z| vcpu-0| I120:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading to vCenter Server 6.0 Update 2a fails on VCSServiceManager with error code ‚1603‘

Knowledgebase Nr: 2148327

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2148327

Beschreibung:
Upgrading vCenter Server to 6.0 Update 2a fails on VCSServiceManager with this error: Installation of component VCSServiceManager failed with error code ‚1603‘. Check the logs for more details Inventory service fails to start. In the firstbootrun-updateboot-scripts.log file, you see entries similar to:Error waiting for service invsvc start. Exit code: 1066 Current State: 1ERROR:root:Unable to start service invsvc The upgrade rolls back.In…
… Für weitere Details den Link zum Artikel anklicken

Titel: After migrating vCenter Server 6.0 from an Embedded Platform Services Controller to External Platform Services Controller the Performance Chart Service fails with the error: Unable to Initialize servlet

Knowledgebase Nr: 2131327

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 6.0.x, VMware vCenter Server Appliance 6.0.x

Link zum Artikel: 2131327

Beschreibung:
After migrating vCenter Server 6.0 from an Embedded Platform Services Controller (PSC) to External Platform Services Controller, you experience these symptoms: Under the System Configuration UI (Administration > System Configuration), the VMware Performance Chart Service reports this error:Unable to Initialize servletFailed to request health status from URI <FQDN of Embedded Platform Services Controller> Under the Alarms pane, you see the Performance Charts Service Health Alarm in…
… Für weitere Details den Link zum Artikel anklicken

Titel: „esxupdate error code 15“ error after patching an ESXi host

Knowledgebase Nr: 2016147

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 2016147

Beschreibung:
When installing an extension, patch, or incompatible VIB on an ESXi host using vSphere Update Manager, the operation fails with the error:esxupdate error code 15 You may see the error:DEBUG: Creating an empty ImageProfile for bootbank /bootbank In the /var/log/esxupdate.log file, you see entries similar to:esxupdate: esxupdate: ERROR: An esxupdate error exception was caught:esxupdate: esxupdate: ERROR: Traceback (most recent call last):esxupdate: esxupdate: ERROR: File „/usr/sbin/esxupdate“,…
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host fails with PSOD when using Intel Xeon Processor E5 v4, E7 v4, and D-1500 families

Knowledgebase Nr: 2146388

Kategorie: Troubleshooting

Aktualisiert: 31.03.2017

Für Produkte: VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 2146388

Beschreibung:
When running a supported version of ESXi host with Intel Xeon Processor E5 v4, E7 v4, and D-1500 families, you may experience these symptoms: The ESXi host fails with this purple diagnostic screen (PSOD)The backtrace information is missing in the screenIn the PSOD screen, you see error similar to:2016-07-27T13:14:04.549Z cpu58:42053 )@BlueScreen: #PF Exception 14 in world 42053:vmm7:My_VM IP 0x410016bb8000 addr 0x410016bb8000…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to connect to remote vSphere Replication Server 6.0

Knowledgebase Nr: 2148489

Aktualisiert: 31.03.2017

Für Produkte: VMware vCenter Server 5.5.x, VMware vCenter Server 6.0.x, VMware vSphere Replication 6.0.x, VMware vSphere Replication 6.1.x

Link zum Artikel: 2148489

Beschreibung:
When trying to connect to target vSphere Replication server, you experience these symptoms: Generic error occurred in the vSphere Replication Management Server:Exception details: ‚The HMS service search did not return exactly one match‘ The Connection to the Target Site operation fails for the entity.You see the error:“vSphere Replication Management Server https://sdkTunnel:8089 is not accessible.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-04-01T08:04:35+00:00April 1st, 2017|Knowledgebase|
Um unsere Webseite für Sie optimal zu gestalten und fortlaufend verbessern zu können, verwenden wir Cookies. Durch die weitere Nutzung der Webseite stimmen Sie der Verwendung von Cookies zu. Weitere Informationen zu Cookies erhalten Sie in unserer Datenschutzerklärung. Sie können die Erfassung Ihrer Daten durch Google Analytics verhindern, indem Sie auf folgenden Link klicken. Es wird ein Opt-Out-Cookie gesetzt, der die Erfassung Ihrer Daten bei zukünftigen Besuchen dieser Website verhindert. Weitere Einstellungen Ok

Google Analytics deaktivieren

Verbiete Google Analytics, mich zu verfolgen