Hi, I haven't seen this before. You may want to relax and/or update the permissions to the key store. (e.g. you're running as administrator in your development machine, but not in prod).
Also make sure the .pfx is readable by the web server (sounds like it is). Some relevant threads: http://social.msdn.microsoft.com/Forums/en-US/clr/thread/7ea48fd0-8d6b-43ed-b272-1a0249ae490f/ http://forums.asp.net/t/1183636.aspx Eric On Mar 23, 10:44 am, XMan82 <[email protected]> wrote: > I've been having some irregular issues with the x509 certificate. > Currently the implementation is working, but it seems unstable so far. > We generated the x509 certificate in both PEM (for Google) and PFX > (for us) formats as described in the Getting Started doc and that > worked perfectly in our test environment. We generated a different > x509 certificate the same way for our production environment, but when > we initially deployed with Google Health we received the following > error: > > System.Security.Cryptography.CryptographicException: > The system cannot find the file specified. > > Pertinent part of the Stack trace: > System.Web.HttpUnhandledException: Exception of type > 'System.Web.HttpUnhandledException' was thrown. ---> > System.Security.Cryptography.CryptographicException: The system cannot > find the file specified. > > at > System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException > (Int32 hr) > at > System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromFile > (String fileName, IntPtr password, UInt32 dwFlags, Boolean > persistKeySet, SafeCertContextHandle& pCertCtx) > > We are using similar code from the .NET code sample for signed > requests:http://code.google.com/p/googlehealthsamples/source/browse/trunk/dotN... > > To resolve this, our Server team recommended that we re-copy and > overwrite the PFX certificate file to our production website again; > and this worked. It was assumed that the PFX file on the production > environment had become corrupted somehow and was not working. However, > the same error came up later last week and was only evident for about > 4 hours and then started working again. Our production environment is > locked down much more than our test environment, but we are still > unaware of the root cause. Any suggestions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en -~----------~----~----~----~------~----~------~--~---
