Ran across this a long time ago and then it came up for our sister site this week and my recollection of this problem was their solution. Thought I would pass it along. If you have a user for whom Growth Charts won't work, but everyone else is working fine, have them change their password. I knew that my problem years ago was a special character in my password. Turns out when the users at our sister site removed the ampersand (&) character from their EMR password, Growth Charts worked again. If you have any accounts set up in the EMR that access CWS/JBoss, make sure you are careful with special characters in the password.
Cheers!
This makes me wonder about other special characters that are used in SQL. % ; , ' and " may all cause a problem, among others. I'm betting the webserver uses input validation that interferes with those characters.
Thank you for posting this. We had one user with this issue and now she can run growth charts.
This didn't work for us. Any other suggestions?
Is it just one user with an issue? Is there any error message?
This is only happening to one Provider, no error message. IT opens in a blank white pop- window where the growth chart should appear. We've changed her password to not include the '&' or a '@' symbol. And I also tried changing the compatibility mode. We are using IE10 on a hosted server. I have not verified that hosted server has Adobe SVG viewer.
If the provider is logged in and then exits back to the login screen and someone else logs in using her same session, do Growth Charts work for this second user or do they get the same blank page?
The second provider logged in the same session and had the same blank growth chart.
Ok, then it is something having to do with that server and not that user. I would suspect that if you had that provider log into a different app server that Growth Charts would work. You will need to check the Adobe SVG install (if you are on a version that is still supporting that) and registry key permissions for Adobe - they can sometimes cause issues. And double-check the browser, though it sounds like you already did. Good luck!