MAILBEE POP3 SMTP WEBMAIL IMAP4 POP IMAP EMAIL COMPONENT VB ASP ACTIVEX COM VBA OCX NET .NET C# VB.NET ASP.NET DOWNLOAD QUEUE SSL SECURITY CENSOR ACCESS PARSER C++ DLL CONTROL LIBRARY MIME INTERFACE

AfterLogic WebMail Pro

AfterLogic Forum : AfterLogic WebMail Pro

Topic: upgrade problem from v 7.7.9 on 8.3.5

Author

Message

<< Prev Topic | Next Topic >>

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 20 July 2019 at 6:05am \| IP Logged

Hello,
I am trying to upgrade from 7.7.9 to 8.3.5
I don't have cplanel.
I use https://afterlogic.com/docs/webmail-pro-8/installation/migration-from-v7
I edited dev / migrate.php

I created a new database. Logged into the admin environment and set: Database settings: SQL login, SQL password, Database name, Host.
Test connection: OK
I click: Create/Update tables and Update configuration

after startup migrate.php
I have an error: Error during connection to p7 DB.

Do you think of anything?

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 20 July 2019 at 6:40am \| IP Logged

I also once received a buzz:

Deleting tables before moving
Moving tables from p7 DB to p8 DB
-----------------------------------------------
Error during migration process. For more detail see log-file.

where I find log?

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 22 July 2019 at 1:52am \| IP Logged

Quote:

after startup migrate.php
I have an error: Error during connection to p7 DB.

Make sure $sP7ProductPath correctly points to v7 installation location, and that data/settings/settings.xml file there holds valid connection details for the database used by v7 installation.

Quote:

Error during migration process. For more detail see log-file.
where I find log?

Please see Troubleshooting section of the migration guide:

Quote:

During the migration, script creates a number of files under data directory:
...
Also, if logging was enabled in admin area, log files are created under data/logs directory, their filenames start with migration-.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 27 July 2019 at 6:12am \| IP Logged

migration log:

[13:09:42.69][4bba9b9a] [GET][ip:192.168.42.101] /webmail-new/dev/migrate.php?pass=XXXXXXX^M
[13:09:42.69][4bba9b9a] POST > []^M
[13:09:42.69][4bba9b9a]^M
[13:09:42.69][4bba9b9a] P8 tables list before upgrade: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes^M
[13:09:42.69][4bba9b9a] Deleting tables from P8 DB: DROP TABLE IF EXISTS `au_adav_addressbookchanges`,
                                `au_adav _addressbooks`,
                                `au_adav _cache`,
                                `au_adav _calendarchanges`,
                                `au_adav _calendarobjects`,
                                `au_adav _calendars`,
                                `au_adav _calendarsubscriptions`,
                                `au_adav _cards`,
                                `au_adav _groupmembers`,
                                `au_adav _locks`,
                                `au_adav _principals`,
                                `au_adav _propertystorage`,
                                `au_adav _reminders`,
                                `au_adav _schedulingobjects`,
                                `au_adav _calendarinstances`
                        ^M
[13:09:42.69][4bba9b9a] P8 tables list after delete operation: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes^M
[13:09:42.92][4bba9b9a]     Table: adav_addressbooks. Migration started^M
[13:09:43.46][4bba9b9a]     Table: adav_addressbooks. Migrated successfully^M
[13:09:43.56][4bba9b9a]     Table: adav_cache. Migration started^M
[13:09:43.56][4bba9b9a]     Table: adav_cache. Migrated successfully^M
[13:09:43.63][4bba9b9a]     Table: adav_calendarobjects. Migration started^M
[13:09:43.69][4bba9b9a]     Table: adav_calendarobjects. Migrated successfully^M
[13:09:43.79][4bba9b9a]     Table: adav_calendars. Migration started^M
[13:09:44.03][4bba9b9a]     Table: adav_calendars. Migrated successfully^M
[13:09:44.10][4bba9b9a]     Table: adav_cards. Migration started^M
[13:09:49.78][4bba9b9a]     Table: adav_cards. Migrated successfully^M
[13:09:49.85][4bba9b9a]     Table: adav_groupmembers. Migration started^M
[13:09:49.85][4bba9b9a]     Table: adav_groupmembers. Migrated successfully^M
[13:09:49.92][4bba9b9a]     Table: adav_locks. Migration started^M
[13:09:49.92][4bba9b9a]     Table: adav_locks. Migrated successfully^M
[13:09:50.10][4bba9b9a]     Table: adav_principals. Migration started^M
[13:09:50.54][4bba9b9a]     Table: adav_principals. Migrated successfully^M
[13:09:50.72][4bba9b9a]     Table: adav_reminders. Migration started^M
[13:09:50.72][4bba9b9a]     Table: adav_reminders. Migrated successfully^M
[13:09:51.16][4bba9b9a] DAV tables was renamed.^M
[13:09:51.23][4bba9b9a] Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0
Connecting to database: mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8^M

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 29 July 2019 at 1:32am \| IP Logged

