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

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.

 

 

2 thoughts on “Potential version mismatch between WAP and SPF, please verify both component’s versions and if they’re compatible”

  1. Hi Chris, sorry for the late reply. I guess you have already solved the problem?
    WAP, SPF and VMM should always be on the same version. Whenever you update one of the components with an Update Rollup, you have to update all of them or you will run into issues as above.

  2. Hi, Marcus, one of my partner run into the same problem as you did, could you explain more details about which version of SPF, SCVMM & System Center 2016, and WAP to solve the problem, please?

    their environment:
    WAP: v3.37.8196.0, with Update Rollup 11,
    System Center 2016 RTM, v7.3.345
    SPF: v7.3.319.0

    So, as my understanding, what you mean is to keep the SPF and System Center VMM with the same v7.3.319.0, or v7.3.345, will solve the problem?

    Thanks.

Leave a Reply