PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Oops! We could not locate your form - no domain name change or transfer

  1. I had a really long and complicated form on my site. It was working wonderfully for weeks, but when I went to access it today I got the "Oops! We could not locate your form" error.

    I've run the meta recovery tool, to no avail. I just says the form could not be recovered.

    I haven't transferred the site or changed the domain name. I saw in another forum request here - - about this happening before without much input, but where that gentleman was able to recover from a database backup, I unfortunately do not have one.

    The form was pretty complicated and I had a bunch of custom styles that would take forever to try and replicate again, plus it had already been browser tested. Any ideas on how I can try and resolve this? Would provided the database entry for this help to troubleshoot?

    When I try and view the wp_rg_form_meta table in PHPMyAdmin, I get the following error:

    SQL query: 
    SELECT *
    FROM  <code>wp_rg_form_meta</code>
    LIMIT 0 , 30
    MySQL said: 
    #1030 - Got error 12 from storage engine
    Posted 11 years ago on Tuesday April 17, 2012 | Permalink
  2. Okay so through some troubleshooting I was able to figure this out.

    "#1030 - Got error 12 from storage engine " means "you don't have enough memory, or the specified memory settings for MySQL are too high for the configuration of your machine."

    So I deleted some data from my database (actually, I deleted an entire old database I no longer use), and the issue was fine.

    Hope that helps someone!

    Posted 11 years ago on Tuesday April 17, 2012 | Permalink
  3. David Peralty

    Glad to hear you were able to sort it out.

    Posted 11 years ago on Tuesday April 17, 2012 | Permalink

This topic has been resolved and has been closed to new replies.