View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
20637Bug reportsFile managerpublic2026-08-06 10:152026-08-07 10:59
ReporterJoshua Kuckherm Assigned Toc_schmitz  
PrioritynoneSeverityblock 
Status assignedResolutionopen 
Product Version7.0.x 
Summary20637: 500 Internal Server Error since Update
Description

Lime is very slow and i do not get new answers by participants. When I try to download the dataset for spss or excel i get the error "500 Internal Server Error". We had an update yesterday and i believe that we have the problems since then. Yesterday everything worked fine.

Steps To Reproduce

Steps to reproduce

(Replace this text with detailed step-by-step instructions on how to reproduce the issue)

Expected result

(Write here what you expected to happen)

Actual result

(Write here what happened instead)

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build) LimeSurvey Community Edition Version 7.0.8+260806
I will donate to the project if issue is resolvedNo
Story point estimate0
Browser
Database type & versionDon´t know
Server OS (if known)
Webserver software & version (if known)
PHP VersionDon´t know

Users monitoring this issue

There are no users monitoring this issue.

Activities

tibor.pacalat

tibor.pacalat

2026-08-06 12:24

administrator   ~85375

I can not reproduce the issue locally. Can you provide me with lsa file, maybe some data is causing server error?
tibor.pacalat

tibor.pacalat

2026-08-06 13:19

administrator   ~85380

Thank you for the lsa file. So I can export excel and spss successfully, excel takes a while and spss is rather quick. I could also go through your survey and submit response when I removed the end url.
I used MySQL database and php 8.3.20, not sure if this makes any difference, but it would be beneficial to know which database and php version are you using.
Joshua Kuckherm

Joshua Kuckherm

2026-08-07 10:59

reporter   ~85389

We reversed the update to version 6 and now it seems that everything works fine again. But we are still analysing the error, especially in the update process, because there are still some unanswered questions.

Issue History

Date Modified Username Field Change
2026-08-06 10:15 Joshua Kuckherm New Issue
2026-08-06 12:24 tibor.pacalat Note Added: 85375
2026-08-06 12:24 tibor.pacalat Bug heat 0 => 2
2026-08-06 12:33 Joshua Kuckherm Bug heat 2 => 4
2026-08-06 13:19 tibor.pacalat Note Added: 85380
2026-08-06 13:20 tibor.pacalat Bug heat 4 => 2
2026-08-07 10:36 c_schmitz Assigned To => c_schmitz
2026-08-07 10:36 c_schmitz Status new => feedback
2026-08-07 10:59 Joshua Kuckherm Note Added: 85389
2026-08-07 10:59 Joshua Kuckherm Bug heat 2 => 4
2026-08-07 10:59 Joshua Kuckherm Status feedback => assigned