Hmm, not seen that one. My only advice would be to try running the certificate manager from a command window (i.e. using python instead of pythonw). This will then give you more detailed error messages.
Hopefully someone else on the list knows this problem... Andrew :) ============================================ Access Grid Support Centre, RSS Group, Manchester Computing, Kilburn Building, University of Manchester, Oxford Road, Manchester, M13 9PL, UK Tel: +44(0)161-275 0685 Email: andrew.row...@manchester.ac.uk -----Original Message----- From: rctho...@lbl.gov [mailto:rctho...@lbl.gov] Sent: 08 March 2005 16:37 To: Andrew Rowley Cc: 'Shawn Needham'; ag-t...@mcs.anl.gov Subject: RE: [AG-TECH] Re: AG teleconf on 8/3 (fwd) On Tue, 8 Mar 2005, Andrew Rowley wrote: > You now need to import this into the Certificate Manager. To do this, > select the "Trusted CA Certificates" tab and select "Import". In the window > that appears, select the "AGDev.0" file for the "Certificate file" and > "AGDev.signing_policy" for the signing policy file (this might be selected > automatically when you select the .0 file). Select "Import" and it should > appear as "Access Grid Developers CA". Indeed when I selected the AGDev.0 certificate file to import into my trusted CA certificates, the accompanying signing policy file magically appeared in the other entry window. But the import again failed because it thinks one with the same name already exists. I click on the option to import anyway, but this results in an "error attempting to import." Yet my Trusted CA Certificates window is empty. I'm guessing the "name" of the certificate doesn't refer to the filename, since I copied it to a different name but this had the same effect. Rollin ------------------------------ Dr. R. C. Thomas Lawrence Berkeley National Lab 1 Cyclotron Road MS 50R5008 Berkeley, CA, USA 94720-8158 Tel 510.486.4697 ------------------------------
