Cannot upgrade from v1.6 ST to v 1.8.0.2: Page 2

Cannot upgrade from v1.6 ST to v 1.8.0.2

sf395

I will in successive posts show you my error messages. I get to the loading attachments stage by performing the followingdelete from ost_team where team_id > 0;alter table ost_team auto_increment=1;drop table ost_canned_response;drop table ost_group_dept_access;drop table ost_filter;drop table ost_filter_rule;It's probably easier if I attach screenshots in successive posts

sf395

It is after this that I dodelete from ost_team where team_id > 0;alter table ost_team auto_increment=1;drop table ost_canned_response;drop table ost_group_dept_access;drop table ost_filter;drop table ost_filter_rule;

sf395

Sorry, I made a mistake in the order of my uploads but I couldn't seem to either delete a draft of an inserted image.I created 4 extra tables in my 1.6 installation to handle products and versions and I altered ost_ticket to include a customer attribute.I cannot risk upgrading my production system if the upgrade process is so apparently hit and miss.

sf395

My production system is a Debian 6, 64 bit server running xampp. I'm testing the upgrade on a laptop running Linux Mint 16, 64 bit and separate Apache2.4, MySQL and PHP. I have set up a virtual host on Apache to mirror the same directory structure as the xampp installation on the production server

ntozier

I would recommend that you contact commercial support services.http://osticket.com/commercial-supportI've done at least 50 upgrades/installs at this point and only once had any real problem (which was fixed by restoring my database, changing a php file to alter the system path main.inc.php and re-running the upgrader). My guess is that is has something to do with your specific setup and any changes that you made to your database.

sf395

Hello,

I'm trying to find out what, if any changes anyone else had made. I shall try dropping the extra tables I created and the extra columns I added to ost_ticket, save the database and then retry.

However, you dais above that you "changed a php file to alter the system path main.inc.php". Can you tell me what you changed?

Thanks

sf395

HelloI'm pretty sure I've sorted the issue which was to do with my database import. If the upgrade fails at some stage then importing the dump of the old osticket 1.6 database doesn't get rid of any newe tables created by the upgrade so far. Hence my database issues.It all seems OK but there are about 100 or so attachments to import and this appears to be taking some time. Currently I'm sitting here waiting with this screen. I'll see when (if) it finishes blank

ntozier

Correction it wasn't main.inc.php that I changed. It was bootstrap.php.I doubt that the change I made will be of use to you. That installation runs under Windows and IIS.Line 265//define('INCLUDE_DIR', 'INCLUDE_DIR/'); // Set by installerdefine('INCLUDE_DIR', ROOT_DIR . 'include/'); // Set by ntozierI commented the line out and added the // Set by ntozier line.

sf395

Ok. I've got further. It stopped at the stage in my last post so I logged off, dumped the current database, deleted the current database and re-created it from the dump. Went to the osticket/scp page and continued the upgrade which completed successfully. However, I may have lost a few tickets.

sf395

It looks OK now. I'm not really happy with the fact that it failed and then completed as described in my previous post. I did the upgrade on a snapshot of the database taken over the weekend and I

think it worked this time because I dropped a view that I had created and I removed two bespoke columns that I had

created from the "ost_ticket" table.Two questions and then I think that's it for now.1) The live database has changed since the weekend. Do I have to do a full upgrade again or can I perform an incremental one?2) Can you point me to any technical documentation as to the php etc. files that make up the new release and which ones from 1.6 SC are no longer needed or have been changed. For example I notice that viewticket.inc.php is now ticket-view.phpThanks

ntozier

1. you would have to do a full upgrade again.2. read the UPGRADING.txt included in the archive.

sf395

OK. I'm just working on some bespoke amendments to the code. I'll try a full upgrade again with these amendments in place.Can I close this and re-open it if necessary?

sf395

BTW: When it stopped during the installation that eventually succeeded the system logs reported that "The AttachmentMigrater task reports

there is work to do".What does that mean, or rather what is there to be done to complete the upgrade?

ntozier

Can I close this and re-open it if necessary?

Once a thread is closed, its closed. If you have additional issues just start new thread.What does that mean, or rather what is there to be done to complete the upgrade?

I would imagine that the upgrader thinks that it has to migrate files from the filesystem to the database. Which since your going from 1.6 to current, it does if you have any attachments on any tickets.

« Previous Page