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

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

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

Vom 10.03.2017 bis zum 11.03.2017 wurden 34 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 10.03.2017 vom Typ: Informational
Titel: Cannot hot add more than 3GB to Linux 64-bit or Windows 7 operating systems

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Creating a virtual machine fails with the error: This operation is not allowed in the current state of the datastore

Am 10.03.2017 vom Typ: How to
Titel: Using the esxcli storage vmfs unmap command to reclaim VMFS deleted blocks on thin-provisioned LUNs

Am 10.03.2017 vom Typ: How to
Titel: Enabling trivia logging in VMware vCenter Server

Am 10.03.2017 vom Typ: Best Practices
Titel: Considerations for using software iSCSI port binding in ESX/ESXi

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Error when connecting to a VMware Workstation server configured on a non-default port

Am 10.03.2017 vom Typ: How to, Informational
Titel: Using the Log Browser to view, search, and export Logs for troubleshooting

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „Make sure migration assistant is running on the VUM server.“ error when upgrading to vCenter Server Appliance 6.5

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „Access Denied“ error when using SSH to login to the appliance

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „Assign virtual machine to resource pool“ error when performing tasks through vSphere Web Client

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Steps to enable the JMX port to capture thread dump/ heap dump for VMware vCenter Orchestrator

Am 10.03.2017 vom Typ: Alerts
Titel: vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Checking and restoring the OVF context of the vSphere Replication Appliance

Am 10.03.2017 vom Typ: How to
Titel: How to enable SSLv3 and TLSv1 for outgoing HTTPS connections manually in vRealize Orchestrator

Am 10.03.2017 vom Typ: Informational
Titel: FAQ: VMware Platform Services Controller in vSphere 6.0

Am 10.03.2017 vom Typ: Troubleshooting
Titel: vRA 7.x services fail when modifying the vIDM database

Am 10.03.2017 vom Typ: Troubleshooting
Titel: VMware vCenter Server 6.0 U3 SDK and CLI support

Am 10.03.2017 vom Typ: How to, Informational
Titel: Configuring Windows PSC 6.0 High Availability for vSphere 6.0

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „XXX Uninitialized error“ and „Not Ready“ Status in host preparation

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „The backing EAM agency for this deployment could not be found“ error after restore from backup

Am 10.03.2017 vom Typ: Licensing, Troubleshooting
Titel: Error message when applying a license key to a host running ESXi 6.0

Am 10.03.2017 vom Typ: Informational
Titel: Allowing a client to run a backup job for more than 24 hours in VMware vSphere Data Protection

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Upgrading vCenter Server from version 5.5 to 6.0 update 2a fails

Am 10.03.2017 vom Typ: Informational
Titel: Determining replication agreements and status with the Platform Services Controller 6.X

Am 10.03.2017 vom Typ: Informational
Titel: Supported versions of Windows 10 on Horizon View

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „Server has a weak ephemeral Diffie-Hellman public key“ error while accessing vRO

Am 10.03.2017 vom Typ: Troubleshooting
Titel: „Current node is not ACTIVE“ error when logging in to vRO 7.0

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Connecting to SRM using an domain account with sufficient privileges fails

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Platform Services Controller 6.0 deployment takes several hours

Am 10.03.2017 vom Typ: Informational
Titel: Upgrading to NSX for vSphere 6.3.0 fails when using Hardware Gateway

Am 10.03.2017 vom Typ: Troubleshooting
Titel: ESXi host fails with intermittent NMI PSOD on HP ProLiant Gen8 servers

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Adding new compute node fails on VIO

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Unable to take snapshots

Am 10.03.2017 vom Typ: Troubleshooting
Titel: Agent machine gets STOP error or stops responding when you open a local file shared with CDR

Ausführliche Auflistung:

Titel: Cannot hot add more than 3GB to Linux 64-bit or Windows 7 operating systems

Knowledgebase Nr: 2008405

Kategorie: Informational

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2008405

Beschreibung:
When trying to hot add memory to a Linux 64-bit or Windows 7 32-bit guest operating systems, you cannot increase the memory to more than 3GB. In the vSphere Web Client, you see the message:The number must be less than or equal to 3072 MB In the vSphere Client, you see the message:This setting is restricted because the virtual machine is powered on
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating a virtual machine fails with the error: This operation is not allowed in the current state of the datastore

