Justin Emlay

Thanks for the link. I was afraid of that. Unique AS2_IDs for every single partner attached to a unique certificate. Yeah, I have no intention of managing dozens of certs especially when more and more partners are following suit with that max 2 year standard. Over time they wont all expire all at once. I would have to keep a monthly eye on them. It looks like lots of other solutions out there (using a cert store) have adopted using a cert with backup or secondary cert to better handle the transition....

Thanks for that Bryan, I was having the same issue, oddly with Amazon as well (different area). I simply deleted that line and all was well after that.

Got everything up and running with the one exception of an issue with MDN mismatch on receiving. However it looks Iike I hit a wall with this particular solution. How do people handle having their cert expire then having to change that cert with many dozens of vendors instantly? Am I understanding this right? As a partner I can only have one global AS2_ID attached to a cert alias? So when I change my cert 100% of all my partner connections will have to use that new cert? In my current solution (iSoft/Liaison...

I don't understand what's going on here at all. On Server 2016 I also had this issue. I did as you suggested and changed Line 74 yet nothing changed after install (as others have reported). Same startup parameters. So I completely deleted that line. Exact same startup parameters. Line 74 has no effect on the install. So I traced it back to line 46 and changed that. Whatever I put on that line (set PR_STARTPARAMS=) is what gets set even though PR_STARTPARAMS isn't specified anywhere else in the file....???...

Is this project dead?