SSMS 18.0 crashes when editing a monitor server instance (by clicking the Settings button on the transaction log shipping page).
Have you always used SSMS to configure your system? I.e. not other tools or straight T-SQL? Is it a coincidence that for both columns you have a value of 14420? Is that a value you recall explicitly setting?
From what you are telling me, it looks like SSMS is assuming that 14420 is a number of days (as opposed to a number of minutes), hence it can’t handle it because “it is too big”).
More investigation going on…
No, it was done using T-SQL. I was just trying to go in and look at something in the setup when it crashed.
14420 - Threshold_alert
14420 - history_retention_period
I was waiting for 18GA to come out. I didn't even have any of the previews installed on this computer.
SQL Server Management Studio 15.0.18118.0
Microsoft Analysis Services Client Tools 15.0.1300.131
Microsoft Data Access Components (MDAC) 10.0.17134.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.17134.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.17134
Here is a link to the procdump request
I am having trouble uploading the 325mb file it generated.