Upgrading 1.15.8 to 1.16.x on Windows Server running IIS/8

arielzusya

I've been running OSTicket on a windows server with IIS/8.0, MySQL 8.0.19, and PHP 7.3.13. In prep for 1.17.x, I was working on moving to 1.16.x. I went to the Web Platform Installer in IIS and installed PHP 8.0 and it broke my OSTicket 1.15.8. I downgraded to 7.3.13 and it returned to working fine. I then tried just overwriting the 1.15.8 files with the current 1.16.x files and then switch the PHP version to 8.0 but it still was broken. If I then downgraded to 7.3.13 it would let me get to the SCP, but then it would tell me that I needed to upgrade to php 8.0 in order to upgrade to 1.16.x. If I switched the site at that moment to PHP 8.0 and refreshed the SCP page in my browser I'd be back to the 500 error. I feel like I'm missing something basic in the process here but I'm not sure what. Any thoughts? Thanks!

ntozier

I'm running a different version of IIS, but I have the same issue.
I spent a few hours trying to get this to work the other day and no real luck.
I don't think that the problem is osTicket however.

I manually installed php 8.0.21 VS16 NTS on my IIS 10 server and added the Handler mapper to point the site to the new version of PHP. Restarted the Site and IIS . Site displays a 500 error, and no php error log. I installed Microsoft Visual C++ 2015-2022 x64 Redistributable thinking okay new version of PHP need a newer version for it to work. Restarted the Site and IIS . Same issue. [note: yes I upgraded my osTicket files on the test site also].

I created a phptest.php and put <?php phpinfo(); ?> in it and go to it and get a PHP configuration screen.
Rechecked my Handler Mappings. killed the App Pool and made a new one. Edited the site to use the new one. Restarted the Site and IIS. Same issue.

Decided okay fine, and use WPI to install PHP 8.0.0. Checked the Handler Mappings. Restarted the Site and IIS. Same issue.

Needless to say if you get any brilliant ideas please let me know. 🙂

arielzusya

ntozier Thanks for confirming that I am not the only one. So far I have no solutions (creative or otherwise). Right now I'm playing with the idea of spinning up a VM running Ubuntu and installing a fresh copy and then moving the DB but I've never tried that before. I'd rather find a way to keep it where it is because I've got a lot of tangential systems configured on that server that support the deployment (like letsencrypt and such). While we wait to see if there is anyone else who has come up with a solution and posts it here, I'll ask--

If I move the DB from a 1.15.8 installation on mysql on a windows server to a MariaDB install of mysql on a ubuntu server running 1.16.3, is it simply a matter of exporting the db from one and importing it into the other or is there more (assuming username and password in config are the same)?

ntozier

arielzusya 'm playing with the idea of spinning up a VM running Ubuntu and installing a fresh copy and then moving the DB but I've never tried that before.

That's actually what I ended up doing. I'm just waiting for the ST to be released before I re-migrate the DB again and run stable.

Side note, I also run letsencrypt.