Collecting diagnostic information for the vSphere 5.5 Microsoft Windows Installer(s)

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

VMware Technical Support routinely requests diagnostic information from you when a support request is handled. This diagnostic information contains product specific logs and configuration files from the host on which the product is run. The information is gathered using a specific script or tool for each product, but during installation collecting data may need to be done manually.

Note: This article provides procedures for obtaining diagnostic information for the VMware vSphere 5.5 Simple and Custom Installers on a Windows platform. For information about collecting logs for the vCenter Server Appliance 5.5, see Collecting diagnostic information for VMware vCenter Server (1011641).

The diagnostic information collected (bundle) can then be uploaded to VMware Technical Support. To uniquely identify your information, use the Support Request (SR) number you received when you opened your Support Request.

• Instructions to open a support request can be found online at Filing a Support Request in Customer Connect (2006985).
• Instructions to upload your support files can be found in the article Uploading diagnostic information to VMware (1008525).
• Instructions to obtain diagnostic information for other VMware products can be found in the article Collecting diagnostic information for VMware products (1008524).

Environment

VMware vCenter Server 5.5.x
VMware vCenter Server 5.1.x
VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 5.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 6.0.x
VMware vCenter Server 4.0.x
VMware vCenter Server 6.5.x
VMware vSphere Web Client 5.5.x

Resolution

In order to collect the diagnostic information about an install or upgrade attempt that was made on a Microsoft Windows instance:

1. Click Start, then click Run.
2. Type in %temp% and press the Enter key.
3. Select these files:
   
   Note: Depending on when the install or upgrade failed, not all files may be present.
    
   • Files created by multiple VMware installers:
     • vminst.log
     • vminst.err
     • vm_ssoreg.log
       
       Note: The preceeding logs contain events registering the Web Client, Inventory, and vCenter Service instances with the Single Sign-On Service instance. The vm_ssoreg.log file is not created when installing Single Sign-On.
        
   • Files created during the vCenter Single Sign-On Service installation or upgrade process:
     • vim-jre-msi.log
     • vim-kfw-msi.log
     • vim-openssl-msi.log
     • vim-python-msi.log
     • vim-tcserver-msi.log
     • vim-sso-msi.log
     • exported_sso.properties (Only present on a vSphere 5.1 to 5.5 Upgrade)
        
   • Files created during the vSphere Web Client Service installation or upgrade process:
     • vim-ngc-msi.log
        
   • Files created during the vCenter Inventory Service installation or upgrade process:
     • vim-qs-msi.log
     • ds.log
     • ds-perf.log
        
   • The vCenter Server service installer log files:
     • vim-vcs-msi.log
     • vim-sps-msi.log
     • vmware_orchestrator_installer_output.txt
     • vim-vmosql.log
     • vimtool.log
     • SqlSetup.log
     • jointool.log
        
4. Compress the files into a zip file.
5. Relocate the file in a known location such as the desktop.
6. Click Start, then click Run...
7. Type in %ProgramData%\VMware\cis\logs\ and press the Enter key.
8. Compress the logs folder.

Additional Information

For assistance with uploading the diagnostic bundle, see Uploading diagnostic information to VMware (1008525).
Files that contain the term msi conform to the standard Microsoft Installer log format. For assistance interpreting the contents of these logs, see Microsoft's An Annotated Windows Installer Log File article and Wilogutil tool.



Collecting diagnostic information for VMware vCenter Server 4.x, 5.x and 6.x
How to file a Support Request in Customer Connect
VMware vCenter Server 4.x、5.x、および 6.x の診断情報の収集