Fehlerbehebung

The following wiki section is the result of the work of multiple LimeSurvey community members. For more up-to-date information, check the LimeSurvey forum. For professional support, contact one of our LimeSurvey authorized partners: https://limesurvey.com.

Allgemeines

Diese Seite listet typische technische Probleme und Ihre Lösungen auf, die nach einer erfolgreiche Installation auftreten können. Wenn Sie Hilfe brauchen, um Probleme zu beheben, die während der Installation auftreten, schauen Sie bitte in die Installations-FAQ.

Beim Öffnen der Administrations-Anmeldungsseite

Fehlermeldung: "No input file specified" nach der Installation

Während der Installation versucht LimeSurvey die beste Lösung für das URL-Format zu finden. Manchmal funktioniert das nicht richtig.

Um LimeSurvey zu zwingen ein anderes URL-Format zu verwenden, müssen Sie die Konfigurationsdatei bearbeiten.

In /application/config/config.php ersetzen Sie

     'urlFormat' => 'path',			

durch dies:

     'urlFormat' => 'get',

Then try to open the administration panel by using the short admin URL:

   http://<yourserver.net>/<limesurvey_dir>/admin

Nach der Anmeldung in der Administration

Jegliche Aktion in der Administration führt zum Anmeldebildschirm

Dies kann aufgrund folgender Hauptgründe passieren:

• PHP Session Probleme
• UTF-8 Kodierungsprobleme
• Internet Explorer (6,7 und 8) Probleme

PHP Sessions:

1. Überprüfe/aktualisiere die Einstellungen upload_tmp_dir und session.save_path in der php.ini
2. Lege die konfigurierten Verzichnisse an
3. IIS: Weise Berechtigungen dem IIS Gastzugang zu, dass diese Verzeichnisse beschrieben werden dürfen
4. Apache: Stelle sicher, dass der Webserver Schreibberechtigungen in diese Verzeichnisse hat
5. Überprüfe ob die Einstellung "session.use_cookies" in der php.ini auf 1 gesetzt ist. Wenn nicht, dann setzen.
6. Überprüfe ob die Einstellung "session.auto_start" in der php.ini auf 0 gesetzt ist. Wenn nicht, dann setzen.

Internet Explorer issues LimeSurvey does not support any longer the access to the administration interface via Internet Explorer.

UTF8-Codierung

Wenn Sie eine Datei bearbeiten (höchstwahrscheinlich ist dies config.php), dann speichern Sie diese nicht im UTF-8 Format. Speichern Sie PHP-Dateien immer im ANSI/ISO Zeichensatz. Seit Version 1.87 können sie die meisten Einstellungen innerhalb der Applikation in den Globalen Einstellungen vornehmen (wie z.B. Site-Name, Administrator-Name usw.)

Nach dem Absenden einer Seite mit einer großen Anzahl an Fragen/Antworten/Unterfragen werden die Teilnehmerantworten nicht gespeichert

There was a new setting introduced in PHP 5.3.9 (and was even backported to some earlier PHP versions): max_input_vars. This setting limits the maximum number of variables that can be POSTed (submitted) to the server. Default is set to 1000 but if you have a question with lots of answer options or a survey page with lots and lots of questions/answers this limit might be exceeded. You will need to set this in your PHP configuration file (php.ini).

Dates are not correctly displayed using MSSQL Server with FreeTDS on Linux

Locate the locales.conf file of FreeTDS and edit it. If you do not have any other applications using FreeTDS, just replace the contents with

[default]
    date format = %Y-%m-%d %H:%M:%S.%z

If you have other applications using FreeTDS, you might want to check first what locale you need to edit.

Save and restart the server. Dates should now be shown properly. If this does not work, you might have edited the wrong file - rinse and repeat.

When I am entering special chars (Chinese, Cyrillic, Greek, Arabic) into my survey or administration , every character is shown as a question mark?

This happens if your database itself is not created to use an UTF-8 charset. This can happen when you have to create the database using a provider administration panel. You can fix this problem by executing the following SQL command on your database (using for example phpMyAdmin) ALTER DATABASE `<your_database_name>` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

Replace <your_database_name> with the name of your database. You need to do this before installing LimeSurvey.

PageSpeed creates some troubles to Limesurvey

You should include ModPagespeed off in your LimeSurvey virtualhost.

Otherwise, you will not be able to use ConfortUpdate, neither export data. Probably something else is going to fail.

Während eine Umfrage ausgefüllt wird

Fehler "Sitzung ist abgelaufen"

Sie könnten an einer Stelle eine Meldung bekommen wie:

FEHLER

Es tut uns leid, aber Ihre Sitzung ist abgelaufen.

Entweder waren Sie zu lange inaktiv, Sie haben Cookies für Ihren Browser deaktiviert, oder es gab Probleme mit Ihrer Verbindung.

Und wenn Sie Suhosin auf Ihrem Server aktiviert haben, könnte das der Grund sein, warum Sie diese Meldung während einer Umfrage gezeigt bekommen.

Hinweis: Wenn Ihre Umfrage nicht aktiv ist, könnte der Fehler sich anders äußern, z.b. dass Sie zur öffentlichen Liste der Umfragen umgeleitet werden. Die Lösung ist aber die gleiche.

Suhosin is an advanced protection system for PHP installations but the Suhosin default configuration can create troubles with LimeSurvey.

First, check and test using the Suhosin log by setting suhosin.log.sapi = 511 and suhosin.simulation = on according to the Suhosin documentation.

The configuration file is usually located in /etc/php5/apache2/conf.d/suhosin.ini, but to be sure you can check your phpinfo (LimeSurvey administration > Global Settings > Button Show phpinfo > Line : "Additional .ini files parsed") to get the correct path.

