175 reputation
7
bio website
location
age
visits member for 2 years, 2 months
seen Sep 16 at 15:38

Sep
12
comment “A severe error occurred” - Login Failed (but only occasionally)
Installing the update seems to have helped although I can't say for sure. It's been over 24hrs and the error hasn't occurred. Thanks for all the help.
Sep
11
comment “A severe error occurred” - Login Failed (but only occasionally)
@Shawn: I'm surprised I didn't stumble upon that article myself. Thanks for pointing it out. I installed the cumulative update for SQL Server 2014 per Max's recommendation and we'll see how it goes.
Sep
10
awarded  Editor
Sep
10
revised “A severe error occurred” - Login Failed (but only occasionally)
added 1077 characters in body
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
Returns zero results. ** For some reason I can't see the responses from James or AaronBertrand that you're referring to.
Sep
10
awarded  Commentator
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
It gives me an error saying you must have reputation of 20 to chat. Not sure what my reputation is.
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
The SID is found neither in the registry, nor via the PSGETSID utility. Here's the crazy thing: Two separate machines, neither of which are on a domain, and neither of which have record of this SID, are generating this error and referencing this same bogus SID: S-1-9-3-3788657366-1166700905-846186909-3339902698
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
The command works but the ID returned is not the same one in the error message. Nothing probative in Security and System logs. Application log shows error message from SQLSERVER but it's clear this error is a result the error we're discussing, not its cause: "The client was unable to reuse a session with SPID 55, which had been reset for connection pooling. The failure ID is 5. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message."
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
Ok, I found the error log. It says, "Reason: could not find a login matching the name provided." Multiple client machines received this same error, and all at exactly the same time (3:00:04 PM Pacific)... Then all of a sudden the problem goes away.
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
@Max: That is very strange! No, not only am I not using domain authentication, but the machines making the connection aren't even on domains (they're on a workgroup) so that should in theory be impossible. Can I reverse lookup the supposed domain/user that's being attempted? Maybe that would give me a hint?
Sep
10
comment “A severe error occurred” - Login Failed (but only occasionally)
@Max: Yes, contained database auth. That's what I'm using. The error log... I can find that in Management Studio, correct?
Sep
10
asked “A severe error occurred” - Login Failed (but only occasionally)
Dec
30
awarded  Nice Question
Oct
24
awarded  Popular Question
Nov
8
awarded  Supporter
Nov
8
accepted Reset all IDs in a Large Table
Nov
8
comment Reset all IDs in a Large Table
Excellent idea. I was hoping for a built-in "resetAllOfMyIDs()" function or something but this'll work. Thanks again.
Nov
8
asked Reset all IDs in a Large Table
Aug
25
accepted Placing Transaction Log on Separate Volume [solid state]?