I am having trouble with moving an existing PSW 2.2.0 install to a new server. I purchased a new server with Win2k3 R2 and ran all updates/patches. I then installed PSW 2.2.0 - which didn't like the fact that I had already updated the .NET 2.0 to SP1. It wanted to try and install that patch but it failed (because I had already updated to a newer version). It gave me the option to continue which I did and it all seemed to install just fine.

I then copied over the files mentioned in the "Important update notes" section of the v2.2.1 release notes regarding creating a backup. This brought over all our data and user accounts (but didn't bring the image collection over - we have just one). I figured it wasn't a big deal and I would find a way or just rebuild it from scratch so I moved on...

I then ran the v2.2.1 installer which finished fine. I went through the firstrun process and everything went find. When it finished, I could log in and it seems that everything was there (except the image collection). I then tested the SSL connection and found it wouldn't even report a server available (I was expecting the SSL certificate warning).

I took a look at the http.conf file in the Apache folder and saw that it looked a bit different than the copy from v2.2.0. I spotted that the mod_ssl switch didn't exist (I chose SSL in the setup but not bind to localhost) so I copied it over from the v2.2.0 conf file and was then able to connect using SSL. However, it wouldn't load any pages and kept saying that the page couldn't be found.

Any ideas? The ssl.conf looks to be the same as the old version and I am just using the test SSL cert until it is all setup then will get a Verisign (or other) certificate.

Thanks,

Max

Good morning Max,

As we'll need to take a look at the configurations of Apache and Windows in detail (in paticular the http.conf file), could you please open a support ticket and attach this file along with your request?

This will simplify the troubleshooting greatly.

Thank!
Eric.

Thanks Eric, issue # is 78926

Thanks Claude, the fixed files you emailed worked... I only found 2 differences in the new/fixed ssl.conf file;

missing line 4:
DocumentRoot "C:\Program Files\PrintShop Web\Website"

and line 154 was commented out (regarding CustomLog)

Is that all that was changed?

The changes were made by one of our programmers, and I dont know what other changes were made to the file.

Thanks for the feedback!

In the ssl.conf line 4 was the real fix the change on line 154 doesn't effect the problem but keeps the log files more clean.

However I also changed a line in your httpd.conf file. I uncommented the LoadModule line for the ssl module. This way Apache will load the ssl module.

Those where the only changes that where necessary.

Thanks Robbie, I had commented the load module out because it wasn't working - that line didn't exist in the http.conf after the upgrade from 2.2 to 2.2.1 so I added it myself to try and fix the problem.

So if anyone else has this problem;

add the following line to the http.conf after the php5_module;
LoadModule ssl_module modules/mod_ssl.so

Then in the ssl.conf file add the following after the ServerName line;
DocumentRoot "C:\Program Files\PrintShop Web\Website"

That should fix it right up!

I have found the solution for the image collection (and other problems discovered while investigating).

It seems that the InnoDB tables were not working correctly after the upgrade to 2.2.1

I used MySQL Administrator to examine the tables which reported as being missing. So I manually removed the tables (by deleting the .MYD .MYI .FRM files). I then created a full backup from our existing 2.2 installation and "restored" to the new server selecting the option to create tables that don't exist.

This regenerated the tables and the image collection is working now.

We also had trouble were the PDF's would not display and kept reporting a problem with the render_image.php which has been resolved by fixing the InnoDB problem.

Found another problem - when I am placing a test order and go to edit the Shipping Address...

I use the drop down to choose a new department and the old server would automatically populate the appropriate address. The new server is not doing this and keeps whatever values are already there.