Ted,
Sure, I get it, multiple dlls being called by the wrong apps. I've definitely been vicitm of this many times before. But we have verified this is not the case.
You say PowerBuilder has to work with the version fo those dlls that ship with it... however, we can put 9.0 dlls in 12.6, and get it to work fine with MKS. So obviously something has changed.
You keep bringing up encryption, but encryption would be on MKS's end. SCC sits between PowerBuilder and the version control product. Even if encryption was an issue, it would have shown up with PB 9.0, not only 12.6. Not only that, the 9.0 dlls work in 12.6. So obviously something has seriously changed, whether how they were complied by SAP, or changes in specs, but SCC has been around forever. I find it interesting that 12.6 isn't puking on the 9.0 dlls.
Researching the original error message that started this thread, I keep finding a ton of sites in blogs that relate to that being a compilation issue, that there was something regarding OpenSSL that wasn't included, or some setting they didn't set right.
I'm frustrated because I feel like this discussion is leading to "not our problem", because you guys are using open source software, leaving the customer at the door step, wishing them the best. Is that where we're at? Does SAP even track SCC changes that have occurred over the years to actually have a better explanation for the customer, other than, it's open source, not SAP's problem? I don't know, that approach seems like it could be costly, because there are still a lot of people out there that use older version control products, and the idea that they're on their own... with that level of support from SAP, I can see why people keep jumping ship.
Don't get me wrong Ted, you've been great, given me some great information, I'm just very frustrated right now, and feel like we're ending up with "MKS is old, the dlls are open source, not SAP's problem".
--Brian