Knowledgebase Nr: 2045801

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2045801

Beschreibung:
When connected to vCenter Server, you experience these symptoms: Cannot create virtual machines from templates.Cannot create a new virtual machine.You see the alarm:Thin-provisioned storage devices met soft threshold The storage utilization on a LUN is above 90%.In the vpxd.log file, you see entries similar to:mem> [verbose ‚Default‘ opID=14603DCE-00001015-3f] [VpxVmomi] Invoke done: vim.Folder.createVm session: f7cc8b40-671c-4729-02e6-9a12996fc5b8mem> [verbose ‚SoapAdapter.HTTPService’…
… Für weitere Details den Link zum Artikel anklicken

Titel: Using the esxcli storage vmfs unmap command to reclaim VMFS deleted blocks on thin-provisioned LUNs

Knowledgebase Nr: 2057513

Kategorie: How to

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2057513

Beschreibung:
This article provides steps to reclaim unused storage blocks on a VMFS datastore for a thin-provisioned device using the esxcli storage vmfs unmap command.   vSphere
5.5 introduced a new command in the esxcli namespace that allows deleted blocks to be reclaimed on thin provisioned LUNs that support the VAAI UNMAP primitive.The command can be run without any maintenance window, and the reclaim
mechanism has been enhanced as such: Reclaim size can be specified in blocks instead of a percentage…
… Für weitere Details den Link zum Artikel anklicken

Titel: Enabling trivia logging in VMware vCenter Server

Knowledgebase Nr: 1001584

Kategorie: How to

Aktualisiert: 10.03.2017

Für Produkte: VMware VirtualCenter 2.0.x, VMware VirtualCenter 2.5.x, VMware vCenter Server 4.0.x, VMware vCenter Server 4.1.x, VMware vCenter Server 5.0.x, VMware vCenter Server 5.1.x, VMware vCenter Server 5.5.x, VMware
vCenter Server 6.0.x, VMware vCenter Server 6.5.x

Link zum Artikel: 1001584

Beschreibung:
When troubleshooting VMware vCenter Server issues, it may be helpful to enable trivia logging in vCenter Server. These logs contain the most verbiage possible, assisting in understanding underlying issues.  For more information, see: Increasing vCenter Server and ESX/ESXi logging levels (1004795) Uploading diagnostic information for VMware (1008525)
… Für weitere Details den Link zum Artikel anklicken

Titel: Considerations for using software iSCSI port binding in ESX/ESXi

Knowledgebase Nr: 2038869

Kategorie: Best Practices

Aktualisiert: 10.03.2017

Für Produkte: VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2038869

Beschreibung:
This article provides information on when to use and when not to use iSCSI port binding. For information on how to configure port binding, see the storage guide for your version of ESXi/ESX.
… Für weitere Details den Link zum Artikel anklicken

Titel:
Error when connecting to a VMware Workstation server configured on a non-default port

Knowledgebase Nr: 2045426

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware Workstation 9.x (Linux), VMware Workstation 9.x (Windows)

Link zum Artikel: 2045426

Beschreibung:
You cannot connect to a VMware Workstation server that is not configured on the default 443 port,When trying to connect to a VMware Workstation server,
you see this error:MEM_ALLOC d:/build/ob/bora-894247/bora/lib/unicode/unicodeSimpleBase.c:793

… Für weitere Details den Link zum Artikel anklicken

Titel: Using the Log Browser to view, search, and export Logs for troubleshooting

Knowledgebase Nr: 2032888

Kategorie: How to, Informational

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2032888

Beschreibung:
You can view, search, and export one or more vCenter Server and ESXi log files at a time using the log browser. You can
also
export, manage, and view different log types. Note: This is a not a comprehensive guide. For more information, see the vSphere documentation. The documentation contains definitive information. If there is a discrepancy between the documentation and this article, assume that the documentation is correct.VMware vSphere Documentation 5.0 – 5.5VMware vSphere Documentation 6.0…
… Für weitere Details den Link
zum Artikel anklicken

Titel: „Make sure migration assistant is running on the VUM server.“ error when upgrading to vCenter Server Appliance 6.5

Knowledgebase Nr: 2148400

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2148400

Beschreibung:
Upgrading the vCenter Server Appliance 6.0 to 6.5 fails with the error:Unable to retrieve the migration assistant extension on source vCenter Server. Make
sure migration assistant is running on the VUM server. In the %temp%installer-xxxxxxxx-xxxxxxxxx.log file, there are entries similar to:YYYY-MM-DDTHH:<TIME> – info: VUM upgrade switch enabled, query extensions and get the size infoYYYY-MM-DDTHH:<TIME> – info: Got the extension: com.vmware.vcIntegrityYYYY-MM-DDTHH:<TIME> -…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Access Denied“ error when using SSH to login to the appliance

Knowledgebase Nr: 2146205

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2146205

Beschreibung:
Using SSH to log in to vCenter Server Appliance fails You see the error:Access Denied Note: For additional symptoms
and log entries, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel: „Assign virtual machine to resource pool“ error when performing tasks through vSphere Web Client

Knowledgebase Nr: 2142994

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2142994

Beschreibung:
Create, Clone, Migrate virtual machine tasks performed through vSphere Web Client (NGC) fails with the error:Resource > Assign virtual machine to resource pool

Für weitere Details den Link zum Artikel anklicken

Titel: Steps to enable the JMX port to capture thread dump/ heap dump for VMware vCenter Orchestrator

Knowledgebase Nr: 2144338

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware vCenter Orchestrator 5.5.x, VMware vCenter Orchestrator Appliance 5.5.x, VMware vRealize Orchestrator 6.0.x

Link zum Artikel: 2144338

Beschreibung:
VMware vCenter Orchestrator takes long time for Workflows to execute. vRO Service might crash because
of Memory leak.  In the /var/log/vco/app-server/Server.log | Catalina. Out, you see entries similar to:  SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/vco] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. SEVERE [localhost-startStop-2]…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider

