Tab issues using SSMS solutions.

Question

Tab issues using SSMS solutions.

largotik

SSC Enthusiast

Points: 163
More actions
December 11, 2017 at 7:20 am

#409847

Hello everyone. I have a problem. Please, help me 🙂
I use Microsoft SQL Server 2016 and SSMS 17.3
I start new project, create and open several queries, click "Save all" and close SSMS.
Wwhen i open project again, and it opens the tabs to where i started last, when i click on the tabs they auto close. I see error "Value cannot be null. Parameter name: o The tab has been closed" on window bottom.

If I use SSMS 2014 in the same scenario - everything is fine.
Thank you for your responses.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246963 More actions · Answer 1

largotik - Monday, December 11, 2017 7:20 AM
Hello everyone. I have a problem. Please, help me 🙂
I use Microsoft SQL Server 2016 and SSMS 17.3
I start new project, create and open several queries, click "Save all" and close SSMS.
Wwhen i open project again, and it opens the tabs to where i started last, when i click on the tabs they auto close. I see error "Value cannot be null. Parameter name: o The tab has been closed" on window bottom.

If I use SSMS 2014 in the same scenario - everything is fine.
Thank you for your responses.

Did you name the individual scripts?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

largotik SSC Enthusiast Points: 163 More actions · Answer 2

Phil Parkin - Monday, December 11, 2017 7:25 AM
largotik - Monday, December 11, 2017 7:20 AM
Hello everyone. I have a problem. Please, help me 🙂
I use Microsoft SQL Server 2016 and SSMS 17.3
I start new project, create and open several queries, click "Save all" and close SSMS.
Wwhen i open project again, and it opens the tabs to where i started last, when i click on the tabs they auto close. I see error "Value cannot be null. Parameter name: o The tab has been closed" on window bottom.

If I use SSMS 2014 in the same scenario - everything is fine.
Thank you for your responses.
Did you name the individual scripts?

Tried called them individually and use the standard names.

alex.ivdroid2 SSC Rookie Points: 30 More actions · Answer 3

alex.ivdroid2

SSC Rookie

Points: 30

December 12, 2017 at 8:51 am

#1971768

I have the same issue using SMS 2017.

Jason Hannas SSC Enthusiast Points: 100 More actions · Answer 4

I'm having the exact same issue...all scripts are named, saved, and in the solution. Save All, close SSMS, reopen--get error reported by OP. Only one of the scripts tabs is open. Order of tabs doesn't matter--always the same one.

Did you ever get this solved?

bioforger Grasshopper Points: 19 More actions · Answer 5

Jason Hannas - Monday, March 26, 2018 6:40 AM
I'm having the exact same issue...all scripts are named, saved, and in the solution. Save All, close SSMS, reopen--get error reported by OP. Only one of the scripts tabs is open. Order of tabs doesn't matter--always the same one.
Did you ever get this solved?

Yep same issue here, so annoying, why isn't this reported as a larger issue, its a pretty fundamental bug. Imagine if you need to open like 20 scripts or something like me, massively inconvenient. And it's still happening in the latest V17.9 release, anyone found a workaround?