I've had another failure this morning and unfortunately the event was too brief to try most of the diagnosis actions suggested. I was running a script that ran...

Gotcha, I think I went from "automatic failover within the AO group is not supported when one of the AO replicas is a clustered instance of SQL Server" to "the...

Thanks again for your comments and your article really clears that up for me.

I can't seem to be as word efficient in my questions as you are in your responses....

Thanks for the information, I appreciate the suggestions.

We do have the ability to reference the IP addresses in one location from another. We can reference DNS names to...

I've realized just now that I should probably also say that I know the issue is not blocking. I do look for blocking every time this problem comes...

Thanks to both of you for your suggestions.

I'll take a look at the service account the next time this happens. I have a GUI AD viewer that I...

I do usually try and hit the URL via windows explorer and can do all the normal read write functions like add a file, drop a file, rename a file.

I...

Thank you for taking the time to respond.

I do run a backup command via a scheduled job that different syntax and it seems to generate the same error messages.

The code...

We did get an approval for a reboot and that solved the issue.

That thread does sound like the same thing.

Thanks for your help! For some reason, it's a little comforting to know that someone else seems to be experiencing the...

Thanks for the info. "sticky-cache" does seem like a pretty appropriate description of this AD behavior.

I had tried removing the ID and readding it, but unfortunately that didn't...

Not a problem, thanks for the suggestion. It got me thinking about logging in general.

There is some logging in the install bootstrap folder. For me this was C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log and then in the most recent folder there's a Detail.txt file.

I found...

Thanks for the suggestion. I ended up finding the issue in the log folder of the bootstrap folder. For me this was C:\Program Files\Microsoft SQL Server\100\Setup...