Quote:

13:09:51.23

Anything in the main debug log around that timestamp?

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 29 July 2019 at 11:12am \| IP Logged

Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0

could not be a problem in the outdated database schema?

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 30 July 2019 at 1:54am \| IP Logged

Not sure, I'll check with the developer who created the migration script, will get back to you once there's a response. Due to vacation season, it'll be a while.

Also, if you wish to get support from Afterlogic team directly, it's recommended to contact us via Helpdesk - and make sure your maintenance contract is up-to-date.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 04 August 2019 at 11:01am \| IP Logged

Thanks for the reply. I'll wait :)

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 05 August 2019 at 3:01am \| IP Logged

Just heard from the developers on this. It looks like the v8 database was missing quite a lot of tables before the migration started: au_adav_addressbooks, au_adav_cache, au_adav_calendarchanges and so on. We're not sure what and where exactly went wrong there, and to narrow it down, we recommend deleting all the tables from the v8 database, then click Create Tables in v8 installation and see if those au_adav_* tables actually get created. And if they do, delete the data/migration file and restart the migration script.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 12:30am \| IP Logged

Hi Igor:
I removed the entire webmail-new directory (it was with version 8)
I deleted the entire AFTERLOGIC_DBv8 database
I created a new empty database AFTERLOGIC_DBv8
I unpacked the downloaded archive with a new version of webmail

After: "Create/Update tables"
mysql> show tables;
+------------------------------+
| Tables_in_AFTERLOGIC_DBv8    |
+------------------------------+
| au_eav_attributes_bigint     |
| au_eav_attributes_bool       |
| au_eav_attributes_datetime   |
| au_eav_attributes_double     |
| au_eav_attributes_int        |
| au_eav_attributes_mediumblob |
| au_eav_attributes_string     |
| au_eav_attributes_text       |
| au_eav_entities              |
| au_min_hashes               |
+------------------------------+
10 rows in set (0.00 sec)

after: edit migrate.php:
I setup:
$sP7ProductPath = "/var/www/webmail";
$sPassword = "MyPASS";

I run in IE or Firefox, It's the same: https://xxx.xxx.xxx.xxx/webmail-new/dev/migrate.php?pass=MyPASS

Deleting tables before moving
Moving tables from p7 DB to p8 DB
-----------------------------------------------
Error during migration process. For more detail see log-file.

there is log migration-log-2019-08-09.txt:

[07:22:06.10][78ddc267] [GET][ip:192.168.42.101] /webmail-new/dev/migrate.php?pass=MyPASS
[07:22:06.10][78ddc267] POST > []
[07:22:06.10][78ddc267]
[07:22:06.10][78ddc267] P8 tables list before upgrade: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[07:22:06.10][78ddc267] Deleting tables from P8 DB: DROP TABLE IF EXISTS `au_adav_addressbookchanges`,
                                `au_adav _addressbooks`,
                                `au_adav _cache`,
                                `au_adav _calendarchanges`,
                                `au_adav _calendarobjects`,
                                `au_adav _calendars`,
                                `au_adav _calendarsubscriptions`,
                                `au_adav _cards`,
                                `au_adav _groupmembers`,
                                `au_adav _locks`,
                                `au_adav _principals`,
                                `au_adav _propertystorage`,
                                `au_adav _reminders`,
                                `au_adav _schedulingobjects`,
                                `au_adav _calendarinstances`

