I get the exact same error.

The logins are on five machines and are all AD accounts.  My dev team is all under one AD account and can access 4 out of the 5 machines.  I...

Thanks for posting, the post explained the issue.  I had already had the team switch back to the primary to read the value and told them we would have to...

I finally got bulk insert working through the AG listener; unfortunately I don't know exactly which of the changes made the difference.  Many of the changes were in AD so...

Jeff,

As I said, I am really hoping this is all around serializable isolation. The code has not changed, in fact the code causing the problem is over 5 years...

I still never found a reference to that operator, but did have some alerts set up for replication. I deleted them and it seems to have solved the problem....

As I said, they are not being logged in SQL Server's error log hence I don't think the connection ever gets to an attempt to log into SQL Server. ...

Yes, I understand that now. Thanks! I was not thinking about the fact that once the transaction log is written on the secondary that it then needs to...

Thank you for the explanation sqlnyc; I had a basic misunderstanding on how the log was being applied at the secondary. I have read a bit more to understand...

I actually caught the error in the script after I posted it, but specifying the database in the connection string was the problem... That would have been done through the...

I had to tear down everything because it was in our QA environment and they thought it was affecting them. I spent some time setting everything back up today....

I am going to give it a try again, in the mean time I figured out why I could not connect to the primary node using its host name. ...

I followed this article: https://msdn.microsoft.com/en-us/library/hh710054.aspx and originally set up everything using the wizards.

Paul, thanks for bringing that up. I am setting up a new server, and yes I was using RDP and using SSMS on the local machine. I tried...

From the SQL Server error log... Login failed for user 'Domain\user'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

Initial searches suggest...