6 Replies Latest reply on Sep 17, 2014 5:39 AM by sz-a

    WSUS Version mismatch 3.2.x <--> 3.2.y ?

    sz-a

      What does this error mean, if i try to publish 3rd Party updates to another wsus-server?:

       

      "The Server has the required certificates for Publishing. There is a version mismatch between the WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.226"

       

      I have 3 WSUS. 2 of them (one of them PM) are Server 2008 R2 and are showing Client and Server api version 3.2.7600.274. The 3rd with the Error is a Server 2003 R2. The WSUS console on the 2003r2 Shows version 3.2.7600.274 for this Server, but in the programs/software list (programs and Features in Server 2008 r2) the KB2720211 is listed as removed (and this isn't removable).

       

      1. I thought a mismatch could only occur between main Versions like WSUS3 / WSUS6 and so on?

      2. How can I update the Client API on WSUS? Do it have to selfupdate? And how can I force this with Patchmanager?

       

      Thanks

        • Re: WSUS Version mismatch 3.2.x <--> 3.2.y ?
          Lawrence Garvin

          "There is a version mismatch between the WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.226"

           

          It means that you have applied KB2938066 to your WSUS server, but you have not applied it to the Patch Manager server.

          The Patch Manager server installed KB2734608, by default, but not KB2938066 (which did not exist at the time of release of PMv2.0).

           

          1. I thought a mismatch could only occur between main Versions like WSUS3 / WSUS6 and so on?

          No, Local Publishing requires that the build numbers of all of the components of the WSUS infrastructure are identical, e.g.

          • KB2720211-only installed everywhere
          • KB2734608-only installed everywhere (which is the presumed scenario of Patch Manager)
          • KB2938066 installed everywhere

           

          2. How can I update the Client API on WSUS?

           

          The "client" in this scenario refers to the machine running the "console" that is attempting to publish the update ... which is the Patch Manager Application Server

            • Re: WSUS Version mismatch 3.2.x <--> 3.2.y ?
              sz-a

              This I don't understand, because all WSUS should have the same versions. I should describe much clearer:

               

              On publishing i get 2 messages:

              1. from the Target WSUS server / "Publishing WSUS Server": "There is a version mismatch between the WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.226"
              2. from the Source WSUS and PM-Server: "The WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.274 are a match"

               

              Because this i asked, how to update the (only) WSUS Client API on the Target WSUS. Or does this mean that the KB on the Target Server isn't installed correctly

               

              I tried again and get:

              - if publishing with enabling "Verify WSUS version compatibility and required signing ..." --> Error messages mentioned above

              - if publishing with disabled "Verify WSUS version compatibility and required signing ..." --> Failure: Message: Failed to publish <packagename>. CreateDirectory failed

                • Re: WSUS Version mismatch 3.2.x <--> 3.2.y ?
                  Lawrence Garvin
                  The WSUS console on the 2003r2 Shows version 3.2.7600.274 for this Server, but in the programs/software list (programs and Features in Server 2008 r2) the KB2720211 is listed as removed (and this isn't removable).

                  Okay.. first note. If the WSUS server is 3.2.7600.274, then it no longer has KB2720211 (v3.2.7600.251) installed, nor does it have KB2734608 (v3.2.7600.256) installed, nor does it have KB2828185 (v3.2.7600.261) installed

                  It has KB2938066 installed, which is v3.2.7600.274.


                  On publishing i get 2 messages:

                  1. from the Target WSUS server / "Publishing WSUS Server": "There is a version mismatch between the WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.226"
                  2. from the Source WSUS and PM-Server: "The WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.274 are a match"

                  Can you explain to me exactly what you're running where? You can only publish to *one* server, and you cannot "publish" "from the Target server", so I'm not really understanding your message in statement #1. You can only publish to the Upstream WSUS Server from the PM Server, so it seems to me that Statement #2 is the only one that matters. By default, a Patch Manager server installs WSUS v3.2.7600.256. The only way this could get to v3.2.7600.274 is if you installed KB2938066 on the Patch Manager server. It would seem, by Statement #2, that you have installed KB2938066 on the Patch Manager server.




                    • Re: WSUS Version mismatch 3.2.x <--> 3.2.y ?
                      sz-a
                      The WSUS console on the 2003r2 Shows version 3.2.7600.274 for this Server, but in the programs/software list (programs and Features in Server 2008 r2) the KB2720211 is listed as removed (and this isn't removable).

                      Okay.. first note. If the WSUS server is 3.2.7600.274, then it no longer has KB2720211 (v3.2.7600.251) installed, nor does it have KB2734608 (v3.2.7600.256) installed, nor does it have KB2828185 (v3.2.7600.261) installed

                      It has KB2938066 installed, which is v3.2.7600.274.

                      But the problem is that the KB2720211 is listed (with the description "This Update has been removed." in german)

                      Hotfix KB2720211 removed on VSRVB2002.jpg

                       

                      On publishing i get 2 messages:

                      1. from the Target WSUS server / "Publishing WSUS Server": "There is a version mismatch between the WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.226"
                      2. from the Source WSUS and PM-Server: "The WSUS Server API version: 3.2.7600.274 and the WSUS Client API version: 3.2.7600.274 are a match"

                      Can you explain to me exactly what you're running where? You can only publish to *one* server, and you cannot "publish" "from the Target server", so I'm not really understanding your message in statement #1. You can only publish to the Upstream WSUS Server from the PM Server, so it seems to me that Statement #2 is the only one that matters. By default, a Patch Manager server installs WSUS v3.2.7600.256. The only way this could get to v3.2.7600.274 is if you installed KB2938066 on the Patch Manager server. It would seem, by Statement #2, that you have installed KB2938066 on the Patch Manager server.

                       

                      Not "from". I publish "to" and get the error message from PM console "from" the WSUS server

                       

                      Our structure is:

                      - 3 sites, 1 WSUS on every site

                      - until today, i only manage our local WSUS (with PM, all roles) through PM, Databases WSUS/PM are on another server

                      - later I possibly install PM servers (Automation role) on every site

                      - I can do inventory and client management action from my local PM server

                       

                      You are right. Because got the version error i decided to update all wsus server to KB2938066. On our local and one of the remote WSUS this where successful (both WSUS role on Server 2008 R2).

                      But on the last the installs aren't sucessful but the wsus server version raised.

                • Re: WSUS Version mismatch 3.2.x <--> 3.2.y ?
                  sz-a

                  After all I removed the mentioned Update from the Installer and Uninstall-Paths from registry. Then I installed the latest WSUS-Update which now where successful. After that I could publish 3rd party updatest to every WSUS and the clients got the new wsus client update.

                   

                  summa summarum: Don't trust the list of installed Software and Updates if you didn't install something successfully by yourself.

                  1 of 1 people found this helpful