Jotform Processing problem with CSV Files

  • Profile Image
    NATEX2013
    Asked on February 09, 2013 at 05:39 PM

    I am trying to download and process a CSV file from my form - using a direct URL link.

    The downloaded CSV file is giving all the error messages pasted below until finally producing the required lines of data.

    Please can you check what is going on.

     

    Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0

     

    Warning: include_once(): Unable to allocate memory for pool. in /etc/jotform/preLoader.php on line 22

     

    Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/index.php on line 2

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 76

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 76

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 179

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/AWSSDK/sdk.class.php on line 38

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 186

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 63

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 189

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 192

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 195

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 198

     

    Warning: include_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 201

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 63

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/LibraryLoader.php on line 61

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/LibraryLoader.php on line 61

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/LibraryLoader.php on line 61

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/LibraryLoader.php on line 61

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/classes/LibraryLoader.php on line 61

     

    Warning: include(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 237

     

    Warning: require_once(): Unable to allocate memory for pool. in /www/v3/builds/4bb14a06a7fe6b3a9aa324bcd4cb2317577197f1/lib/init.php on line 63

  • Profile Image
    NATEX2013
    Answered on February 09, 2013 at 05:43 PM

    Just to add that it seems to be working reliably now - hopefully was a temporary glitch in your processing?

  • Profile Image
    jonathan
    Answered on February 09, 2013 at 07:12 PM

    Hi,

    Thank you for updating us. It must be a temporary glitch related to network traffic performance.

    Glad to know it had resolved on your end and you are able to proceed.

    Please inform us immediately if this issue happen again.

    Thanks.