[07:22:06.10][78ddc267] P8 tables list after delete operation: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[07:22:06.40][78ddc267]     Table: adav_addressbooks. Migration started
[07:22:07.03][78ddc267]     Table: adav_addressbooks. Migrated successfully
[07:22:07.14][78ddc267]     Table: adav_cache. Migration started
[07:22:07.14][78ddc267]     Table: adav_cache. Migrated successfully
[07:22:07.21][78ddc267]     Table: adav_calendarobjects. Migration started
[07:22:07.24][78ddc267]     Table: adav_calendarobjects. Migrated successfully
[07:22:07.31][78ddc267]     Table: adav_calendars. Migration started
[07:22:07.51][78ddc267]     Table: adav_calendars. Migrated successfully
[07:22:07.60][78ddc267]     Table: adav_cards. Migration started
[07:22:12.46][78ddc267]     Table: adav_cards. Migrated successfully
[07:22:12.53][78ddc267]     Table: adav_groupmembers. Migration started
[07:22:12.53][78ddc267]     Table: adav_groupmembers. Migrated successfully
[07:22:12.60][78ddc267]     Table: adav_locks. Migration started
[07:22:12.60][78ddc267]     Table: adav_locks. Migrated successfully
[07:22:12.66][78ddc267]     Table: adav_principals. Migration started
[07:22:12.93][78ddc267]     Table: adav_principals. Migrated successfully
[07:22:13.00][78ddc267]     Table: adav_reminders. Migration started
[07:22:13.00][78ddc267]     Table: adav_reminders. Migrated successfully
[07:22:13.24][78ddc267] DAV tables was renamed.
[07:22:14.12][78ddc267] Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0
Connecting to database: mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8

There is mysql tables now:
mysql> show tables;
+------------------------------+
| Tables_in_AFTERLOGIC_DBv8    |
+------------------------------+
| addressbooks                 |
| au_eav_attributes_bigint     |
| au_eav_attributes_bool       |
| au_eav_attributes_datetime   |
| au_eav_attributes_double     |
| au_eav_attributes_int        |
| au_eav_attributes_mediumblob |
| au_eav_attributes_string     |
| au_eav_attributes_text       |
| au_eav_entities              |
| au_min_hashes               |
| cache                        |
| calendarobjects              |
| calendars                    |
| cards                        |
| groupmembers                 |
| locks                        |
| principals                   |
| reminders                    |
+------------------------------+
19 rows in set (0.00 sec)

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 09 August 2019 at 12:53am \| IP Logged

Thank you, developers will have it analyzed, just one quick question please - what's the exact v8 version number? The latest currently available one is 8.3.7; I understand this started from 8.3.5 but there's a good chance the issue is resolved with the upgrade to the latest release. Thanks.

--
Regards,
Igor, Afterlogic Support

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 09 August 2019 at 12:55am \| IP Logged

Just to clarify - if you switch over to the latest version, for now please just check if the complete set of tables is created there, and let us know. Thanks.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 1:54am \| IP Logged

I downloaded a new version, but I have the same problem

Deleting tables before moving
Moving tables from p7 DB to p8 DB
-----------------------------------------------
Error during migration process. For more detail see log-file.

[08:51:57.24][d935b4d7] P8 tables list before upgrade: au_adav_addressbookchanges, au_adav_addressbooks, au_adav_cache, au_adav_calendarchanges, au_adav_calendarinstances, au_adav_calendarobjects, au_adav_calendars, au_adav_calendarsubscriptions, au_adav_cards, au_adav_groupmembers, au_adav_locks, au_adav_propertystorage, au_adav_reminders, au_adav_schedulingobjects, au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[08:51:57.93][d935b4d7] Deleting tables from P8 DB: DROP TABLE IF EXISTS `au_adav_addressbookchanges`,
                                `au_adav _addressbooks`,
                                `au_adav _cache`,
                                `au_adav _calendarchanges`,
                                `au_adav _calendarobjects`,
                                `au_adav _calendars`,
                                `au_adav _calendarsubscriptions`,
                                `au_adav _cards`,
                                `au_adav _groupmembers`,
                                `au_adav _locks`,
                                `au_adav _principals`,
                                `au_adav _propertystorage`,
                                `au_adav _reminders`,
                                `au_adav _schedulingobjects`,
                                `au_adav _calendarinstances`

