1066
Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 13, 2017, 08:40:38 pm »
Alright, so a quick update.
I did the following:
1) split up the contents of SENT folder into multiple child folders, that got me several with approx 1000-1500 msg each, a lot better than the single massive SENT folder
2) I re-indexed all the current folders, no errors found
3) I shut PMMail down, backed it up as both dir copy and ZIP
4) I installed the NEW application into a separate directory (so no overwrite over the old one) ...and....drumroll...here is where I ran into an issue...
During the install it appears that the new application process completed successfully. I do have the PMMail folder with all icons present. However, during the said install the Migrate tool was automatically kicked-off. I pointed it to the old PMMail install and told it to COPY stuff, do not delete the old one.
It is during this processing that I am getting an error message, see attachment for a screenshot of the error itself and some variable values in the inspection window.
Specifically, what I am wondering is whether the Migration tool crashes because it's attempting to copy a file which in the NEW install is currently 0 (zero) bytes. After all, it gave me an option to Migrate during the install, and as such I have not actually ran the new PMMail even once by this point in time.
The specific command that fails is: {"copy "'dst_dir'\Tools\group.db" "'dst_dir'\Tools\group.db.BAK" '}, where: dst_dir = G:\APPS\TCPIP\PMMail3\Accounts, and where the matching contents of that directory are:
Directory of G:\apps\tcpip\pmmail3\accounts\tools
10-13-17 2:10p 31118 0 addr.db
10-13-17 1:29p 3474 0 assoc.db
3-26-17 5:35p 289 0 books.db
2-08-11 8:19a 92 0 csetalii-default.db
10-13-17 1:36p 0 124 csetalii.db
10-05-98 2:00a 350 0 DirSvcs.db
7-18-17 3:56p 0 0 GROUP.DB
7 file(s) 35323 bytes used
Sooo....I have a half-baked install at the moment, and starting the NEW PMMail produces a good looking account structure, however, with zero messages. To be expected since the migration failed. I can certainly re-do all of this, however, one thought is troubling me: even in my old PMMail install that group.db file is 0 (zero) bytes as well.
Here are the matching entries for this directory in the old install:
Directory of G:\apps\tcpip\pmmail\tools
9-29-17 2:53p 31118 0 ADDR.DB
10-03-17 12:36p 1137 0 ASSOC.DB
3-26-17 5:35p 289 0 BOOKS.DB
10-05-98 2:00a 350 0 DirSvcs.db
7-18-17 3:56p 0 0 GROUP.DB
5 file(s) 32894 bytes used
Given the date/time stamp of the group.db file present in the NEW directory it certianly appears that the Migration process successfully copies it over in the first place, but then fails later on as it attempts to create a backup???
What is stored in that file anyways???
EDIT
====
Also attached the migratePMM.log-20171013-14-58-17, which I believe is the Migration Tool log. Unfortunately I do not see the failure point in there, but that could be just due to a timing issue?
I will try to log a ticket for this issue...
I did the following:
1) split up the contents of SENT folder into multiple child folders, that got me several with approx 1000-1500 msg each, a lot better than the single massive SENT folder
2) I re-indexed all the current folders, no errors found
3) I shut PMMail down, backed it up as both dir copy and ZIP
4) I installed the NEW application into a separate directory (so no overwrite over the old one) ...and....drumroll...here is where I ran into an issue...
During the install it appears that the new application process completed successfully. I do have the PMMail folder with all icons present. However, during the said install the Migrate tool was automatically kicked-off. I pointed it to the old PMMail install and told it to COPY stuff, do not delete the old one.
It is during this processing that I am getting an error message, see attachment for a screenshot of the error itself and some variable values in the inspection window.
Specifically, what I am wondering is whether the Migration tool crashes because it's attempting to copy a file which in the NEW install is currently 0 (zero) bytes. After all, it gave me an option to Migrate during the install, and as such I have not actually ran the new PMMail even once by this point in time.
The specific command that fails is: {"copy "'dst_dir'\Tools\group.db" "'dst_dir'\Tools\group.db.BAK" '}, where: dst_dir = G:\APPS\TCPIP\PMMail3\Accounts, and where the matching contents of that directory are:
Directory of G:\apps\tcpip\pmmail3\accounts\tools
10-13-17 2:10p 31118 0 addr.db
10-13-17 1:29p 3474 0 assoc.db
3-26-17 5:35p 289 0 books.db
2-08-11 8:19a 92 0 csetalii-default.db
10-13-17 1:36p 0 124 csetalii.db
10-05-98 2:00a 350 0 DirSvcs.db
7-18-17 3:56p 0 0 GROUP.DB
7 file(s) 35323 bytes used
Sooo....I have a half-baked install at the moment, and starting the NEW PMMail produces a good looking account structure, however, with zero messages. To be expected since the migration failed. I can certainly re-do all of this, however, one thought is troubling me: even in my old PMMail install that group.db file is 0 (zero) bytes as well.
Here are the matching entries for this directory in the old install:
Directory of G:\apps\tcpip\pmmail\tools
9-29-17 2:53p 31118 0 ADDR.DB
10-03-17 12:36p 1137 0 ASSOC.DB
3-26-17 5:35p 289 0 BOOKS.DB
10-05-98 2:00a 350 0 DirSvcs.db
7-18-17 3:56p 0 0 GROUP.DB
5 file(s) 32894 bytes used
Given the date/time stamp of the group.db file present in the NEW directory it certianly appears that the Migration process successfully copies it over in the first place, but then fails later on as it attempts to create a backup???
What is stored in that file anyways???
EDIT
====
Also attached the migratePMM.log-20171013-14-58-17, which I believe is the Migration Tool log. Unfortunately I do not see the failure point in there, but that could be just due to a timing issue?
I will try to log a ticket for this issue...