Method Community

 

Error Msg from webform

Last post 04-25-2011 4:28 PM by Method_Victor. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-25-2011 8:15 AM

    • ian
    • Top 100 Contributor
    • Joined on 07-13-2010
    • Posts 48

    Error Msg from webform

    I got an email from Method, it says, Normal 0 false false false EN-US ZH-CN X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

    Your client had encountered an error with web form CustomWebForm. This may be due to incorrect setup of the web form. The error encountered was: Transaction (Process ID 91) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

     

     

  • 04-25-2011 8:39 AM In reply to

    Re: Error Msg from webform

    Hi Ian,

    I am going to move this to the appropriate forum.

    -Michael

    Michael Melo
    Product Manager
    Method Integration Inc.
    Website: http://www.method.me
    LinkedIn: http://www.linkedin.com/in/MichaelMelo
  • 04-25-2011 4:28 PM In reply to

    Re: Error Msg from webform

    Hi Ian,

    The reason why you got this message is because there were few threads in database, trying to update the same database record at the same time. Since these threads weren't able to decide which transaction should it use, it simply failed. This problem is very very rare and you were unlucky enough to encounter it. I believe your web form is fine and you shouldn't receive the same error ever again.

    Sorry for the inconvenience,

    Victor

Page 1 of 1 (3 items)