Workflow and ServiceDesk Community

 View Only
  • 1.  SD 7.5: Can't Work Incidents in Firefox

    Posted Nov 27, 2013 02:58 PM

    Has anyone else seen this? I can not work an incident in Firefox on either OS X or Windows. I've tried FF 23 and up and when you click on the "Work Incident" link the page opens but remains blank. We haven't made any major modifications to the system at all. We are running 7.5 SP1 and didn't actually test it prior to SP1 (working an incident from FF).



  • 2.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Nov 27, 2013 03:08 PM

    I just finished an upgrade to 7.5 SP1 and you scared the heck out of me! :)

    The good news is that yes, I can indeed work incidents properly on FF 23. Only tested Windows version, but I'm going to assume it's fine.



  • 3.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Nov 27, 2013 03:15 PM

    That helps and sorry for the scare! It means that it is likely us but now to figure out where the error is and how to fix it. Its the only thing that doesn't work for us. Had a scare for a little while becasue I couldn't select or change a category on the Work Incident screen from IE or Safari, it just wouldn't let the drop-down to work at all and then I realized that there was HTML in the description field. Removed the HTML tags and then the categories could once again be selected.



  • 4.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Nov 27, 2013 03:38 PM

    I've noticed the same things about the HTML handling. We have a large amount of it in IM descriptions and it would just get stripped out during a work or edit event, but now it's not getting silently stripped. This is causing some minor grief in the way we input tickets, but should be easy to work around.



  • 5.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Dec 06, 2013 02:01 PM

    A little more snooping into the console with Firefox and it appears that the issue is with FF 23 and above and an issue with Mixed Active Content! Even though everything we're doing is going over SSL, Firefox is still blocking the content in the iFrame of the page when you try to go work an incident. You can work around it by clicking the shield in the addressbar and disabling the blocking for that page but it isn't a good solution at all since it isn't persistent 

    Has anyone else seen this at all or do you think we have some funny non-SSL things going on here? I know it could be a lot of things but that's as far as we've gotten so far.



  • 6.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Dec 06, 2013 03:22 PM

    I may have had similar issues when I switched the server from http to https, but that was a while ago, so I can't say for sure. I think the real question is why is content mixed? Was this server always setup as https or was it switched to it at some point? If it was switched, there may be something that was missed.



  • 7.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Dec 09, 2013 09:25 AM

    It was always https. There does appear to be calls to one or two elements over http according to the console so now the task of trying to hunt them down and figure out where and why it happened.



  • 8.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Dec 09, 2013 09:35 AM

    Might be able to use this article as a sort of checklist: https://www.symantec.com/connect/articles/add-ssl-your-existing-servicedesk-75-installation

    And just to be thorough, the same thing for SD 7.1, not needed here, but in case some 7.1 user stumbles across this thread: https://www.symantec.com/connect/articles/enable-ssl-servicedesk-71-after-post-install-wizard-finishes



  • 9.  RE: SD 7.5: Can't Work Incidents in Firefox

    Posted Dec 12, 2013 10:58 AM

    Interestingly I checked each table and the application settings and they all have the right https:// URL. There might be another place,  just need to try to track it down. Here's the error from FF specifically:

     

    [10:53:09.712] Blocked loading mixed active content "http://servername/ProcessManager/WorkflowTasks/TaskResponsePage.aspx?TaskID=12c7af5c-5790-11e3-ad66-005056a761d4&TaskResponseID=12c7af6a-5790-11e3-ad66-005056a761d4&time=1386863589703&vw_id=win_response_12c7af6a-5790-11e3-ad66-005056a761d4" @ https://servername/ProcessManager/scripts/VirtualWindow/window.js:334

     

    Obviously there's an HTTP reference but have no idea where its getting that one from.