Peter, I'm not sure what you mean by "either of the UVA .NET implementations". If you are talking about the service at https://wincluster1.cs.virginia.edu/HPCP/HPCPService.asmx, yes, it is still running. Try your client again and I will see if something appears in my logs. Glenn -----Original Message----- From: ogsa-hpcp-wg-bounces@ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Peter G. Lane Sent: Monday, November 06, 2006 10:28 AM To: ogsa-hpcp-wg@ggf.org Subject: [ogsa-hpcp-wg] Globus Status I have the create and terminate operations implemented and working locally. I will put up an endpoint sometime today, and by them will hopefully have the other operations implemented. Is there a WSDL snipit or something of this "Show job output" operation, or does this just mean that I have an FTP server running? Problems -------- I am unable to get responses from either of the .Net implementations using my client. My SOAP message logging show that the client message is going out, but nothing is ever received back. Are these services still up? I tried using my client on the Platform service (service URL https://plato.dreadnought.org), but I got an error saying that the client couldn't find the correct CA. I did download and install the CA cert and have debug output showing it was loaded, so I'm wondering if anyone has had success with this service recently. If so, Chris, could I get the public certificate of the server to help in my debugging? After agreeing that we wouldn't use EPRs, I'm confused about the use of them on the wiki. I did what others did and didn't bother implementing support for the WS-Addressing SOAP headers. The Platform EPR is trivial so that's not a problem. The GenesisII EPR, though, is very non-trivial. That said, I see that some clients have indeed talked to the GenesisII endpoint, so I'm rather confused. Did I miss a discussion where it was decided that full WS-Addressing support was now mandatory? Finally, I tried to use the CROWN endpoint too, but I get the following error: Authentication failed [Caused by: Defective credential detected [Caused by: [JGLOBUS-96] Certificate "C=CN,ST=Beijing,L=Beijing,O=company,OU=department,CN=localhost" expired]] Peter