Azure Stack PoC deployment stops at step 60.140.149 on HP Server

Hi everyone,

maybe you encounter the following issue already.

When deploying the Azure Stack PoC RTM on a HPE Server, the deployment stop without any error or something at step 60.140.149.

After one week troubleshooting together with the customer and no solution, my dear coworker Alexander Ortha gave me an hint what the issue could be.

He previously hab the same issue with an HPE and he needed to update the Firmware and BIOS of the system. Afterwards the installation went through smoothly.

So I tried and he was right. So just try it yourself and update the firmware of your systems to lastest version.

Cheers,

Flo

Virtual Machine Converter – Cannot Convert VMware VM – Disk configuration

Today I had an issue with virtual machine converter during migration of a VM from VMware to Hyper-V. The screenshot below shows the issue.

Untitled

The issue shows an configuration missmatch which stopped the convert of the VM.

The solution of the issue is pretty easy. You need to check and change the virtual machine configuration in VMware vCenter.

First you need to check the SCSI Bus logic. There you need to configure LSI Logic.

Second and more likely the reason for the issue is that one or more of your disks are configured as independed. Just uncheck the box and your fine. ūüôā

Untitled

 

Cluster Manager, Server Manager & Hyper-V Console not starting

This week I had a very strange issue with a Hyper-V Cluster managed by Virtual Machine Manager.

Completely randomly different cluster nodes failed and I weren’t able to start failover cluster manager on one of the cluster nodes. ¬†On the infected node it self, I wasn’t able to open the hyper-v manager or server manager.

After a lot of research I found a solution from the windows server core team which pointed me to the solution.

Unable to launch Cluster Failover Manager on any node of a 2012/2012R2 Cluster

When Failover Cluster Manager is opened to manage a Cluster, it will contact all the nodes and retrieve Cluster configuration information using WMI calls. If any one of the nodes in the Cluster does not have the cluster namespace “root\mscluster” in WMI, Failover Cluster Manager will fail and give one of the below errors:

clip_image002

Or,

Unfortunately, it does not give any indication of which node is missing the WMI namespace.  One of the ways you can check to see which one has it missing is to run the below command on each node of the Cluster.

It can be a bit tedious and time consuming if you have quite a few nodes, say like 64 of them.  The below script can be run on one of the nodes that will connect to all the other nodes and check to see if the namespace is present.  If it is, it will succeed.  If the namespace does not exist, it will fail.

—————–

 
—————–

In the below example, you can see that one of the nodes failed.

To correct the problem, you would need to run the below from an administrative command prompt on the “failed” node(s).

cd c:\windows\system32\wbem
mofcomp.exe cluswmi.mof

Once the Cluster WMI has been added back, you can successfully open Failover Cluster Management.  There is no restart of the machine or the Cluster Service needed.

Quote: Microsoft Ask the Core Team Blog

In my case I wasn’t able to fix it so easy because the server vendor implemented the WMI Provider directly in his BMC via Agent (for the interested ones Fujitsu). during the process of recompiling the WMI for the Cluster the whole Server Network interfaces and BMC fail.

so my fix:

  1. shutdown the server
  2. make it powerless
  3. start it
  4. check cluster (everything fine)
  5. uninstall the (fucking) agent

Since than it worked.

Updating permission setting for folder ‘ ‘ failed when I install a high available SQL Instance on cluster shared volume

Hey everybody,

the following blog is more to remind my self on a mistake I do very often. ūüėČ

When I install a SQL Failover Cluster and a High Available Instance on a cluster shared volume, I get the error “Updating permission setting for folder ‘ ‘ failed”.

IMG-20150725-WA0002

There are different posts to solve the issue more or less complex.

SQL Installation Error updating permisson setting for folder

SQL Server 2008 installation will fail if the setup account does not have certain user rights

Permission error installing Failover Cluster instance

In my case the solution was pretty easy. I mostly forget to create a sub directory for SQL Databases and Files on the cluster shared volume. So as example:

False:

C.\ClusterStorage\SQL-Backup\ <- will give you the error

Right:

C:\ClusterStorage\SQL-Backup\Files\ <- will work fine

So easy solution for the error, create a subfolder and install use that path during installation.