Knowledgebase Nr: 2145308

Kategorie: Alerts

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2145308

Beschreibung:
This message is displayed for non-vSAN enabled ESXi hosts:Retrieve a ticket to register the Virtual SAN VASA Provider The environment uses vCenter Server 6.0 Update 2 and does not have vSAN enabled
… Für weitere Details den Link zum Artikel anklicken

Titel: Checking and restoring the OVF context of the vSphere Replication Appliance

Knowledgebase Nr: 2106709

Aktualisiert: 10.03.2017

Für Produkte: VMware vSphere Replication 5.8.x, VMware vSphere Replication 6.0.x, VMware vSphere Replication 6.5.x

Link zum Artikel: 2106709

Beschreibung:
Missing OVF context can cause multiple problems when using vSphere Replication. These problems include, but are not limited to the following: Upgrading vSphere Replication might fail. After an upgrade, the vSphere Replication appliance is corrupted. After an upgrade, the vSphere Replication appliance appears as a vSphere Replication server. Registering an upgraded vSphere Replication instance with vCenter Single Sign-On fails with errorBad exit code: 1. The OVF context of the vSphere…
… Für weitere Details den Link zum Artikel anklicken

Titel: How to enable SSLv3 and TLSv1 for outgoing HTTPS connections manually in vRealize Orchestrator

Knowledgebase Nr: 2144318

Kategorie: How to

Aktualisiert: 10.03.2017

Für Produkte: VMware vRealize Orchestrator 6.0.x, VMware vRealize Orchestrator 7.0.x

Link zum Artikel: 2144318

Beschreibung:
This article provides information on how to enable SSLv# and TLSv1 for outgoing HTTPS connections in vRealize Orchestrator 6.0.4 and 7.0.x manually. To enable outgoing HTTP connections through the SOAP, HTTP-REST, and Orchestrator Configuration plug-ins to servers that require TLSv1 when using vRealize Orchestrator 6.0.4 and 7.0.x, you must enable SSLv3 and TLSv1 manually. This issue might occur in the SOAP, REST, and Configuration plug-ins in Orchestrator, which use the Import a certificate…
… Für weitere Details den Link zum Artikel anklicken

