HPSUM Node Baseline fails with a Inventory Error on HPE Servers

This is a quick little tip for you guys if you encounter this issue while running the launch_hpsum.bat file from a Windows server and you are trying to update the firmware or the drivers for the hardware components.

When you try and run the node inventory you are presented with the below message. This is quite simple to get around, all you have to do is right click the launch_hpsum.bat file and run as administrator.

 -Alstar

-Alstar

How To Delete Or Cancel Hung Print Jobs

Today, one of my user had clogged my entire print queue on a server giving a 4GB print job!! I mean who does that??!. This stopped all my other print jobs from starting and all the users had started complaining.

I tried deleting his job from the print queue manager on the server and I got an Access Denied message, so not sure what was going on. So I finally performed the below steps to blow that 4GB print job from the queue!

  • Stop the Print Spooler service

  • Go to the folder —> C:\Windows\System32\Spool\Printers

  • In that folder look for all the .SPL files, which are the spool files and locate the one with the massive size that you want to delete and blow it away.

  • Start the Print Spooler service back on

  • After that if you see the print queue on the server, you should not see that job again and chances are that all your other print jobs should start to print.

-Alstar

Unable to install the .NET Framework security update KB4457918 on Windows Server 2008 R2

This month my SCCM team had released a .NET framework update for 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 7 and Server 2008 systems. I was trying to install that on one of my Windows 2008 R2 server system and it kept failing.

After looking at the WindowsUdpate.log file under C:\Windows, I spotted quite a few error codes which ranged from:

  • WARNING: Command line install completed. Return code = 0x0000066a, Result = Failed, Reboot required = false

  • WARNING: Exit code = 0x8024200B

  • WARNING: Exit code = 0x00000000; Call error code = 0x80240022

  • Installation Failure: Windows failed to install the following update with error 0x80070643

The way I fixed my particular issue was I repaired my Microsoft .NET Framework 4.5.2 listed under the Program and Features menu.

  • Start —> Run —> Appwiz.cpl

  • Locate Microsoft .Net Framework 4 Client Profile and right click it

  • Select Uninstall/Change

  • Select the repair option and click on NEXT

  • After the installation has been repaired, it will ask for a reboot

  • Reboot the server

  • Install the latest update again and hopefully it should install just fine this time.

If the above procedure does not work, then you will have to look at alternatives.

-Alstar.

The mount point disk volume is not a clustered resource.To continue, add the resource to the cluster, or remove the mount point to cluster the shared disk

I had a Windows 2012 cluster on which my SQL team was trying to create a new role and install SQL 2016 on it. When running through the SQL installation they kept getting an error message and the base disk which acts as a mount point for the rest of the disks wasn't being detected and an error would show up.

The way we install SQL is,  we have a base disk which acts as a mount point, which is generally 1 Gb in size. Then we have different disks namely Data,Backup,Logs and TempDB which are mounted inside this base disk as mount points and have varying sizes depending upon the requirement. The actual error was:

"The mount point disk volume '\\?\Volume{79d2349d-08dc-472a-ba6a-a73117f88bd2}\' mounted at 'J:\$RECYCLE.BIN\S-1-5-21-1831736574-1690769945-617630493-456775\$R5498E5\' is not a clustered resource.To continue, add the resource to the cluster, or remove the mount point to cluster the shared disk."

To fix this I followed the below steps:

  • Remove the disks from the resource group
  • Remove the disks from the cluster
  • Bring the disks online in computer management
  • Format the Base disk that the mount points attach to
  • Recreate the mount points inside the Base disk
  • Re-add the disks to the cluster
  • Delete the Role and re-create it
  • Re-add the disks to the resource group
  • Re-create the dependencies from the mount point disks to the Base disk
  • Start SQL installation

10fb does not support flow control autoneg - Vmware Esx 6.5

I had recently used the HPE custom ISO image downloaded from the vmware website for my HPE Gen 9 server. I wanted to install Vmware Esxi 6.5 on it. Everything went as expected and I was able to get that installed and running. This server had a dual port 10Gb network adapter added on as a card from Intel as you see below.

1.JPG

After a while, I started getting loads of messages in my VmKernel.log file under /var/log/vmkernel.log and the message read as

10fb does not support flow control autoneg

So after looking around, I figured this might be an issue with my native driver for this card which was of the version 1.4.1.

2.JPG

I then proceeded to download a different version of the driver for this card to see if that fixes the problem and I found a version ixgbe version 4.5.3 on the Vmware website and I downloaded that. Click on this LINK.

This is compatible with Esxi 6.5, so don't worry. After this was downloaded I copied it to a datastore locally on the host and then SSH'ed using the root password and installed the VIB using the below command.

esxcli software vib install -v {Complate path to the VIBFILE}

Reboot the host

After the host comes back up, disable the old driver and enable the new one

esxcli system module set -e=true -m=ixgbe (This enables the new driver)
esxcli system module set -e=false -m=ixgben (This disables the old driver)

After this has been completed, you can reboot the host and then check the vmkernel log again using the below command to see if you are getting the alert again, and hopefully you should not!

tail /var/log/vmkernel.log -f

You can check the driver on your vmnic adapter as well by using                                               esxcli network nic get -n vmnic6 and you should get the below output with the updated driver version.

3.JPG

-Ali Hassan