[08:51:57.93][d935b4d7] P8 tables list after delete operation: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[08:51:58.09][d935b4d7]     Table: adav_addressbooks. Migration started
[08:51:58.49][d935b4d7]     Table: adav_addressbooks. Migrated successfully
[08:51:58.56][d935b4d7]     Table: adav_cache. Migration started
[08:51:58.56][d935b4d7]     Table: adav_cache. Migrated successfully
[08:51:58.62][d935b4d7]     Table: adav_calendarobjects. Migration started
[08:51:58.66][d935b4d7]     Table: adav_calendarobjects. Migrated successfully
[08:51:58.72][d935b4d7]     Table: adav_calendars. Migration started
[08:51:58.93][d935b4d7]     Table: adav_calendars. Migrated successfully
[08:51:59.27][d935b4d7]     Table: adav_cards. Migration started
[08:52:04.30][d935b4d7]     Table: adav_cards. Migrated successfully
[08:52:04.37][d935b4d7]     Table: adav_groupmembers. Migration started
[08:52:04.37][d935b4d7]     Table: adav_groupmembers. Migrated successfully
[08:52:04.44][d935b4d7]     Table: adav_locks. Migration started
[08:52:04.44][d935b4d7]     Table: adav_locks. Migrated successfully
[08:52:04.51][d935b4d7]     Table: adav_principals. Migration started
[08:52:05.09][d935b4d7]     Table: adav_principals. Migrated successfully
[08:52:05.32][d935b4d7]     Table: adav_reminders. Migration started
[08:52:05.32][d935b4d7]     Table: adav_reminders. Migrated successfully
[08:52:05.67][d935b4d7] DAV tables was renamed.
[08:52:05.80][d935b4d7] Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0
Connecting to database: mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 1:56am \| IP Logged

Scripts in folder /vendor/sabre/dav/bin/ can somehow be used?
migrateto20.php
migrateto21.php
migrateto30.php
migrateto32.php

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 09 August 2019 at 1:58am \| IP Logged

Apparently the problem isn't about migration, we're not sure why DAV tables aren't created at all. Please remove the tables, enable logging, create tables again and see if the logs show anything relevant.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 2:34am \| IP Logged

interestingly:

by clicking Create / Update tables:
mysql> show tables;
+-------------------------------+
| Tables_in_AFTERLOGIC_DBv8     |
+-------------------------------+
| au_adav_addressbookchanges    |
| au_adav_addressbooks          |
| au_adav_cache                 |
| au_adav_calendarchanges       |
| au_adav_calendarinstances     |
| au_adav_calendarobjects       |
| au_adav_calendars             |
| au_adav_calendarsubscriptions |
| au_adav_cards                 |
| au_adav_groupmembers          |
| au_adav_locks                 |
| au_adav_propertystorage       |
| au_adav_reminders             |
| au_adav_schedulingobjects     |
| au_eav_attributes_bigint      |
| au_eav_attributes_bool        |
| au_eav_attributes_datetime    |
| au_eav_attributes_double      |
| au_eav_attributes_int        |
| au_eav_attributes_mediumblob |
| au_eav_attributes_string      |
| au_eav_attributes_text        |
| au_eav_entities               |
| au_min_hashes                 |
+-------------------------------+
24 rows in set (0.00 sec)

after run migrate.php:
mysql> show tables;
+------------------------------+
| Tables_in_AFTERLOGIC_DBv8    |
+------------------------------+
| addressbooks                 |
| au_eav_attributes_bigint     |
| au_eav_attributes_bool       |
| au_eav_attributes_datetime   |
| au_eav_attributes_double     |
| au_eav_attributes_int        |
| au_eav_attributes_mediumblob |
| au_eav_attributes_string     |
| au_eav_attributes_text       |
| au_eav_entities              |
| au_min_hashes               |
| cache                        |
| calendarobjects              |
| calendars                    |
| cards                        |
| groupmembers                 |
| locks                        |
| principals                   |
| reminders                    |
+------------------------------+
19 rows in set (0.00 sec)

