none
Failover Cluster Manager bug on Server 2019 after .NET 4.8 installed - unable to type more than two characters in to the IP fields RRS feed

  • Question

  • We ran into a nasty bug on Windows Server 2019 and I can't find any KB articles on it. It's really easy to replicate. 

    1. Install Windows Server 2019 Standard with Desktop Experience from an ISO. 

    2. Install Failover Cluster Services.

    3. Create new cluster, on the 4th screen, add the current server name. This is what it shows:

    cluster services working correctly before .NET 4.8 is installed

    4. Install .NET 4.8 from an offline installer. (KB4486153) and reboot.

    5. After the reboot, go back to the same screen of the same Create Cluster Wizard and now it looks different:

    cluster services broken afte.NET 4.8 is installed - unable to put in a 3-digit IP

    Now we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters. 

    Has anyone else encountered this? It should be really easy to reproduce. 

    Friday, September 20, 2019 3:46 PM

All replies

  • We ran into a nasty bug on Windows Server 2019 and I can't find any KB articles on it. It's really easy to replicate. 

    1. Install Windows Server 2019 Standard with Desktop Experience from an ISO. 

    2. Install Failover Cluster Services.

    3. Create new cluster, on the 4th screen, add the current server name. This is what it shows:

    cluster services working correctly before .NET 4.8 is installed

    4. Install .NET 4.8 from an offline installer. (KB4486153) and reboot.

    5. Go back to the same screen of the same Create Cluster Wizard and now it looks different:

    cluster services broken afte.NET 4.8 is installed - unable to put in a 3-digit IP

    Now we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters. 

    Has anyone else encountered this?

    Thanks.


    Wednesday, September 18, 2019 5:11 PM
  • Hi,

    Thanks for posting in our forum!

    From your screenshot, it looks like a display problem.

    Do you have this problem in other places where you need to enter an IP address?

    We haven't received any similar feedback so far, and I've searched for known problems with this update, and I haven't mentioned them either.

    https://support.microsoft.com/en-us/help/4486153/microsoft-net-framework-4-8-on-windows-10-version-1709-windows-10-vers

    It is recommended that you restart the machine and try again. if still not, please reinstall Failover Cluster Manager feature.

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 19, 2019 7:25 AM
    Moderator
  • This is happening on *every* clean install of Windows Server 2019. Without .NET 4.8, it works fine. Issue above appears immediately after installing it. Uninstalling it fixes it. You should easily be able to reproduce it on your end. It's a new bug.
    Thursday, September 19, 2019 11:25 AM
  • Hello Michael,

    Good find, I suggest you submit this bug over here:
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, September 19, 2019 11:30 AM
  • Hello Michael,

    Good find, I suggest you submit this bug over here:
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    That's a link to report enhancement requests, not bugs. Were you able to reproduce this issue on your end?
    Thursday, September 19, 2019 12:50 PM
  • Open an incident with Microsoft support.  You are not charged for bugs.  

    However, the process 'appears' to charge you.  You need to provide a credit card (if you do not have a support contract), but when it is determined that it is a bug, no charge is applied to your credit card.  Microsoft has handled bug reports in this manner for many years, so it is a proven process.


    tim

    Thursday, September 19, 2019 1:26 PM
  • Well when creating a cluster, you shouldn't run any other installations (in general), especially .NET Framework as the Failover Cluster Manager uses the .NET Framework.

    I couldn't reproduce this as the .NET Framework 4.8 installer was complaining that the Failover Cluster Manager was open and needs to be closed.

    I did continue the installation without closing the Failover Cluster Manager, and the .NET Framework 4.8 installation was successful.

    However the issue you're facing might might be unpredictable, because the Failover Cluster Manager was not closed (as warned in my screenshot) and therefore it's producing unexpected things.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, September 19, 2019 1:31 PM
  • @Leon, I think you misunderstood.

     I installed Windows Server 2019 from the ISO. Then I installed Failover Cluster services. Then I installed .NET 4.8 using offline installer and rebooted. Then I opened the Create Cluster Wizard and ran into the issue above at that step. Uninstalling .NET 4.8 and rebooting and then opening Create Cluster Wizard, shows that the problem went away. 

    At no point did I have both open at the same time. Do you see the issue if all you install is .NET 4.8, *reboot* and THEN open the Create Cluster Wizard - are you able to type in 3 digit IPs in that "Address" window?


    • Edited by MichaelAdyne Thursday, September 19, 2019 1:37 PM clarification
    Thursday, September 19, 2019 1:35 PM
  • I'll give it a go..

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, September 19, 2019 1:38 PM
  • Thank you. If you can reproduce it on your end, on a clean install of Windows Server 2019 and just .NET 4.8 then it's clearly a bug. I just want to confirm that it's not specific to our environment (this is happening on a VM). 
    Thursday, September 19, 2019 1:44 PM
  • I can confirm, it happens to me as well, both on a cleanly installed Windows Server 2019, and also on a Windows Server 2019 (in use for other workloads).

    No matter how I try I cannot enter XXX.XXX.XXX.XXX in the Address field.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, September 19, 2019 1:54 PM
  • OK, so it's a clearly a new bug and I can't find any KBs or other forum threads mentioning this bug. How do we report this and get it fixed? Do you have any ability to directly contact Microsoft engineers?
    Thursday, September 19, 2019 1:56 PM
  • I suggest you do as Tim provided above.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, September 19, 2019 1:57 PM
  • Open an incident with Microsoft support.  You are not charged for bugs.  

    However, the process 'appears' to charge you.  You need to provide a credit card (if you do not have a support contract), but when it is determined that it is a bug, no charge is applied to your credit card.  Microsoft has handled bug reports in this manner for many years, so it is a proven process.


    tim

    No, it actually does charge $499 and then you have to apply for a refund. Sorry, I can't do that right now. Can you please file a bug report for this?

    Thank you.

    Thursday, September 19, 2019 1:59 PM
  • Have you ever tyr to use command to do this as a workaround?


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 20, 2019 1:30 AM
    Moderator
  • What command?
    Friday, September 20, 2019 1:33 PM
  • I sent this post off to the product manager for Failover Clustering.  However, after having done this in the past, I know he is going to ask you to file a bug.  That is the process that is followed - a bug report needs to get generated so it can be tracked through engineering.  A report from a customer who is experiencing the issue puts more emphasis behind it that an engineer filing.

    FYI, in the future, you may want to post clustering issues in the clustering forum.  https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverClustering  This forum is for general questions about Windows Server 2019.  You won't find many clustering engineers lurking in this forum.  There are some engineers I know who check the clustering forum from time to time, including the product manager to whom I forwarded this note.


    tim

    Friday, September 20, 2019 2:44 PM
  • How do I file a bug without paying $499 ?
    Friday, September 20, 2019 2:46 PM
  • Yes, they charge your card, but they remove the charge when they validate that it is a bug.  I'm sure you can imagine how many false bug reports they get.

    As this bug is so easy to reproduce, it should not take long for the engineers to validate it as a bug.  Yes, you are taking a bit of a risk that it is 'working as designed', but if it is as you say, it seems pretty obvious. 


    tim

    Friday, September 20, 2019 3:28 PM
  • Can I ask one of you (Tim or Leon) to call it in into the $499 line as a user-reported bug? You were able to duplicate it on your end as well, correct?

    Thanks a lot.

    -Michael.

    Friday, September 20, 2019 4:09 PM
  • Duplicate post.  Yes, technically it should have been posted here first, but there is a fairly lengthy exchange already established at https://social.technet.microsoft.com/Forums/en-US/a563b4e2-67d0-4f96-a10e-5136bc86521b/failover-cluster-manager-bug-on-server-2019-after-net-48-installed-unable-to-type-more-than-two?forum=ws2019.

    Failover cluster product management has been made aware of this issue.


    tim

    Saturday, September 21, 2019 1:57 PM
  • Leon and I are no different from you and would have to follow the same process of opening a case and supplying a credit card. Yes, I happen to be an MVP and I have known the failover cluster product manager for many years.  He responded to me within a couple hours saying he would be looking into it.  Let's see what happens.

    There is one point that I need to clarify though.  In your original post you state "we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters.".  In your network definition you defined a /24 network.  That means you should only be able to manipulate the fourth octet.  If you are trying to change one of the other octets, you would be placing the IP address into a separate network, which should be blocked.  Are you saying that before adding .NET 4.8 you are able to change other octets?  If so, that would also be a bug.


    tim

    Saturday, September 21, 2019 2:04 PM
  • Before installing .NET 4.8, we can only manipulate the 3rd octet - after installing it, we can manipulate all of them but only put in two digits. You should be able to replicate this on your end as well.
    Saturday, September 21, 2019 2:07 PM
  • Leon and I are no different from you and would have to follow the same process of opening a case and supplying a credit card. Yes, I happen to be an MVP and I have known the failover cluster product manager for many years.  He responded to me within a couple hours saying he would be looking into it.  Let's see what happens.

    There is one point that I need to clarify though.  In your original post you state "we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters.".  In your network definition you defined a /24 network.  That means you should only be able to manipulate the fourth octet.  If you are trying to change one of the other octets, you would be placing the IP address into a separate network, which should be blocked.  Are you saying that before adding .NET 4.8 you are able to change other octets?  If so, that would also be a bug.


    tim

    Right, so since you're able to independently replicate this bug on your end, would you mind calling in the $499 line and going through the normal procedure to report this bug?

    Thanks a lot.

    Monday, September 23, 2019 4:05 PM
  • What level of importance are you putting on this as a bug?  Yes, we can replicate it, but neither of us ran into this bug as an issue that is impacting our business.  As a result, its importance would rank pretty low on our bug reports.  Low business impact means low engineering priority.

    As I stated, the product manager (who is a great guy and has always followed up when he said he would) is aware and has said he will follow up.  Personally, I have never filed a bug report on clustering because I have known the clustering product management almost from the beginning of Windows clustering and have raised issues directly with them.  That has always been sufficient for me.  It does not mean that issues are resolved as quickly as I would like, but it has always worked for me.


    tim


    Tuesday, September 24, 2019 12:50 PM
  • What level of importance? Well, it means that we or anyone else who wants to use Failover Clustering will be unable to install .NET 4.8 on any server that uses it. I assume it's not super urgent yet but as .NET 4.8 becomes required for various applications, it will become more important. At the very least, there should be a KB article about it.
    Tuesday, September 24, 2019 1:13 PM
  • What level of importance are you putting on this as a bug?  Yes, we can replicate it, but neither of us ran into this bug as an issue that is impacting our business.  As a result, its importance would rank pretty low on our bug reports.  Low business impact means low engineering priority.

    As I stated, the product manager (who is a great guy and has always followed up when he said he would) is aware and has said he will follow up.  Personally, I have never filed a bug report on clustering because I have known the clustering product management almost from the beginning of Windows clustering and have raised issues directly with them.  That has always been sufficient for me.  It does not mean that issues are resolved as quickly as I would like, but it has always worked for me.


    tim


    Please let me know if you hear back from the product manager. 
    Tuesday, September 24, 2019 6:50 PM
  • Sure, if I hear anything more I will report it here.

    tim

    Wednesday, September 25, 2019 1:20 PM
  • Michael,

    Please send me an email and I can get a case created (no charge) for you on this.  I just need your contact information.  We can create the bug and get it to the correct people.

    John


    Thanks, John Marlin Microsoft Program Manager

    Thursday, September 26, 2019 9:27 PM
  • Michael,

    Please send me an email and I can get a case created (no charge) for you on this.  I just need your contact information.  We can create the bug and get it to the correct people.

    John


    Thanks, John Marlin Microsoft Program Manager

    Sure, I can send it to you. What's your email address to send it to?
    Thursday, September 26, 2019 9:28 PM
  • john.marlin@microsoft.com

    Thanks, John Marlin Microsoft Program Manager

    Thursday, September 26, 2019 9:30 PM
  • Hi Michael and followers of this thread,

    The .Net team has been made aware of this issue and is investigating.  John and I are in communication with them.  They do not have a need to create a support case for this issue at this time.  If that changes, I'll be in touch.

    Thank you,

    Chris

    Friday, September 27, 2019 6:27 PM
  • Hi Michael and followers of this thread,

    The .Net team has been made aware of this issue and is investigating.  John and I are in communication with them.  They do not have a need to create a support case for this issue at this time.  If that changes, I'll be in touch.

    Thank you,

    Chris

    Will there be a KB article describing this issue?
    Wednesday, October 2, 2019 8:58 PM
  • As noted by Chris, this is a .NET issue, so they would be the team that would be responsible for creating a KB for it.  Most likely they are working on a fix.  Based on past experience, depending on how quickly they feel they can generate a fix, they would publish a KB article explaining the limitation or a KB detailing the patch to apply.  But the KB article will come from the .NET team as they are team developing the solution.

    tim

    Thursday, October 3, 2019 1:36 PM
  • Just touching base with the thread.  We have identified the issue and currently working on the fix.  Didn't want you to think we forgot about this thread.  Nope, we are on it...

    Thanks, John Marlin Microsoft Program Manager

    Friday, October 11, 2019 7:19 PM