Titel: FAQ: VMware Platform Services Controller in vSphere 6.0

Knowledgebase Nr: 2113115

Kategorie: Informational

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2113115

Beschreibung:
This article provides information on some of the frequently asked questions about VMware Platform Services Controller (PSC) for vSphere 6.0. The PSC contains common infrastructure services such as vCenter Single Sign-On (SSO), VMware Certificate Authority (VMCA), licensing, and server reservation and registration services. For more information, see: VMware vCenter Single Sign-On Server 5.5 FAQs (2057799) for historical reference vSphere Software Components section in the vCenter Server and…
… Für weitere Details den Link zum Artikel anklicken

Titel: vRA 7.x services fail when modifying the vIDM database

Knowledgebase Nr: 2144907

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware vRealize Automation 7.0.x

Link zum Artikel: 2144907

Beschreibung:
After modifying the vIDM database, you experience these symptoms: All vRealize Automation services fail vIDM is unable to communicate with its database In the horizon.log file of vRealize Automation appliance, you see entries similar to: org.postgresql.util.PSQLException: FATAL: password authentication failed for user „horizon“ 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: VMware vCenter Server 6.0 U3 SDK and CLI support

Knowledgebase Nr: 2149213

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2149213

Beschreibung:
SDK communication with vCenter Server or ESX might fail when the vCenter Server system is configured to use the TLSv1.1 and TLSv1.2 protocols. vCLI/ESXCLI/PowerCLI communication with vCenter Server or ESX might fail when the vCenter Server system is configured to use the TLSv1.1 and TLSv1.2 protocols.
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring Windows PSC 6.0 High Availability for vSphere 6.0

Knowledgebase Nr: 2113085

Kategorie: How to, Informational

Aktualisiert: 10.03.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2113085

Beschreibung:
The article provides the procedure to configure Platform Services Controller (PSC) High Availability for vSphere 6.0 for a Windows Server installation. If you are using the vCenter Server 6.0 Appliance, deployed as Platform Services Controllers, see Configuring PSC 6.0 High Availability for vSphere 6.0 using vCenter Server 6.0 Appliance (2113315) Notes: If you have upgraded from vSphere 5.5 Single Sign-On, see Configuring PSC 6.0 High Availability after upgrading from SSO 5.5 High…
… Für weitere Details den Link zum Artikel anklicken

Titel: „XXX Uninitialized error“ and „Not Ready“ Status in host preparation

Knowledgebase Nr: 2149433

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware NSX for vSphere 6.2.x

Link zum Artikel: 2149433

Beschreibung:
Hosts show the status as „Not Ready“ while all NSX services are running.Running the command esxcli software vib list | grep -E ‚esx-vdpi|esx-vxlan|esx-vsip on the host shows the correct version of NSX VIBs installed.Clicking on the resolve fails, you may see error similar to:Unable to access agent offline bundle at https://NSXIP/bin/vdn/vibs[object 6] Cause: XXX uninitialized.
… Für weitere Details den Link zum Artikel anklicken

Titel: „The backing EAM agency for this deployment could not be found“ error after restore from backup

Knowledgebase Nr: 2148362

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x

Link zum Artikel: 2148362

Beschreibung:
In the NSX Manager, you may see high priority alerts similar to:Nov 8 04:35:00 NSXMGR 2016-11-08 04:35:00.422 GMT+00:00 INFO TaskFrameworkExecutor-18 SystemEventDaoImpl:133 – [SystemEvent] Time:’Tue Nov 08 04:35:00.410 GMT+00:00 2016′, Severity:’High‘, Event Source:’Security Fabric‘, Code:’250024′, Event Message:’The backing EAM agency for this deployment could not be found. It is possible that the VC services may still be initializing. Please try to resolve the alarm to check existence of…
… Für weitere Details den Link zum Artikel anklicken

Titel: Error message when applying a license key to a host running ESXi 6.0

Knowledgebase Nr: 2149439

Kategorie: Licensing, Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2149439