[09:16:34.99][074e756f] P8 tables list before upgrade: au_adav_addressbookchanges, au_adav_addressbooks, au_adav_cache, au_adav_calendarchanges, au_adav_calendarinstances, au_adav_calendarobjects, au_adav_calendars, au_adav_calendarsubscriptions, au_adav_cards, au_adav_groupmembers, au_adav_locks, au_adav_propertystorage, au_adav_reminders, au_adav_schedulingobjects, au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[09:16:36.08][074e756f] Deleting tables from P8 DB: DROP TABLE IF EXISTS `au_adav_addressbookchanges`,
                                `au_adav _addressbooks`,
                                `au_adav _cache`,
                                `au_adav _calendarchanges`,
                                `au_adav _calendarobjects`,
                                `au_adav _calendars`,
                                `au_adav _calendarsubscriptions`,
                                `au_adav _cards`,
                                `au_adav _groupmembers`,
                                `au_adav _locks`,
                                `au_adav _principals`,
                                `au_adav _propertystorage`,
                                `au_adav _reminders`,
                                `au_adav _schedulingobjects`,
                                `au_adav _calendarinstances`

The migration script removes the tables see. log file. But then they won't create them anymore.
If I don't change anything and give F5:
So I get further:

[09:22:21.96][33157e9d] P8 tables list after delete operation: addressbooks, au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes, cache, calendarobjects, calendars, cards, groupmembers, locks, principals, reminders
[09:22:22.20][33157e9d]     Table: adav_addressbooks. Migration started
[09:22:22.60][33157e9d]     Table: adav_addressbooks. Migrated successfully
[09:22:22.66][33157e9d]     Table: adav_cache. Migration started
[09:22:22.66][33157e9d]     Table: adav_cache. Migrated successfully
[09:22:22.72][33157e9d]     Table: adav_calendarobjects. Migration started
[09:22:22.75][33157e9d]     Table: adav_calendarobjects. Migrated successfully
[09:22:22.82][33157e9d]     Table: adav_calendars. Migration started
[09:22:23.02][33157e9d]     Table: adav_calendars. Migrated successfully
[09:22:23.09][33157e9d]     Table: adav_cards. Migration started
[09:22:28.70][33157e9d]     Table: adav_cards. Migrated successfully
[09:22:28.79][33157e9d]     Table: adav_groupmembers. Migration started
[09:22:28.79][33157e9d]     Table: adav_groupmembers. Migrated successfully
[09:22:28.93][33157e9d]     Table: adav_locks. Migration started
[09:22:28.93][33157e9d]     Table: adav_locks. Migrated successfully
[09:22:29.01][33157e9d]     Table: adav_principals. Migration started
[09:22:29.45][33157e9d]     Table: adav_principals. Migrated successfully
[09:22:29.60][33157e9d]     Table: adav_reminders. Migration started
[09:22:29.60][33157e9d]     Table: adav_reminders. Migrated successfully
[09:22:29.60][33157e9d] Error during rename tables process. SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'addressbooks' already exists

Gradually I have make through this:
DROP TABLE adav_addressbooks;
DROP TABLE addressbooks;
DROP TABLE cache;
DROP TABLE adav_cache;
DROP TABLE calendarobjects;
DROP TABLE adav_calendarobjects;
DROP TABLE adav_calendars;
DROP TABLE calendarshares;
DROP TABLE adav_calendarshares;
DROP TABLE cards;
DROP TABLE adav_cards;
DROP TABLE groupmembers;
DROP TABLE adav_groupmembers;
DROP TABLE locks;
DROP TABLE adav_locks;
DROP TABLE principals;
DROP TABLE adav_principals;
DROP TABLE reminders;
DROP TABLE adav_reminders;
DROP TABLE calendars;

