How to read vmware logs in windows

The following instructions are meant for IT professionals. Also see the Upgrade error codes section in this guide to familiarize yourself with result codes and extend codes. Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process. Based on the extend code portion of the error code, determine the type and location of a log files to investigate.

Using the result code portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below. When you have located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed just prior to generating the result code.

For example, assume that the error code for an error is 0xB - 0xD. Searching for "B" reveals the following content from the setuperr. Some lines in the text below are shortened to enhance readability. The date and time at the start of each line ex: is shortened to minutes and seconds, and the certificate file name which is a long text string is shortened to just "CN. This file is a local system certificate and can be safely deleted. Searching the setupact. This confirms our suspicion that this file is the cause of the upgrade failure:.

If you just need to take a quick look at a log file because you know what you are looking for, there is a quicker way. After your log download has finished, you can upload those logs right to VMware through the vSphere client. Then you can browse to the logs you downloaded and click upload. If you just need to quickly look at a log file, you can ssh directly to your VCSA and take a look at it.

Navigate to the Access tab in the left pane, and click Edit next to access settings. From here you can toggle the settings on and off. You can do the same thing if you need to look at logs on an ESXi host, ssh and browse to the directory. You can also view the logs on an ESXi host by connecting to the host directly with the vSphere Client. While you may not feel like reading vCenter server logs for fun, it is a good idea to at least know how to access them in case you ever have an issue with your environment.

VMware makes this easy to do by being able to access them and upload them from the vSphere Client. If you know what you are looking for and need to quickly take a look at something, you may just want to ssh to the VCSA directly and take a look at them.

We are going to take a look at two different ways to take a look at your vCenter logs: Export the vCenter logs to your computer Look at the logs on the VCSA directly We will also briefly cover the main log file to look at, and how to send your logs to VMware support. Once connected you can view logs in a variety of ways such as:. Having established a connection to my vCenter server, running Get-LogType displays the vCenter logs that are available to view:.

This will show everything in the vmkernel log, however if we are looking for something in particular we can filter the log using something like:. This website uses cookies to improve your experience.

We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More. How to Use the Docker Exec Command.