8 Replies Latest reply on Feb 4, 2014 2:15 PM by Josh_Corey

    Script Error

    charlotte0204

      We implemented two e-forms for 80 employees across the organization to submit "yes/no" type responses each month.  We are in a CITRIX environment, and about half the employees are on a PC with the remainder on a WYSE terminal.  Many employees, when launching the form, are receiving an error message regarding the scirpt.  Once they select "No', they are able to proceed to completing the form.  Any insign into what may be causing this and how to resolve the issue?  A copy of the error message is below:

       

      New Picture (1).png

        • 1. Re: Script Error
          Todd Rein Level 3

          Hi,

           

          Can you send me a private message with your form URL and we'll take look? 

           

          Thanks,

          Todd

          • 2. Re: Script Error
            Todd Rein Level 3

            Hi,

             

            Thanks for the URLs.  Note that when you reply to the forum emails, your response is posted back to the forums and is public.  If you want to send me a private message, so no one else can see your response, log into the forum, and click the send private message link.

             

            We tried viewing your forms on IE9 here, and could not reproduce the problem.  So we'll need to get more information from you to help us try and reproduce the issue.  Here's some questions:

            - Are you seeing the issue when you view the form?  Or after you fill it out and click submit?

            - When you do see the issue, what version of IE you are using?  Go to the help | about menu.  If you can give us the full version # (major and minor version #s) that will help us.

            - If you are using IE9, do you know if you are using compatibility mode?

              - Do you ever see the issue in non-IE browsers (i.e. Firefox, Chrome, etc.)?

             

            Thanks,

            Todd

            1 person found this helpful
            • 3. Re: Script Error
              charlotte0204 Level 1

              Hi Todd,

               

              This happens in our Citrix environment once the user accesses either form from the link posted to our Intranet. When you first click on the link or URL, you can see the progress bar at the bottom taking longer than expected to pull down the online form. After about 15-20 seconds, you will receive the error "Stop running this script" - A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer might become unresponsive.

               

              You then have to select "NO" two times in order to continue. This was occurring on my pc but I found a microsoft kb article and "fix-it" tool that resolved only on my pc. The issue is we are not able to run such utilities in our Citrix environment or on the terminal servers. We are running IE 8 v8.0.6001.19272. I do not believe we have Mozilla installed on any terminal servers but I will verify and test.

               

              I JUST LOGGED INTO OUR INSURANCE SERVER ENVIRONMENT WITH A TEST ACCOUNT AND IT WORKS USING IE 9 BROWSER. COULD IT BE THE AUTHOR HAD IE 9 WHEN CREATING THE ONLINE FORM?

               

              Patrick Bedgood

              • 4. Re: Script Error
                AmiJasonInLove

                I have the same issue with a new form I created.  It's quite a lengthy FormsCentral online document.  It didn't have any script errors until I really started digging into the additional features (Skip Logic) and added additional questions.  If I have too much skip logic will it gum up my form or is there a limit to how complex/big a form is on the FormsCentral? I am running IE 7 and most users will take a while to migrate to IE8.

                • 5. Re: Script Error
                  RandySwineford Adobe Employee

                  We'll be happy to help you out. Can you please share the form URL with us? Either post it here or email us at formscentral_feedback@adobe.com

                   

                  Thanks,

                  Randy

                  1 person found this helpful
                  • 6. Re: Script Error
                    Workflow Specialist

                    I too have that same problem, and feel that the issues lie with excessive rules.  I create many forms, some more complicated than others, and ONLY the ones with complex rules, such as Property State IS NOT...... (30 states) seem to have issues.  This is due to Adobe's inability to allow multiple types of ANY/ALL statements.  So, in situations where you are cross referencing several attributes, such as Property State, Business Source, and Transaction type... You are forced to write a very complex rule including many IS NOT, or create a single rule for all 50 states or scenarios.  I am testing now to find out which one works better.  I truly believe that if your field has over 20 rules associated with it, the system begins to show lag, or have script errors.

                     

                    Adobe Staff, please help me.

                    • 7. Re: Script Error
                      Workflow Specialist Level 1

                      Randy, if you could assist me with script errors on a large adobe form, i would appreciate it.  As you see in my description, once the parameters get to be large, we have script issues.

                      General forms run perfectly.

                       

                      Thanks

                      John S

                      • 8. Re: Script Error
                        Josh_Corey Adobe Employee

                        Hi Workflow Specialist;

                         

                        Can you share your form with me and we can investigate?  Share with jcorey@adobe.com and please include a reference to this Forum post so I know what we are looking for, instructions for sharing your form: http://forums.adobe.com/docs/DOC-2462

                         

                        I responded with the same to the email you sent to FormsCentral Feedback.

                         

                        Thanks,

                        Josh