Timeline for SSMS Crashes When Creating or Editing SSIS Packages
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2018 at 23:56 | comment | added | AKDiscer | Same here, still have a ticket open with Microsoft. We've been doing little things here and there, memory dumps, etc. So, we're still waiting on them to build a similar environment and then we'll troubleshoot more. | |
| Jun 22, 2018 at 15:07 | comment | added | Steve Pantazis | I worked with an engineer from Microsoft last night to look at the SSMS crash problem. The engineer took copious notes, with the plan to recreate the same environment at Microsoft to determine what is causing the crash, and offer a workaround and time to resolution. He threw out a what-if question, and asked if I might consider a lower Windows version than Windows Server 2016, which seems to indicate the problem with SSMS in SQL Server 2017 might have a correlation to Windows Server 2016--pure conjecture on his part, but interesting nonetheless. | |
| Jun 22, 2018 at 13:18 | history | undeleted | Paul White♦ | ||
| Jun 22, 2018 at 13:18 | history | deleted |
ypercubeᵀᴹ András Váczi Paul White♦ |
via Vote | |
| Jun 22, 2018 at 13:18 | history | edited | Paul White♦ | CC BY-SA 4.0 |
Incorporated comments
|
| Jun 21, 2018 at 23:46 | review | Low quality posts | |||
| Jun 22, 2018 at 11:14 | |||||
| Jun 21, 2018 at 23:42 | review | Late answers | |||
| Jun 21, 2018 at 23:45 | |||||
| Jun 21, 2018 at 23:26 | review | First posts | |||
| Jun 21, 2018 at 23:32 | |||||
| Jun 21, 2018 at 23:21 | history | answered | Steve Pantazis | CC BY-SA 4.0 |