Verify WMI for MS Cluster issues

In a cluster environment, WMI is often used to share information and notification within the nodes. Some of the cluster issues/error due to the WMI is as listed below:

“RPC Server Unavailable” error.
Access is Denied.
The computer ‘Node1’ could not be reached.
Failed to retrieve the maximum number of nodes for ‘{0}’.
The computer does not have the Failover Clustering feature installed. Use Server Manager to install the feature on this computer.
Note: first confirm you have installed the Failover Clustering feature on this node

In above case we need to make sure that the WMI is working fine and this can be confirmed following the steps listed below:
Make sure that the WMI service is up and firewall settings.

1. Launch CMD
2. Type “WBEMTest” (without quotes”).
3. The Windows Management Instrumentation Tester will launch
4. Select Connect
5. Namespace: Root\MSCluster
6. Select Connect and if you see more options available, it means you are connected and WMI is working
7. Click on Query and enter SELECT * from MSCluster_Resource to confirm (any error shown represents WMI issue).

Thanks,
WinteAdmin

IBM DB2 error SQL5005C during server startup.

Upon windows server hosting DB2 reboot you will get an error message “SQL5005C”. This actually refers to “The operation failed because the database manager failed to access either the database manager configuration file or the database configuration file.” This is due to DB2 database utility (such as db2start, db2icrt, restore, or many others) requires that the database manager write to or read from either the database manager configuration file or the database configuration file, and the database manager was unable to access the configuration file.

This is fixed by performing the below steps:

1. Log in to the machine as system administrator.
2. Remove the db2systray by performing the following steps:
a. Windows Start –> All Programs –> IBM DB2 –> Command Line Tools –> Command Window Administrator.
b. db2systray -clean
3. Log off and log in to the machine.

Thanks,
WintelAdmin

Server (HP) not reachable on network “Port was disabled because a pause flood was detected” .

Host was not reachable on network. When checked on ILO server is up and running. When I try to ping the server its unresponsive.Host is a blade server, hence suspected an issue with the network module. Therefore, connected virtual connect. Found one of the virtual connect module was degraded. When analysed the HP Virtual connect found an error message stating “Port was disabled because a pause flood was detected”

Further to this when validated the server port assigned to the bay1/bay2 found the status “Not Linked/Pause Flood Detected”. It confirms the issue was caused by pause Flood. In some cases, a flex-10 port can enter into disabled state due to the triggering of “pause-flood”, or network-loop. You can confirm the same port status using Virtual Connect Manager CLI. Connect to Virtual connect using SSH and Execute the below command:

Show port-protect

This would show the blade server that’s in impact. To fix the issue, please execute the below command:

reset port-protect

Verify the port status again using the command “show port-protect” and ensure no port’s protect types are reported as “Pause Flood”.
Another action plan would be to update the Drivers and Firmwares.

You can also disable is using the command listed below
set port-protect pauseFlood=Disabled

Thanks,
WintelAdmin

VMware Virtual Machine Reporting from VSphere

VMware PowerCLI is a powerful utility to generate virtual machine information and status. This is very cool and handy tool. I use to generate VMTools status, Datacenter and ESX host name information.

Command to connect vCenter:

Connect-VIServer vcenter1, vcenter2, vcenter

Initialize VMTools Version:
New-VIProperty -Name ToolsVersion -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Config.tools.ToolsVersion’ -Force

Initialize VMTools Status:
New-VIProperty -Name ToolsVersionStatus -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Guest.ToolsVersionStatus’ -Force

Verify VMTools status on all virtual machines and export the output to excel:
Get-VM | Select Name, ToolsVersion, ToolsVersionStatus | Export-Csv -NoTypeInformation -UseCulture -Path C:\Temp\VMToolsInfo.csv

Export VM name, cluster and ESX Host:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}}, @{N=”ESX Host”;E={Get-VMHost -VM $_}} | Export-Csv -NoTypeInformation C:\temp\VM_CLuster_Host-.csv

Export VM name and Cluster name:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}} | Export-Csv -NoTypeInformation C:\temp\test-VM_CLuster.csv

