Hi All,
importing a survey and am having issues.
The import doesnt "finish" it just white screens. The url is back to just admin.php with no ?action=..

when opening the survey, I get:

Number of questions/groups: 1188/66

I have far more questions and groups

So..Have I hit a limit on amount of questions/groups?
or
have I hit some wierd timeout??

temp.csv:

and here is the template

tons of this:

[Mon Jul 14 15:15:24 2008] [error] [client xxx.xxx.xxx.xxx] PHP Warning: array_combine() [<a href='function.array-combine'>function.array-combine</a>]: Both parameters should have an equal number of elements in D:\WebRoot\limesurvey\admin\importsurvey.php on line 811, referer: lcs098/apps/limesurvey/admin/admin.php?action=newsurvey
[Mon Jul 14 15:15:24 2008] [error] [Mon Jul 14 15:15:24 2008] [error] [] PHP Warning: array_map() [<a href='function.array-map'>function.array-map</a>]: Argument #2 should be an array in D:\WebRoot\limesurvey\admin\importsurvey.php on line 812, referer: lcs098/apps/limesurvey/admin/admin.php?action=newsurvey

in the apache log

1188 question is VERY much. Which database do you use? The only limit which you might hit is a database limit. Please search the forum for more details on this, this has ben discussed before.

hey Mazi,
as always, thanks for the reply.

As I understand, reading prior to posting about question limitations in limesurvey, the main issue seemed to be the number of columns the question contained.

in our case, our columns are quite small, (not exceeding 1000), the issue is in regard to each question being represented as a row (with columns) in the database. MSSQL can handle 1000's of rows so I do not believe that to be the issue.

I think it is at least a few possibilities:
malformed csv (already posted with fake/nil data here)

a timeout from php of limesurvey or a failure in i/o throughput from web application to database

regardless,limesurvey fails silently with a white screen, the only error (posted) was from apache log

it would be great to not have to figure out the sequence of creating tables and directly inject them into the database from the "glue" app used to bind a list with questions

so the question still stands, is it something we did, or are trying to do that limesurvey just cant handle?

It is important to note, the rows that do make it in to the database, limesurvey displays that survey fine. This appears to be another import issue?

Well, the import is connected to a certain extern module. Maybe we have to search for the error there.

Furthermore there is a column for each question, check table lime_survey_12345. You can try to copy the survey using export/import and delete 100 questions. After that try again to see if the limit is reacher when using only 700/800/900 questions.

Ah!
getting closer.

So. The white screen "silent failure" happens on import before the survey is activated on a little over 1000 questions (1188 consistently make it in).. This shouldn't as it is writing into _questions as rows.. So that I think is still a bug in LS

lime_survey_12345 is created after and that appears to be the dilemma for questions mapping to columns, hence the limit.. Why does LS do it this way? We are trying to figure out a workaround.. what is each column used for?

wrobyn wrote:
So. The white screen "silent failure" happens on import before the survey is activated on a little over 1000 questions (1188 consistently make it in).. This shouldn't as it is writing into _questions as rows.. So that I think is still a bug in LS
Maybe you reach some server limit in this case? There are some settings like memory and timeout which can affect the import. Take a look at php.ini and try to raise limits.

lime_survey_12345 is created after and that appears to be the dilemma for questions mapping to columns, hence the limit.. Why does LS do it this way?
If you do it the other way round you might reach some limits when having > 1000/10000 answers. This limit would be reached earlier. Some users have > 10000 participants and only a very few have > 1000 questions.

Greetings,

Here my two cents opinion. According to my experience most white screen failure are due to syntax error in programs or lack of some server resource (max execution time, memory or max filesize request). I did some hack in version 1.71+(5448) to resolve similar problem in importsurvey.php, maybe it helps here.

First I put following lines in config.php

$cfg_memory_limit = "50M"; // Max script memory in megabytes
$cfg_max_execution_time = "600"; // Max script exec time in seconds
$cfg_max_filesize = "512000"; // Max file upload size in bytes

Then insert at beginning of importsurvey.php

ini_set("memory_limit","$cfg_memory_limit";
ini_set("max_execution_time","$cfg_max_execution_time";

And modify line 25 from

$buffer = fgets($handle, 56550);
to
$buffer = fgets($handle, $cfg_max_filesize);


Config values should be adjusted according to environment and file size. In my case these value fit most occasion, even a survey with around 250 groups, 350 questions and 2300 answers (290K survey file).

At last....remember those changes in case you upgrade version !!!

Hi,
thanks for the input..
What is really happening on our end is that we are in fact exceeding MSSQL column length (around 1024)

questions are store "horizontally" in pre LS2 database schema.. so this will physically cap the number of questions that can be imported..

I think if you created a survey with 2000 questions (the table in question) you would see the same result (white screen)

it is important to note that groups, and answers are stored pre LS2 (if I remember correctly) in "vertical" database tables so the amount of groups and/or answers (and even, theoretically survey K file size) dont really matter..

It was questions, and just finding the limit of LS1