Beschreibung:
The error message is received when applying a license key to a host running ESXi 6.0.“There are more cores (x) on this host than there are valid specified licenses for (x), please specify another license”
… Für weitere Details den Link zum Artikel anklicken

Titel: Allowing a client to run a backup job for more than 24 hours in VMware vSphere Data Protection

Knowledgebase Nr: 2109662

Kategorie: Informational

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2109662

Beschreibung:
The backup job fails to complete in 24 hours The MC Server cancels the job when the backup window expires, which results in a partial backup In the /space/avamarclient/var-proxy-x/job_name.log file, you see entries similar to:<YYYY-MM-DD>T<TIME>.601-8:00 avvcbimage Info <9772>: Starting graceful (staged) termination, MCS cancel (wrap-up stage)<YYYY-MM-DD>T<TIME>.775-8:00 avvcbimage Info <16022>: Cancel detected(externally cancelled by Administrator),…
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading vCenter Server from version 5.5 to 6.0 update 2a fails

Knowledgebase Nr: 2148371

Aktualisiert: 10.03.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2148371

Beschreibung:
Starting VMware Identity Management Services fails when upgrading vCenter Server 5.5 to vCenter Server 6.0 Update 2a. Installing or upgrading to vCenter Server 6.0 update 2a fails with the error:Encountered an internal error. These errors are displayed at the end of the backtrace: „WindowsError: [Error 2] The system cannot find the file specified „WindowsError: [Error 183] Cannot create a file when that file already exists In the /var/log/firstboot/vmidentity-firstboot.py_xxxxx_stdout.log…
… Für weitere Details den Link zum Artikel anklicken

Titel: Determining replication agreements and status with the Platform Services Controller 6.X

Knowledgebase Nr: 2127057

Kategorie: Informational

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2127057

Beschreibung:
This article provides information on using the vdcrepadmin command-line interface (CLI) for reviewing the existing vSphere domain, Platform Services Controllers (PSC) that make up your vSphere domain as well as checking the replication agreements configured and replication status within your environment. Although the utility can be used for other operations, at this time, only what is documented must be executed by technical support staff and customers. The vdcrepadmin CLI is located in these…
… Für weitere Details den Link zum Artikel anklicken

Titel: Supported versions of Windows 10 on Horizon View

Knowledgebase Nr: 2149393

Kategorie: Informational

Aktualisiert: 10.03.2017

Für Produkte: VMware Horizon 6 version 6.2.x, VMware Horizon 7 version 7.0.x, VMware Horizon 7 version 7.1.x

Link zum Artikel: 2149393

Beschreibung:
This article is designed to track the supported versions of Windows 10 along with the releases of VMware View.
… Für weitere Details den Link zum Artikel anklicken

Titel: „Server has a weak ephemeral Diffie-Hellman public key“ error while accessing vRO

Knowledgebase Nr: 2131619

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware vCenter Orchestrator 5.5.x, VMware vRealize Orchestrator 6.0.x

Link zum Artikel: 2131619

Beschreibung:
When accessing VMware vRealize Orchestrator with a Web browser, you see the error: Server has a weak ephemeral Diffie-Hellman public key The Web browser is a recent version of Firefox or Chrome.In Internet Explorer, you see the error:Page Cannot be Displayed error
… Für weitere Details den Link zum Artikel anklicken

Titel: „Current node is not ACTIVE“ error when logging in to vRO 7.0

Knowledgebase Nr: 2144621

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Für Produkte: VMware vRealize Orchestrator 7.0.x

Link zum Artikel: 2144621

Beschreibung:
When the Authentication Provider in vRealize Orchestrator (vRO) 7.0.x is configured to use the vSphere Authentication Mode to connect the vSphere 6.0.x PSC, you experience these symptoms: Unable to log in to vRealize Orchestrator. You see the error:Current node is not ACTIVE. In the server.log in the vRO server, you see entries similar to:[serverHealthMonitorScheduler-1] WARN {} [RetriableOperation] Exception handled during retry operation with message: 400 Bad Request In the…
… Für weitere Details den Link zum Artikel anklicken

Titel: Connecting to SRM using an domain account with sufficient privileges fails