Thanks,
WintelAdmin.

Error: Could not access VBscript run time for custom action.

Recently got an update from the application team that they are unable to install and software. When executing the setup file they are getting an error pop-up window stating “Could not access VBscript run time for custom action.”. This issue was fixed using below steps:

1. Open Registry Editor” and locate the below key.

HKEY_Local_Machine\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

2. Expand {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key, locate InprocServer32 and click on it.
In the right column you should see two values.

3. Right-click InprocServer32 > Permissions > Advanced > Permissions > highlight Administrators, choose Edit > and in the Permissions check box next to Full Control; Save all changes;

4. Then in the right column or Registry Editor right-click (Default) > Modify, and insert the correct path in Value Data:

C:/Windows/system32/vbscript.dll

5. If you have 64-bit Windows repeat steps 3 – 5 for next registry keys:

HKEY_Local_Machine\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

HKEY_Local_Machine\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8

6. After that close Registry Editor.

After the above changes when we tried executing the same setup it went success.

Thanks,
WintelAdmin

VMware Tools is no more depended on vSphere/Esxi release.

VMware tools 10.0.0 is now no more dependent on vSphere release/Esxi builds. I think this is the first time when VMware released VMware Tools separately. As per release note its backward compatible, compatible with Esxi 5.0 and also compatible with Workstation 12.0 and VMware Fusion 8.0. It will allow to get the latest new features and enhancements made to the VMware tools faster to the customers.

You can download and install the latest version of VMware Tools from Here.

Thanks,
WintelAdmin

Enable Time Synchronization Between Windows (VM Guest) and ESX (Host).

This is in continuation to my previous post RDP Connection on a virtual server

As discussed earlier there was an issue with the AD authentication and connectivity. It was all because of the different time zone set on an ESX host and the guest operating system. Changing time on DC was not recommended by the AD Team as the impact was unknown and similarly we have no clue on the impact due to time change on ESX cluster. Hence, I decided to manually do the time sync between the ESX host and Guest machine.

Time sync status was validation using the command:
VMwareToolboxCmd.exe timesync status

Enter the command to enable or disable periodic time synchronization.
VMwareToolboxCmd.exe timesync Enable/Disable

We executed below command to fix the issue
VMwareToolboxCmd.exe timesync Enable

Note: VMTools installation directory on Windows is C:\Program Files\VMware\VMware Tools.

Thanks,
WintelAdmin

RDP Error – The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

Unable to connect to the Remote Desktop. Server operating system is Windows Server 2012 Standard R2. When we try to RDP, we get the below error message:

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

There was two server with same configuration and setting but one of connecting to RDP with AD authentication whereas the other was not working. One was physical and the other was virtual hosted on an ESX host.
RDP on physical was good and the issue was with the virtual host. It was confirmed that the issue was due to time latency.
Therefore, this issue was due to the time difference between the virtual machine and the NTP server set on an ESX host.
This issue was later fixed by synchronizing the server time with the ESX host.

Note:
If you do not wish to have auto sync, disable the Windows Time service or block the outbound port 123 on your local firewall.

Thanks,
WintelAdmin

Windows could not finish configuring the system.

Recently, I was installing Windows 2008 R2 on a HP ProLiant DL380 Gen9 server. Found that the server was throwing an error message stating “Windows could not finish configuring the system.”. When you click on “OK”, servers gets automatic reboot and shows again the same error.

When searched on google, I found that this error message occurs with Windows Server 2008 R2 operating systems if the system contains a registry key that is larger than 8 kilobytes (KB). A Hotfix for this problem is available from Microsoft

KB981542

In my case it was during a clean install of Windows OS, hence it was fixed following the steps listed below:

When you find the error message stating that the “Windows could not finish configuring the system” appears on your screen:

1. Hold down the SHIFT key and press F10 (SHIFT + F10) to open command prompt.
2. At command prompt type: cd oobe (& press Enter).
3. Then type: msoobe (& press Enter).
4. Finally Restart your computer.

You will see your machine back with CTRL+ALT+DEL screen.

Thanks,
WintelAdmin