Ok I worked with our SysAdmin we put the Listener name in DNS and used the primary replica IP for the Listener.  After DNS propagated I was finally able to...

Can you give me details on how to create a DNS alias?  Appreciate the information everybody!

@sreekanth,

both the below links show how to set up a listener in a Read-Scale AG set up (clusterless AG).

https://kohera.be/blog/sql-server/clusterless-availability-groups/

https://www.sqlservercentral.com/blogs/configure-always-on-ag-with-sql-2017

@Beatrix,

You are correct, but at least...

Where did everybody go?  This used to an active forum with lots of rich information and help.  =)

Sue,

You the wooooo MAN!  I was doing it on the Primary and then I did what you said to do and went to a replica and I see the wizard...

I use management studio and right click the AG group and select Failover and when the wizard comes up I select the secondary replica i want to failover too, but...

Found the solution.  It was tied to a network issue.  We moved our vms to another network and boom it connected and worked fine.

Correction node 2 is in Atlanta and node 3 is in Seattle with node 1.

Ok thanks.  Reading some more on this and seems to be service broker related and sure enough I see they have some sort of service broker set up.

Awesome thank you GilaMonster!  Now my next question is do I rebuild the cl index on this system table to get the size of this index down?

Thanks for the link to upgrade path Phil.  @michael-2 yes it would be an in place upgrade.  Makes life easier if I can just skip the sql 2016...

Hello guys thanks for the help.  I just disabled and enabled the queues and that seemed to take the messages away.  Recycling the queues helped I guess for now (crossing...

yes I have ran that query and i have some that says INACTIVE and NOTIFIED.

Ah yes sorry here is the message.

The queue 1845581613 in database 6 has activation enabled and contains unlocked messages but no RECEIVE has been executed for 1113349 seconds.

Sue,

Thanks for the tip may have solved the problem.  The problem looks like that SQL Log reader agent job was the culprit.  But, I disabled it before and...