Kindly assist with this error: Fail to import questionnaire to Headquarters. Please contact support to resolve this problem
Do you know the version of the Survey Solutions software installed on the server?
Does the questionnaire compile in the Designer without errors?
Please let us know if there are any relevant records in the server’s error log around the time you’ve attempted to import the questionnaire.
Hi, I’m having the same problem but the form compiles without errors. The server has recently been upgraded and works fine on other surveys. Please assist
(SERVER IS: https://50x2030methods.worldbank.org/)
Server Version is 23.06.1 upgraded two months ago with ESRI extension
Possible this is due to the amount of attachments on this form? ~90MB
Hello @emass1991 ,
thank you very much for reporting the issue. We have reproduced the issue with a large attachment:
Best, Sergiy
@emass1991 , could you please re-check if the issue with importing a questionnaire with a large attachment from Designer to HQ is still present?
Also, if anyone else has experienced this issue after 21 August 2023, please write details here.
Thank you, Sergiy
Dear Sergiy,
I’m experiencing the same issue , this time with a questionaire with only 1 text question (a test questionnaire). The questionnaire compiles without any errors. The version installed is number 23.09.1 (build 35025).
What does the error log say?
As shown in the image, the error message was: “Fail to import questionnaire to Headquarters. Please contact support to resolve this problem” .
This problem disappeared after rebooting the server. We didn’t anything more than rebooting windows server.
That is the error message shown to the user. It contains no explanation on the reasons why the problem has occurred. See Application log files.
Hi, I’m also having the same problem but the form compiles without errors. There’re notification, “new version available”. So, do we should update our server? Please assist., thank you
That is the error message shown to the user. It contains no explanation on the reasons why the problem has occurred. See Application log files .
Update the server to the latest version before getting the logs.
Also, your screenshot shows http:// protocol is used instead of https://. This shouldn’t be used in production for security reasons.
thank you sergiy, its solved after we updated the version.
Great! Thank you for confirming!