Dear Folks!I have Problems with version 1.10 right after the installation. I tried it three times. always deleting and rebuilding the database and webserver files.Details on the server: Webspace from german hoster strato.deosTicket-Version v1.10 (901e5ea) — Up to dateServer-Software Apache/2.2.31 (Unix)MySQL-Version 5.6.33PHP-Version 5.6.27there are php-mods missing: intl, APCu (can't fix it)i also included german language packAfter i filled the forms on the /setup/ page it left me with a blank page. I thought that the routine had accomplished its tasks successfully, since there were no errors shown.I continued deleting /setup/ and removed write access from /include/ost-config.php.So far no problems. I could also log in, specify all necessary email options and add a colleague. Password Reset worked as well as sending emails over smtp.Next step would be to add a Organisation, but the form lacked a field for the organisation name. then there was one organisation "osTicket".I even tried to add a user, but after i clicked on Add User the backend left me with a rotating loading animation.The mailsystem sent me multiple error reports as given in the attached txtAm i doing it wrong?Hope you can help me ^^

[Errormessages.txt](https://forum.osticket.com/assets/files/migrated/FileUpload/69/98cf6a506dae15f526c89c429fc23c.txt)

Language packs for 1.10 have not been release yet to my knowledge so you might want to swtich back to English and see if you encounter the same issues.  Once you do if you are still having the same issues then it sounds to me like your host is blocking AJAX calls.  You might want to consult your error log and talk to them.  It's like a mod_security rule or SELinux.FYI I do not see any attachments on this thread.

Run this manually:CREATE TABLE IF NOT EXISTS `ost_ticket__cdata` (PRIMARY KEY (ticket_id)) DEFAULT CHARSET=utf8 AS SELECT entry.`object_id` as `ticket_id` FROM ost_form_entry entry JOIN ost_form_entry_values ans ON ans.entry_id = entry.id JOIN ost_form_field field ON field.id=ans.field_id WHERE entry.object_type='T' GROUP BY entry.object_id;Problem is that you had extra comma "SELECT entry.`object_id` as `ticket_id`,  FROM", thus the query failed. Error 1146 is just a symptom of 1064 I believe. This still should be reported to devs though, without investigating further, I can't really say why you have this issue :)

Write a Reply...