Knowledgebase Nr: 2147590

Aktualisiert: 10.03.2017

Für Produkte: VMware Site Recovery Manager 6.1.x

Link zum Artikel: 2147590

Beschreibung:
Connecting to VMware SRM using an domain account with sufficient privileges results in errors on SRM site objects, such as:Cannot complete login due to an incorrect user name or password.Cause:Cannot retrieve SRM properties Connecting with an SSO-based account works without errors or connectivity issues.
… Für weitere Details den Link zum Artikel anklicken

Titel: Platform Services Controller 6.0 deployment takes several hours

Knowledgebase Nr: 2147428

Aktualisiert: 10.03.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2147428

Beschreibung:
Platform Services Controller deployment takes several hours to deploy.The deployment fails with the error:Firstboot script execution errorCould not configure the Service Control Agent administration groupUsing the top command, the Platform Services Controller memory usage is very high during deployment and while using the cmsso-util script to move-services.The vmdir log file contains multiple Delete Entry entries for for vsan.health similar to:2016-10-04T22:55:40.215836+00:00 info vmdird…
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading to NSX for vSphere 6.3.0 fails when using Hardware Gateway

Knowledgebase Nr: 2148511

Kategorie: Informational

Aktualisiert: 10.03.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2148511

Beschreibung:
When upgrading to VMware NSX for vSphere 6.3.0 with a HW VTEP in the environment, you may experience this symptom: Upgrade is halted You see the error similar to:Cannot continue upgrade due to errors: „(1)“ Hardware Gateway(s)found in the system. Unable to proceed with the upgrade. Please contact VMWare Support to continue. Please correct before proceeding.
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host fails with intermittent NMI PSOD on HP ProLiant Gen8 servers

Knowledgebase Nr: 2149043

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2149043

Beschreibung:
ESXi hosts running 5.5 p10, 6.0 p04, 6.0 U3, or 6.5 may fail with a purple diagnostic screen caused by non-maskable-interrupts (NMI) on HPE ProLiant Gen8 Servers.
… Für weitere Details den Link zum Artikel anklicken

Titel: Adding new compute node fails on VIO

Knowledgebase Nr: 2149270

Aktualisiert: 10.03.2017

Für Produkte: VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2149270

Beschreibung:
During deployment of VIO 3.0, the process fails with the error: „Failed to create the virtual machine for cluster alphanjMitaka3 while deploying“ in VCSA web client 6.0. In the OMS logs, you see entries similar to:[2017-02-28T21:52:51.612+0000] INFO SimpleAsyncTaskExecutor-9| com.vmware.openstack.service.impl.ClusteringService: ClusteringService, start to clone template.[2017-02-28T21:52:51.612+0000] INFO SimpleAsyncTaskExecutor-9|…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to take snapshots

Knowledgebase Nr: 2148299

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

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

Link zum Artikel: 2148299

Beschreibung:
Unable to take snapshots manually and through backup Taking snapshot with or without quiesce or memory state will fail with the following error:An error occurred while taking a snapshot: msg.fileio.generic.|An error occurred while saving the snapshot: msg.fileio.generic. In the vmware.log file, you see entries similar to: | vmx| I120: VigorTransportProcessClientPayload: opID=254F67FE-00000087-ce-3b-ab7a seq=6800308: Receiving Snapshot.Take request. | vmx| I120: SnapshotVMX_TakeSnapshot…
… Für weitere Details den Link zum Artikel anklicken

Titel: Agent machine gets STOP error or stops responding when you open a local file shared with CDR

Knowledgebase Nr: 2149417

Kategorie: Troubleshooting

Aktualisiert: 10.03.2017

Link zum Artikel: 2149417

Beschreibung:
In certain circumstances, opening a local file with File > Open in a remote desktop or remote application causes the guest operating system on the Horizon Agent machine to encounter a STOP error (blue screen) or to stop responding (hang) when client drive redirection (CDR) is used.For example, if you use client drive redirection to share a local folder with a Windows 10 remote desktop, launch Notepad in the remote desktop, and then use File > Open to open a file in the local folder, a…
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-03-11T09:08:37+00:00März 11th, 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