Don't forget to restart your Apache/Nginx server for the parameters to be taken into account (service apache2 restart or service nginx restart).

When the simulation is on, Suhosin is not blocking anything and the errors are reported into the logs (usually in your system log: /var/log/syslog). If you get an error messages such as "ALERT-SIMULATION - configured POST variable limit exceeded" that's Suhosin alerting...", try the following configuration (which seems to work well with LimeSurvey):

suhosin.memory_limit = 128
suhosin.post.max_value_length = 5000000
suhosin.post.max_vars = 5000
suhosin.request.max_value_length = 5000000
suhosin.request.max_vars = 5000

Mit diesen Parametern sollten Sie in der Lage sein, die Einstellung suhosin.simulation zurück auf den "off"-Wert zu stellen (so dass der Server geschützt ist und LimeSurvey immer noch funktioniert).

The default values of Suhosin are not working well with LimeSurvey. If you really want to secure your server tightly, you might want to use the simulation mode to tune the setting and find the good values between 1000 and 5000 for the vars and 1000000 and 5000000 for the value_lengths.

Note: There was an additional PHP setting introduced recently which needs to be tweaked, too: max_input_vars - this setting is the same as suhosin.post.max_vars but needs to be set separately in php.ini.

Ich kann die Sprache nicht ändern!

No matter what language you choose, the interface (admin and user) are always displayed in the English language. Normally, this is caused by a bug in your PHP version. There is no other fix for this than updating your PHP version.

Some common errors (IIS focused)

Index.php won't open

Possible cause: This might happen if you haven't installed the necessary extensions

• You need to install Multi-byte string and MSSQL (or MySQL) extensions

Possible cause: ISAPI filter not configured

• In IIS, for the website (you could do it at the directory level) you must configure it to use php5isapi.dll

Index.php won't open and "php.exe -i" gives error messages about missing .dll's

This may happen if you install too many extensions

• If you install all PHP extensions, PHP will fail because not all dependencies were met (e.g., the oracle package needs oracle dll's)
• Install only the extensions you need
• To test, try running php.exe -i from the command line

Message stating database was missing

This may happen if you navigate to wrong url:

• Make sure you go to limesurvey/admin/install/index.php instead of limesurvey/index.php !

Above fixes do not solve the problem

This may happen if you have not restarted IIS

• Restart IIS

Things that are easy to forget:

• .php needs to be associated to filter php5isapi.dll
• limesurvey/tmp directory needs writing permission for survey uploads
• updating doc_root in php.ini and $rootdir in config.php

Missing files ("No such file or directory")

When uploading LimeSurvey to your server it might happen that the connection is interrupted so that some files are not transferred or not transferred completely. Depending on the files, you can get different error messages whenever you access different features/parts of LimeSurvey. The missing files throw errors look like this:

"Warning: require_once(/path/to/your/limesurvey/installation/filename) [function.require-once]: failed to open stream: No such file or directory in /path/to/your/limesurvey/installation/filename on line 12345" OR

"Fatal error: require_once() [function.require]: Failed opening required 'require_once(/path/to/your/limesurvey/installation/filename)' (include_path='.:/x/y/z) in /path/to/your/limesurvey/installation/filename on line 12345"

Lösung

1. Löschen Sie alle hochgeladenen Dateien.

2. Laden Sie die Dateien erneut hoch.

(3. Wenn notwendig: Nochmals neu installieren)

After submitting a page, you end up on the general index page/on a 404 page or you get the message 'The CSRF token could not be verified'

or

After clicking 'Next' on a page which contains a big number of answers/subquestions, not all responses are being saved

or

After clicking 'Next', I end up on the same page

or

Using the quick translation system doesn't save answers or subquestions

or

When exporting a big number of response fields, not all of them are being exported

• This is most likely because of a limiting setting in your webserver: max_input_vars . This setting limits the maximum number of variables that can be POSTed (submitted) to the server.

Default is set to 1000, but if you have a question with lots of answer options or a survey page with lots and lots of questions/answers, this limit might be exceeded. You will need to edit your PHP configuration (php.ini).

• Also, check your PHP settings if your host is using the Suhosin extension for Apache which may be set to be too limiting on a couple of settings.

• For example, the two settings "suhosin.post.max_vars" and "suhosin.request.max_vars" are both set to a value of 200 by default. Increase those settings both to 400 or higher so users can complete and submit long surveys.

• If you still have problems, try switching the module to simulation_mode (and so basically deactivate it), as the maximum value always depends on your particular survey.

• Another reason might be a proxy or a similar software which does not allow big post requests or requesting the same page several times in the background (which leads to a new CSRF-key being created). Try a different internet connection in this case.

No questions are shown when using MSSQL Server with FreeTDS on Linux

If you check carefully any question group there is a space in the group relevance which makes the entire group non-relevant. The underlying problem is that your FreeTDS returns spaces on empty fields because of a misconfiguration. You can fix this problem by forcing the FreeTDS protocol version to at least 8.0. So, edit freetds.conf (e.g. /etc/freetds/freetds.conf) and change the respective line to

    tds version = 8.0

That should fix this issue.

After taking the survey

Texts that were entered by the participant appear as question marks in the results

This happens if your database itself does not by default use an UTF-8 charset. This can happen when you have to create the database using a provider administration panel. You can fix this problem by executing the following SQL command on your database (using for example phpMyAdmin):

   ALTER DATABASE `<your_database_name>` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

Replace <your_database_name> with the name of your database. After you did that, deactivate your survey and activate it again.