Then I am here again:
[09:30:27.61][57f3d1e2] P8 tables list after delete operation: au_eav_attributes_bigint, au_eav_attributes_bool, au_eav_attributes_datetime, au_eav_attributes_double, au_eav_attributes_int, au_eav_attributes_mediumblob, au_eav_attributes_string, au_eav_attributes_text, au_eav_entities, au_min_hashes
[09:30:27.77][57f3d1e2]     Table: adav_addressbooks. Migration started
[09:30:28.17][57f3d1e2]     Table: adav_addressbooks. Migrated successfully
[09:30:28.24][57f3d1e2]     Table: adav_cache. Migration started
[09:30:28.24][57f3d1e2]     Table: adav_cache. Migrated successfully
[09:30:28.31][57f3d1e2]     Table: adav_calendarobjects. Migration started
[09:30:28.34][57f3d1e2]     Table: adav_calendarobjects. Migrated successfully
[09:30:28.41][57f3d1e2]     Table: adav_calendars. Migration started
[09:30:28.64][57f3d1e2]     Table: adav_calendars. Migrated successfully
[09:30:28.71][57f3d1e2]     Table: adav_cards. Migration started
[09:30:34.31][57f3d1e2]     Table: adav_cards. Migrated successfully
[09:30:34.41][57f3d1e2]     Table: adav_groupmembers. Migration started
[09:30:34.41][57f3d1e2]     Table: adav_groupmembers. Migrated successfully
[09:30:34.48][57f3d1e2]     Table: adav_locks. Migration started
[09:30:34.48][57f3d1e2]     Table: adav_locks. Migrated successfully
[09:30:34.54][57f3d1e2]     Table: adav_principals. Migration started
[09:30:34.89][57f3d1e2]     Table: adav_principals. Migrated successfully
[09:30:34.96][57f3d1e2]     Table: adav_reminders. Migration started
[09:30:34.96][57f3d1e2]     Table: adav_reminders. Migrated successfully
[09:30:35.50][57f3d1e2] DAV tables was renamed.
[09:30:35.57][57f3d1e2] Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0
Connecting to database: mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 2:42am \| IP Logged

I accidentally deleted webmail in 7, missing a directory, but the script didn't report anything :(

I restored the directory from backup and ran everything again:
09:42:00.97][40c51d01]     Table: adav_locks. Migration started
[09:42:00.97][40c51d01]     Table: adav_locks. Migrated successfully
[09:42:01.06][40c51d01]     Table: adav_principals. Migration started
[09:42:01.45][40c51d01]     Table: adav_principals. Migrated successfully
[09:42:01.69][40c51d01]     Table: adav_reminders. Migration started
[09:42:01.69][40c51d01]     Table: adav_reminders. Migrated successfully
[09:42:02.06][40c51d01] DAV tables was renamed.
[09:42:02.12][40c51d01] Error during upgrade DB process. Failed migration from a pre-2.0 database to 2.0. Output:
SabreDAV migrate script for version 2.0
Connecting to database: mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 2:47am \| IP Logged

I run:
php migrateto20.php "mysql:host=127.0.0.1;dbname=AFTERLOGIC_DBv8" afterlogic "MyPASXXX"
next: migrateto21.php migrateto30.php migrateto32.php

Didn't I do something wrong?

Igor
AfterLogic Support

Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6066

Posted: 09 August 2019 at 3:13am \| IP Logged

Well yes that looks good, but you'd need to run the main migration script first with stop_before_sabredav_migrate per Alternative migration approach section at Migration from v7 page.

--
Regards,
Igor, Afterlogic Support

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 09 August 2019 at 4:27am \| IP Logged

Thank you, I managed to reproduce it :)

Thank you for your help.
I noticed a few things:
1) Existing users log in without a problem. A new user must have an @ xxx.com name can be set so that new users do not have to enter the entire domain?

2) Next in the settings:
Email account settings - (Forward or Autoresponder or AutomaticReply) everything works well, but if I do: delete the texts and then uncheck the enable, then I will save the changes, so the changes will not be saved and an error will be reported. Can't you edit it? I know you just need to uncheck the enable and then save your changes, but it can confuse users

esetman
Senior Member

Joined: 25 August 2014
Location: Czech Republic
Online Status: Offline
Posts: 158

Posted: 15 August 2019 at 5:00am \| IP Logged

does anyone know? Point 2 could be modified in the new version

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

Printable version

Forum Jump

.NET Components

ActiveX Components

Web scripts

Solutions

AfterLogic WebMail Pro