locked
Healthvault production environment error RRS feed

Answers

  • Hello All,

    Application configuration difference between PPE and PROD environment caused the above issue and it is resolved now.

    Thank you,


    Anish Ravindran
    • Proposed as answer by Anish Ravindran Wednesday, February 2, 2011 1:26 PM
    • Marked as answer by Aneesh D Tuesday, March 8, 2011 9:19 PM
    Wednesday, February 2, 2011 1:25 PM

All replies

  • Hello Jmannummel,

    Could you please let me know whether you are getting any error if yes please paste the complete stack trace of the error. Please send me your application Id to my email Id: v-madank@microsoft.com .

    Regards,

    Madan Kamuju

    Thursday, January 27, 2011 3:53 PM
  • For production applications, the redirect is controlled on a per-application basis using the "action URL" defined for the application in the online application configuration center.

    It's possible that that value is set to https://www.test.com

    If that's the problem, you can update that to the full URL for the redirect page and make a new "go live" request so that we can push the update to our production system.

    Thursday, January 27, 2011 5:33 PM
  • Hello ,

    We are trying to sync the data between orbitphr production environment and healthvault.

    It was working in ppe environment. The same app id is moved to production.

    There is no action url mentioned in the online https://config.healthvault-ppe.com/ configuration while sending the certificate for production deployment. ( It was blank while sending the same cert to production deployment )

    Whether we need to set the action url in the https://config.healthvault-ppe.com/ and re-send it again to the microsoft team to publish ?.

    Changes done in the https://config.healthvault-ppe.com/ will reflect in the production environment or we have to resend it ? .

    Error

    Its always redirects to

    <add key="WCPage_ActionAppAuthReject" value="https://www.orbitphr.com"/>

    Since it is failed from the authentication side , its not executing any code in the page.

    Thanks,

    Jmannummel

    Friday, January 28, 2011 6:36 AM
  • Hello jmannummel,

    For security reasons, the production version of the HealthVault Web site redirects only to URLs that have been submitted to Microsoft in advance. Each application must register an ActionUrl on the HealthVault server. The page at this ActionUrl should be capable of understanding ten different targets that can be passed to the application by the HealthVault Web site.

    If your application is already in live then you need to contact the Go-Live team , The changes are minor then the Go-Live team will review and push the changes to Production Environment.

    If your application is not in live you need to go through the complete process of Go-Live . For more information please look into the Go-Live Guide .

    You need to set the correct ActionUrl in PPE and make a Go-Live request so that we can push the changes to Production Environment. Please look into this URL for more information on ActionUrl.

    Please let me know if you have any queries.

    Regards,

    Madan Kamuju

    • Proposed as answer by Madan kamuju Friday, January 28, 2011 1:55 PM
    Friday, January 28, 2011 9:55 AM
  • The below web.config variable is there in the pre production environment

    <add key="NonProductionActionUrlRedirectOverride" value="Redirect.aspx"/>

    and http://localhost/redirect.aspx in the online configuration ppe.

    1). If we move the same id to production whether it will work or not?.

    2). Whether we need to comment the web.config variable key="NonProductionActionUrlRedirectOverride" in production environment

    Thanks for the reply.

    Thanks,

     

    Jmannummel

    Friday, January 28, 2011 1:28 PM
  • Hello Jmannummel,

    Please find the below comments for your questions and let me know if you need any other information.

    1). If we move the same id to production whether it will work or not?.

       Answer:   The same Id will not work in Production environment until we review your configuration as i mentioned in my previous post.

    2). Whether we need to comment the web.config variable key="NonProductionActionUrlRedirectOverride" in production environment

       Answer: You need to comment this line in web.config file because this will make sure that your HealthServiceActionPage won't over-ride  the default action url which you set in your application's configuration.

    Please look into this URL for more information on ActionUrl handling in different environments.

    Hope this helps and let me know if you need any other information.

    Regards,

    Madan Kamuju


     

    • Proposed as answer by Madan kamuju Friday, January 28, 2011 1:55 PM
    Friday, January 28, 2011 1:52 PM
  • Team,

    I am working with Arul internally to resolve the issue. I will update the thread once it is resolved.

    Thank you


    Anish Ravindran
    Friday, January 28, 2011 6:28 PM
  • Hello All,

    Application configuration difference between PPE and PROD environment caused the above issue and it is resolved now.

    Thank you,


    Anish Ravindran
    • Proposed as answer by Anish Ravindran Wednesday, February 2, 2011 1:26 PM
    • Marked as answer by Aneesh D Tuesday, March 8, 2011 9:19 PM
    Wednesday, February 2, 2011 1:25 PM