2 Replies Latest reply: Sep 16, 2008 1:39 PM by Steve Skinner RSS

    Praying for a solution for "while executing findServerBehaviors" error

    Steve Skinner Community Member
      There has been a problem with Dreamweaver for quite some time regarding these problematic javascript errors. My error in particular is:

      "While executing findServerBehaviors in Insert Record2.htm, a JavaScript error occurred."

      This happens all the time, and renders the Insert and Update behaviors unusable until you restart DW. What this means is that I restart DW on any given day no less than a dozen times. Rediculous.... I've been testing with DW CS4 and this problem has not gone away, and actually seems to be worse.

      Please don't post a response linking to the article about troubleshooting javascript errors in DW, as I have already gone through all these steps - deactivating or uninstalling extensions, deleting winfilecache, recreating site cache, etc., etc.

      I am hoping that after all this time someone has figured out what this error actually points to and how to solve this problem. I have researched this as much as I'm able to and it appears to have something to do with the translation of the page where server behaviors are already present on the page. The file in question that causes this error seems to be serverbehaviorclass.js which I found on my windows vista machine at c:\program files\adobe\adobe dreamweaver cs3\configuration\shared\common\scripts\

      Is there at least any place where Dreamweaver logs the actual code or server behavior that causes this error? As it is the error is pretty non-specific, but it's such a usability problem within the program when it starts happening. I would be happy to stop using any extension that might be causing the problem, but there's no way to know which one it is. Disabling or uninstalling 3rd party extensions didn't seem to make much of a difference. In fact, this error often happens when working with a page where the only server behaviors used are Dreamweaver's own.
        • 1. Re: Praying for a solution for "while executing findServerBehaviors" error
          Newsgroup_User Community Member
          If that fails to solve the problem, then I recommend you contact Adobe
          directly and use one of your one-on-one support incidents.

          http://www.adobe.com/support/programs/dreamweaver/index.html?tab:contact=1

          --
          Murray --- ICQ 71997575
          Adobe Community Expert
          (If you *MUST* email me, don't LAUGH when you do so!)
          ==================
          http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
          http://www.dwfaq.com - DW FAQs, Tutorials & Resources
          ==================


          "Steve Skinner" <webforumsuser@macromedia.com> wrote in message
          news:gaoras$3m7$1@forums.macromedia.com...
          > There has been a problem with Dreamweaver for quite some time regarding
          > these
          > problematic javascript errors. My error in particular is:
          >
          > "While executing findServerBehaviors in Insert Record2.htm, a JavaScript
          > error
          > occurred."
          >
          > This happens all the time, and renders the Insert and Update behaviors
          > unusable until you restart DW. What this means is that I restart DW on any
          > given day no less than a dozen times. Rediculous.... I've been testing
          > with DW
          > CS4 and this problem has not gone away, and actually seems to be worse.
          >
          > Please don't post a response linking to the article about troubleshooting
          > javascript errors in DW, as I have already gone through all these steps -
          > deactivating or uninstalling extensions, deleting winfilecache, recreating
          > site
          > cache, etc., etc.
          >
          > I am hoping that after all this time someone has figured out what this
          > error
          > actually points to and how to solve this problem. I have researched this
          > as
          > much as I'm able to and it appears to have something to do with the
          > translation
          > of the page where server behaviors are already present on the page. The
          > file in
          > question that causes this error seems to be serverbehaviorclass.js which I
          > found on my windows vista machine at c:\program files\adobe\adobe
          > dreamweaver
          > cs3\configuration\shared\common\scripts\
          >
          > Is there at least any place where Dreamweaver logs the actual code or
          > server
          > behavior that causes this error? As it is the error is pretty
          > non-specific, but
          > it's such a usability problem within the program when it starts happening.
          > I
          > would be happy to stop using any extension that might be causing the
          > problem,
          > but there's no way to know which one it is. Disabling or uninstalling
          > extensions didn't seem to make much of a difference.
          >

          • 2. Re: Praying for a solution for &quot;while executing findServerBehaviors&quot; error
            Steve Skinner Community Member
            So, now I understand why there has never been a real solution for this problem. Adobe won't touch this issue.

            I just got off the phone with Adobe support, who told me they don't provide support for issues "like this". I thought there was some confusion, so I clarified the point by explaining again that the error is occurring within the software using its own native server behaviors. He did go so far to say that there is most likely corruption in the file(s), but would not give any guidance on how I could go about solving the problem or what to look for. Apparently their way of handling this situation is to claim that the customer some how corrupted their otherwise perfect code, and they don't support custom code issues. If it was custom code, I would certainly not argue that point at all, but the code in question is 100% generated by DW's own server behaviors. Am I crazy to expect support for this issue? I even told him that I would be happy to pay for a support case to get the assistance I need to solve the problem. Still, I got stone-walled. As a side note, I was completely calm and polite on the phone. In other words, I wasn't being a jerk. :-)

            With support like this, it just doesn't feel very good to keep forking over money for upgrades... Very few times have I needed to get help that couldn't be solved by the knowledge base or the forum. After the thousands I've paid through the years for Adobe web dev software, upgrades, extensions, etc., it's disappointing to know you can't really get the help you need when you need it most.

            So, in actuality, contacting Adobe seems to be the worst option. Just my 2 cents worth.