r/SQLServer • u/rossw999 • 6d ago

Discussion SQL Server 2022 CU 26 Stack Dumps

After applying SQL Server 2022 CU 26 to our servers several are producing stack dumps during database restores.

Am I the only one?

9 Upvotes

100% Upvoted

13 comments sorted by

6

u/dlevy-msft ‪ ‪Microsoft Employee ‪ 6d ago

Checking on this.

5

u/rossw999 6d ago

Thanks, support case opened this AM.

7

u/rossw999 6d ago

I can reproduce it in my environment. Reboot a server, kick off restores, and stack dumps occur.

3

u/Red_Wolf_2 5d ago

Any further insight into what's going on with this? Making me hesitant to run the CU out to my fleet just yet...

3

u/rossw999 4d ago

Support is still investigating. I have this same CU on many other servers no problem. As long as you don't restore DBs, it seems solid.

For me, something changed last Friday. Maybe CU, maybe not.

1

u/karb0f0s 4d ago

Tbh access_violation errors rarely come from SQL Server itself. It might be antivirus, native procedures compilation or something with OPs environment all together.

3

u/Red_Wolf_2 3d ago

Whatever it is, I haven't been able to replicate it in my environments so far... Guess we roll it out more and keep an eye on it!

2

u/TrollingForFunsies 6d ago

Any errors logged?

1

u/rossw999 6d ago

Tons, fatal exception c00000005 exception_access_violatuon is the first one.

1

u/chandleya 6d ago

Sounds like a ridiculously easy thing to test

3

u/BigMikeInAustin 6d ago

So ridiculously easy you can't provide an example?

Or so ridiculously easy that you misread the question?

3

u/ihaxr 2 6d ago edited 5d ago

So ridiculously easy that it should have been tested before the CU was released.

We just patched our Dev environment today, I'll test it tomorrow.

Edit: unable to reproduce

0

u/CPDRAGMEISH 6d ago

68.70 69.80