I have gone thru both articles and numerous others but I have3 still been unable to get the async DR member out of the waiting status. In the portal I went to SYSTEM>JOURNALS>MIRROR JOURNAL FILES and no mirror journal files show up. Are there cache or windows utilities that I can use to trace the activity between these two machines (primary & async member). What troubleshooting steps should I take now?
I have verified that the ports are open and in process explorer it appears that the async member goes to the primary successfully but I'm still getting an unable to connect in my console log.
There are no errors in my windows event logs. I turned on all system events in the audit log for both servers and there are no errors that show up.
I am on CACHE 2014.1.1.702
thanks for the suggestion. I did put the password in for the SSL setup. I'm sure it's something little that I'm not familiar with.
Thanks for the info and I opened a ticket with our support this morning. I'm just trying to dig thru as much as I can myself before letting someone else come in and fix it. I didn't answer your question but yes I did add the async as an authorized async on the primary.
Log in or create a new account to continue