locked
Authorize failing redirecting to https://account.healthvault-ppe.com:443/undefined RRS feed

  • Question

  • I went through http-headers, the last thing it tries to post to is 

    #request# POST https://account.healthvault-ppe.com/appselectrecord.aspx?appid=813C11EA-1B9C-11DD-AB99-FEB456D89593&redirect=https%3a%2f%2fwdh-qa.spinnphr.com%3a443%2fauth&selrecordid=6db1ffc5-451b-4168-9501-8f25639fdacf
    Then it redirects to: https://account.healthvault-ppe.com:443/undefined
    Wednesday, June 24, 2009 8:25 PM

Answers

  • UPDATE: this code bug was present in a code update to the HealthVault platform in the PPE environment.  The release had been scheduled to go live to production this week, but we have decided to delay the release and fix the bug (two bugs, actually), do some additional testing, and release next week.

    This issue should no longer occur after the bug is fixed.

    That being said, while you can have different versions of the same type in an online and offline rule, there likely isn't any good reason to do so, and many reasons to avoid doing so.  Please try and ensure your type versions match between online and offline rules.

    Thanks for the issue/bug report-- it has helped us improve the quality of our own releases.  Keep those bug reports coming.

    Thanks.
    Wednesday, July 1, 2009 6:24 PM

All replies

  • You may want to try again and check if the problem persists since I see updates to HV sites over the last day...

    Raj
    Raj HealthVault Developer Tool http://xray.getrealconsulting.com
    Thursday, June 25, 2009 4:42 AM
  • Still happening, but that's good to know.
    Thursday, June 25, 2009 7:20 PM
  • I just tried (from your post above):
        https://account.healthvault-ppe.com/appselectrecord.aspx?appid=813C11EA-1B9C-11DD-AB99-FEB456D89593&redirect=https%3a%2f%2fwdh-qa.spinnphr.com%3a443%2fauth&selrecordid=6db1ffc5-451b-4168-9501-8f25639fdacf

    And it worked for me (I ended up in the app auth workflow as expected).

    Is this still occurring for you?
    Thursday, June 25, 2009 8:21 PM
  • Still not working. I get to the page where the user is to select a person to authorize (note: in Chrome, it doesn't list the names, just '...'). But when I select one and click 'CONTINUE', I get:

    in IE8:

    We're sorry. We could not complete your last request.

    An error occurred that we did not expect. The most recent action you were taking may not have completed successfully, but the rest of your HealthVault information is still safe.


    Firefox/Chrome: 

    We're sorry. We cannot find a page with that address.

    and the url is https://account.healthvault-ppe.com/undefined

    On another note, when will we be able to selected all the records at once (using checkboxes)? That was shown at the conference.
    Thursday, June 25, 2009 8:32 PM
  • Interesting-- I can reproduce the first (IE8) behavior you're seeing above.

    Regarding the checkboxes, no announced date... we're working on it.  It'll be a big improvement for us and our partners, so we'll release it as soon as it's done.
    Thursday, June 25, 2009 8:43 PM
  • Our engineering team has investigated last night and this morning, and it appears this is due to a combination of an unusual data type rule combination and a recent code change we made to the HealthVault platform code.

    It looks like you have one version of the "Procedure" data type configured for Online access, and the other version configured for Offline access.  The mismatch of one version for online and the other version for offline is hitting a bug in our platform code that we missed in testing. 

    Can you change your data type rules to use the same version of the "Procedure" data type and see if the issue still occurs?

    This bug has been triaged as a very high priority issue, and we'll be shipping a fix soon.  However, until the fix is available, it's easy to avoid if you make sure to avoid version mismatches between your online and offline rules.

    Please let us know if that works for you-- we're continuing to investigate.

    Friday, June 26, 2009 5:16 PM
  • There is a mistake in the above post. You seem to be using different versions of Family History and Immunization thing types in online vs offline access rule. 
    Please update it to either use the same versions in both online and offline or have both versions in both online and offline.

     For easy lookup this is what you are looking for

    Immunization

    <type-id>cd3587b5-b6e1-4565-ab3b-1c3ad45eb04f</type-id> online

    <type-id>3d817dbe-af42-4a9d-a553-d1298b4d08fc</type-id> offline

     

    Family History

     

     

    <type-id>cd3587b5-b6e1-4565-ab3b-1c3ad45eb04f</type-id> online

    <type-id>22826e13-41e1-4ba3-8447-37dadd208fd8</type-id> offline

     

    Thanks,

     

     

    Hema
    Friday, June 26, 2009 9:37 PM
  • Hema-- thanks for the correction.  Apologies for the mistake in my post.

    mdotmoment11: please let me know if this works for you.  If so, I may need to work with you to update the configuration on your production application as well.  Please feel free to contact me directly over mail and we'll work it out.

    Thanks for helping us find the bug here-- and apologies for the bug itself.

    Friday, June 26, 2009 10:53 PM
  • tried to make the switch, but get this error through the web interface for config:

    An un-expected error happened. Details:.


    Message:A master application must specify a child method mask ceiling
    Monday, June 29, 2009 10:31 PM
  • We're checking it out-- it looks like updates in the app config center, at least for this app ID, are having an issue.  We're investigating and ops/dev/test engineers are on it.  Apologies for the delay and error--
    Tuesday, June 30, 2009 1:06 AM
  • Quick update (we're also handling this over mail, but I want to keep the public thread updated as well):

    The ACC updates are working fine in general.  We made the data type changes to the app config here per above suggestions, and it apepars at this time to have solved the app auth issue.  We've successfully authorized records for this app ID at this time.

    We're continuing to check out some browser behavior questions at this point.

    Next step is to update the production app config today, once we're comfortable with the app config changes.
    Tuesday, June 30, 2009 3:10 PM
  • UPDATE: this code bug was present in a code update to the HealthVault platform in the PPE environment.  The release had been scheduled to go live to production this week, but we have decided to delay the release and fix the bug (two bugs, actually), do some additional testing, and release next week.

    This issue should no longer occur after the bug is fixed.

    That being said, while you can have different versions of the same type in an online and offline rule, there likely isn't any good reason to do so, and many reasons to avoid doing so.  Please try and ensure your type versions match between online and offline rules.

    Thanks for the issue/bug report-- it has helped us improve the quality of our own releases.  Keep those bug reports coming.

    Thanks.
    Wednesday, July 1, 2009 6:24 PM