MSI Error 25543 when installing SPF Update Rollup

When trying to install an Update Rollup for SPF through Windows Update you may run into a Failed installation. And running the update manually gives a MSI Error 25543 where you have to click the Ok button like 10 times before it abort.

I’ve solved that at three different occasions by just stopping the IIS “Internet Information Services” and then installing the update manually.

Remember to start IIS after the update is installed and verify the bindings for SPF is still correct (there has been occasions where there have been duplicate bindings).

 

Potential version mismatch between WAP and SPF, please verify both component’s versions and if they’re compatible


Notice: Undefined index: host in C:\home\site\wwwroot\wp-includes\media.php on line 1372

I had a customer today who were getting errors when trying to create Virtual Machines in Windows Azure Pack (WAP).

WAP Tenant Log file
WAP Tenant Log file

Looking in the logfile on the Tenant server (Tenant Admin Log) showed that there were quite a lot of Error Events when a user is trying to create a server.

Some operations worked, like creating a virtual network but not deploying a virtual machine.

The interesting part here is the reference to; “Potential version mismatch between WAP and SPF, please verify both component’s versions and if they’re compatible”

Full Eventlog details, might help with search indexes.

 

I had a look at the SPF Server, and immediately noticed that the version of SPF was System Center 2016 RTM with no updates installed.

Updating SPF to the same version as Virtual Machine Manager (VMM) 2016 and Windows Azure Pack solved the problem.