go to post Bob Binstock · Jun 22, 2022 Tom, can you provide a little more info? was this a different IRIS instance than the one you successfully connected to from VS Code? was it remote? what port # did you use in the successful case, and what # in the failed one? i think the error message is from VS Code, is that right?
go to post Bob Binstock · May 19, 2022 they were in one of the lists in the section David linked to, but now they are in all four. thanks for catching this David!
go to post Bob Binstock · May 18, 2022 inadvertently omitted, sorry. will add to the doc as soon as i get a chance.
go to post Bob Binstock · Apr 30, 2019 we'll add the USER> prompt and a link to the Terminal doc to these instructions, and get rid of the extraneous word.
go to post Bob Binstock · May 23, 2018 in deference to the wisdom of Salva and Doug, i have removed the section about mounting files individually.
go to post Bob Binstock · Mar 23, 2017 If you are doing database encryption only, this is very unlikely to be the problem. Journal encryption is a bit tricky as indicated by the text I cited, but as that text also says, "there are no specific mirroring-related requirements for database encryption".
go to post Bob Binstock · Mar 23, 2017 William, is it possible that the DR async and failover members do not have all of the needed encryption keys loaded? See Activating Journal Encryption in a Mirror in the High Availability Guide. This text applies to releases supporting multiple encryption keys; what release are you running?
