December 11, 2017 at 11:14 am
Eirikur Eiriksson - Monday, December 11, 2017 10:50 AMSomehow the FInUse rings a bell, come a cross problems highlighting the function when the authentication mode was incorrectly configured, might be worth looking into
😎
My friend from across the puddle.. How are you doing buddy? I hardly have time to reply often but I read your posts / articles. Awesome!
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
December 12, 2017 at 2:08 am
It's from a private list with MS that the option was suggested. If this is not a test environment, I wouldn't enable that without guidance from MS. In fact, with a stack dump, I'd be calling MS Support to see what they can deduce from logs.
December 12, 2017 at 3:36 am
Steve,
I tried -x, but unfortunately I had a fresh crash with -x on.
Eirikur,
I am using mixed authentication mode, but ALL MY DATABASES ARE CONTAINED (accounts are included in the database). Do you think it has to do something with contained accounts?
Thanks
December 13, 2017 at 2:12 am
I'd open a case with MS.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply